As an aside, a LegacyError is any PHP error that isn't an exception (or, that is an UNCAUGHT exception).
The errorHandler in sfErrorHandlerPlugin replaces the standard PHP error handler and rethrows PHP errors as exceptions (which the rendering filter then catches and displays) On 6 Mar 2009, at 09:59, Lee Bolding wrote: > > > On 6 Mar 2009, at 02:59, Lawrence Krubner wrote: > >> Okay, I sort of see what is going on now. >> >> When the login page is done loading, the sfErrorHandler plugin >> attempts to send a 500 response and then send an error. >> >> Does anyone know why this plugin would mis-fire? > > Well, that's a test case I hadn't thought of ;) > > I'll try to replicate it over the weekend. > > Looks like the security controller has started sending the error page, > and then sfErrorHandler caught the exception, and tried to send it's > 500 error page too. If that's the case, I probably just need to add a > catch clause into the rendering filter to ignore this type of > exception. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
