Closed hlorofos closed 2 months ago
Workaround is:
remove statamic from auto-discovery by adding the following to composer.json
"extra": {
"laravel": {
"dont-discover": [
"statamic/cms"
]
}
}
manually add \Statamic\Providers\StatamicServiceProvider::class,
to the end of providers list in config/app.php
for Laravel Framework.
Now its possible to run php artisan
command again
Do you have anything custom in your AppServiceProvider
or your ViewServiceProvider
?
I see the issue.
In https://github.com/statamic/cms/pull/9732 it should have been added to boot
, not register
.
Bug description
I'm trying to install Statamic CMS over my existing application, but when I run
php artisan
it failed with the following stack traceImportant lines are here
It tries to register it's blade directives but failed.
How to reproduce
this happened on the existing project on Laravel 10.48.8 when I tried to add Statamic by running
composer require statamic/cms --with-dependencies
Logs
No response
Environment
Installation
Existing Laravel app
Antlers Parser
None
Additional details
No response