-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GeneratorCommand cannot have an empty name #1163
Comments
Are you able to provide the full stack trace for the error? You can find it in your log file ( |
Yes! Here it is:
|
Thanks! I have a feeling this is actually an issue in Statamic, rather than Simple Commerce, caused by statamic/cms#9270. I'll try and take a look in the next couple of days. |
Thanks @duncanmcclean! |
Closing in favour of statamic/cms#10873, which already has a PR opened against it. |
Actually, I don't think that's the same thing. Re-opening. |
If you make the |
@duncanmcclean I get a not instantiable error in my logs:
|
I was just browsing the issues when this occurred. Happened to me as well. Unfortunately I cannot tell if it was a Statamic upgrade or a Simple Commerce upgrade that lead to this error. Actually. The error message seems to complain about a name being empty. Looking at the other commands the all seem to have a name: protected $name = 'namehere '; |
I've opened a PR on the Statamic side (statamic/cms#10882), which coupled with v7.5.2 will fix the issue. The Statamic fix will likely be included in the next release. |
Cool! Thanks! @darinlarimore I temporary added the following to GeneratorCommand.php for now so I can continue to develop locally. It will be overridden by the next Statamic update:
|
This is fixed now - with Statamic v5.29.0 and Simple Commerce v7.5.2. |
Description
Using Statamic v5.28.0 I receive an error when running composer install. This error seems to stem from the

@php artisan package:discover --ansi
post-autoload-dump function.Steps to reproduce
using composer update statamic/cms
Environment
Command
php please support:details
won't run!The text was updated successfully, but these errors were encountered: