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
It has a service argument for taking the service container (arguments: ["@service_container"]), which is then handled by the symfony dependency injection.
All this was working before I installed the doctrine migrations, then after installing, when flushing I get an error like this:
Catchable Fatal Error: Argument 1 passed to Core\DataFormsBundle\EntityListener\DataFormListener::__construct() must implement interface Psr\Container\ContainerInterface, none given, called in ...\vendor\doctrine\doctrine-bundle\Mapping\ContainerAwareEntityListenerResolver.php on line 76 and defined
Then un-installing doctrine migrations bundle removes the error and the listener works as expected.
Has anyone else had an error like this?
The text was updated successfully, but these errors were encountered:
I don't know, I could spend some time with old code, but we moved on to Symfony 4 and have not had any issues with any versions of migrations for Symfony 4.
I have the following versions:
I have an entity listener set up according to the service definition at https://symfony.com/doc/master/bundles/DoctrineBundle/entity-listeners.html
It has a service argument for taking the service container (arguments: ["@service_container"]), which is then handled by the symfony dependency injection.
All this was working before I installed the doctrine migrations, then after installing, when flushing I get an error like this:
Catchable Fatal Error: Argument 1 passed to Core\DataFormsBundle\EntityListener\DataFormListener::__construct() must implement interface Psr\Container\ContainerInterface, none given, called in ...\vendor\doctrine\doctrine-bundle\Mapping\ContainerAwareEntityListenerResolver.php on line 76 and defined
Then un-installing doctrine migrations bundle removes the error and the listener works as expected.
Has anyone else had an error like this?
The text was updated successfully, but these errors were encountered: