-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Could not find any fixture services to load. #728
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
Comments
The fixtures of this app are stored in Independently from the previous comment, you can execute the command as follows to make it work no matter which version of fixtures bundle you use: $ php bin/console doctrine:fixtures:load --fixtures=src/DataFixtures/ |
Thanks, but I get this
Current package set:
|
Same behavior with
See:
|
Why don t you guys simply provide an sql file for mysql users? Nobody wants to work with sqlite, I guess. |
@lbm-services The answer is simple, this demo version should work in one click, I mean |
I guessed that, I mean as an OPTION. |
@lbm-services It would be a good idea to create a dockerized fork of |
@lbm-services Actually, you don't need any SQL file at all if you prefer MySQL. Just tweak DB credentials and use console commands: bin/console d:d:c
bin/console d:s:c
bin/console d:f:l That's it, you'll have the same dummy data you see in SQLite |
Let's close this because when using the latest DoctrineFixturesBundle (as recommended by this app) you no longer see this error. If you still see this problem, please tell us your DoctrineFixturesBundle version and the steps to reproduce. Thanks! |
@lbm-services I also get same problem and solve it by assigning tag to the fixture. Please see the solution https://stackoverflow.com/questions/47613979/symfony-3-4-0-could-not-find-any-fixture-services-to-load/48049905#48049905 |
I have two fixtures-loader services registered in a configuration file, each depending on a specific doctrine database connection. |
You probably have 2 entity managers, so you can use |
@bocharsky-bw I do know about the --em option … |
Hm, what about to pass an entity manager into all fixture loaders and add a custom logic at the beginning of |
Lol that's exactly my workaround solution at the moment.
But this do feel like a workaround and not a proper solution to me. |
Then probably better to create an issue in DoctrineFixturesBundle instead or make a PR :) |
https://symfony.com/doc/master/bundles/DoctrineFixturesBundle/index.html follow the documentation It is fixed. |
I've created a PR: doctrine/DoctrineFixturesBundle#250 |
After changing .env to mysql doctrine:schema:create finished successful.
doctrine:fixtures:load
Could not find any fixture services to load.
The text was updated successfully, but these errors were encountered: