Christian Raue
Christian Raue
I guess it's related to symfony/symfony#7360.
I just tried upgrading again, from Symfony 2.1.8 to 2.1.9, but this error is still present using - jms/di-extra-bundle (1.2.0), - jms/di-extra-bundle (1.3.0), or - jms/di-extra-bundle (1.3.x-dev a153677). Would be...
I tried again using the following sets with Symfony 2.1.9: ``` - jms/aop-bundle (1.0.0) - jms/cg (1.0.0) - jms/di-extra-bundle (1.1.1) - jms/metadata (1.1.1) - jms/security-extra-bundle (1.2.0) ``` ``` - jms/aop-bundle...
@fesja: Yes, I'm using Twig. But I don't think that it has to do with this issue directly. I have no idea which component is causing it, though. @schmittjoh: Can...
In my case, `@PreAuthorize` seems to cause this issue. If I remove them from all controllers, the error doesn't show up.
@schmittjoh: Here's how to trigger this error with a clean 2.1.9 standard edition: In `src/Acme/DemoBundle/Controller/SecuredController.php`, change ``` php /** * @Route("/hello/admin/{name}", name="_demo_secured_hello_admin") * @Secure(roles="ROLE_ADMIN") * @Template() */ public function helloadminAction($name)...
Will this be merged some day?
Please refer to the documentation of DoctrineCacheBundle. It's already deprecated and you should better use Symfony's Cache component.
I'm unable to reproduce this. Could you set up a test or project revealing the issue?
I've [added Redis to the test suite](fc47fef66f174343f32f1b6b1c204b927236769c). This should make it easier to add a failing case.