Open mariselli opened 10 years ago
Which version of this bundle are you using?
On Wed, Dec 4, 2013 at 2:37 AM, Mattia Mariselli notifications@github.comwrote:
Hi, I had a cache problem with this bundle in dev environment. When I mark a file with @Secure https://github.com/Secure annotation, every* next change to the file has no effect (when I go to the url the action are execute even if I changed the role). To make changes effective I have to run a cache:clear. In product environment that's would be good, but in dev env it's extremely frustrating. Which could be the problem?
Thanks for support, greetings.
- changes to annotation and code both
— Reply to this email directly or view it on GitHubhttps://github.com/schmittjoh/JMSSecurityExtraBundle/issues/159 .
I'm using 1.2 with Symfony 2.3.7
I have similar effect with a controller as a service (don't know if that matters) using the @Secure annotation. When i remove an action in my controller and refresh my page, i have an error (not intercepted by Symfony)
Fatal error: Uncaught exception 'ReflectionException' with message 'Method MyBundle\Controller\DefaultController::indexAction() does not exist' in ..\Symfony\vendor\jms\metadata\src\Metadata\MethodMetadata.php:64 Stack trace: #0 ..\Symfony\vendor\jms\metadata\src\Metadata\MethodMetadata.php(64): ReflectionMethod->__construct('MyBundle...', 'indexAction') #1 ..\Symfony\vendor\jms\security-extra-bundle\JMS\SecurityExtraBundle\Metadata\MethodMetadata.php(101): Metadata\MethodMetadata->unserialize('a:2:{i:0;s:52:"...') #2 [internal function]: JMS\SecurityExtraBundle\Metadata\MethodMetadata->unserialize('a:6:{i:0;s:93:"...') #3 ..\Symfony\vendor\jms\metadata\src\Metadata\ClassMetadata.php(94): unserialize('a:5:{i:0;s:52:"...') #4 [internal function]: Metadata\ClassMetadata->unserialize('a:5:{i:0;s:52:"...') #5 M:\sf2_cache\opali\dev\jms_security\MyBundle-Controller-DefaultController.cache.php(1): uns in ..\Symfony\vendor\jms\metadata\src\Metadata\MethodMetadata.php on line 64
seems like cache is not refreshed / cleared I use Symfony 2.4.1 / PHP 5.7 / dev-master branch of this bundle
+1
I downgraded to 1.5.1 and cache now clears.
+1
Still seeing this in dev environment on PHP7, Version 1.6.1
Hi, I had a cache problem with this bundle in dev environment. When I mark a file with @Secure annotation, every* next change to the file has no effect (when I go to the url the action are execute even if I changed the role). To make changes effective I have to run a cache:clear. In product environment that's would be good, but in dev env it's extremely frustrating. Which could be the problem?
Thanks for support, greetings.