I've fixed this. Basically, it was a security context issue. In case someone
runs into a similar problem, here is the problem and my solution.
A Twig_Error_Runtime exception was getting thrown due to there not being an
authentication token set. This gets triggered when attempting to render my
While I'm spamming my own thread (sorry about that...), is there a way to
alter my firewall configuration so that exceptions are included in same
security context as the rest of my site? The problem is that if a user is
logged in and an exception is thrown, it appears to log them out due to the
This probably isn't incredibly new behavior but I just recently updated to
the latest master of Symfony2 and I noticed that NotFoundHttpException is no
longer caught when it's thrown unless I use the dev environment.. I just get
a blank white page instead. I've tried to keep up with the changes
Le 13/05/2011 22:13, Carl a écrit :
This probably isn't incredibly new behavior but I just recently
updated to the latest master of Symfony2 and I noticed that
NotFoundHttpException is no longer caught when it's thrown unless I
use the dev environment.. I just get a blank white page instead.
I'm using the current master branch. Until I added the init() function found
in the SE to my AppKernel class, the raw PHP error was being displayed
instead of the exception being intercepted, which is rather troubling in a
production environment. I've made certain to clear my cache, rebuild my
It looks like the MethodNotAllowedException (I think that's the name) is
affected as well. If I try to access a route that requires the method to be
POST via the GET method, I just get a blank white page. If I enable error
handling, a raw PHP error message is displayed saying that the exception
