You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to run this now, it fails on the first tenant with this error:
PHP Fatal error: Cannot declare class AddNotificationsEnabledSettings, because the name is already in use in /Users/matt/Sites/supersecretproject/database/settings/tenant/2023_06_05_145021_add_notifications_enabled.php on line 7
Symfony\Component\ErrorHandler\Error\FatalError
Cannot declare class AddNotificationsEnabledSettings, because the name is already in use
I dropped a ray()->backtrace() into the migrations file and it is indeed being required twice:
Is this a Laravel bug? I can't see anything in either package which would cause Laravel to forget it's static include cache. I notice Taylor did rename this static cache variable a few months ago.
Should this project be using anonymous classes?
The text was updated successfully, but these errors were encountered:
We have a console command which runs all tenant migrations like below. Not sure what changed because this used to work fine as recently as march.
When trying to run this now, it fails on the first tenant with this error:
I dropped a
ray()->backtrace()
into the migrations file and it is indeed being required twice:Is this a Laravel bug? I can't see anything in either package which would cause Laravel to forget it's static include cache. I notice Taylor did rename this static cache variable a few months ago.
Should this project be using anonymous classes?
The text was updated successfully, but these errors were encountered: