Closed malle-pietje closed 4 months ago
After publishing and running the migrations, the error went away:
php artisan vendor:publish --tag="filament-email-migrations"
php artisan migrate
May I suggest adding a note to the README.md file to emphasize this step is required when upgrading?
By the way; thanks for maintaining this great plugin. It has been extremely useful in this specific app! 👍
After publishing and running the migrations, the error went away:
php artisan vendor:publish --tag="filament-email-migrations" php artisan migrate
May I suggest adding a note to the README.md file to emphasize this step is required when upgrading?
By the way; thanks for maintaining this great plugin. It has been extremely useful in this specific app! 👍
Thanks @malle-pietje, in the last release i've added a notice into README
What happened?
After running
composer update
I am getting this error when accessing the main resource page for the email logs:This is the relevant output from the
composer update
command:How to reproduce the bug
Simply upgrade from version 1.3.1 to 1.4.0.
The config file wasn't changed, here are the contents:
There are no pending migrations after the update.
Package Version
1.4.0
PHP Version
8.2.15
Laravel Version
10.48.10
Which operating systems does with happen with?
Linux
Notes
The app where this happened doesn't have a team model.