I've never called forward(), but the documentation says "This method stops the action. So, no code is executed after a call to this method." I assume it is throwing the exception to stop the action. I would think this propagates up and is caught at a higher level, though apparently that is not happening for you. Possibly Symfony wants you to consciously catch and handle this, when you call forward()?
On Sep 24, 4:34 am, ollietb <[email protected]> wrote: > Hi there > I've noticed that my PHP logs are full of thousands of PHP Fatal > error: Uncaught exception 'sfStopException' errors whenever an action > is forwarded or redirected. It's making it hard for me to debug > errors. The offending code is in the sfAction class. Here is one > example. > > public function forward($module, $action) > { > > $this->getController()->forward($module, $action); > > throw new sfStopException(); > } > > The sfStopException is thrown but not caught. I'm thinking of using > set_exception_handler() in the projectConfiguration class to override > the default exception handler if an exception is not caught within a > try/catch block. The exception handler would simply be a a function > which die()s the current execution. Do any of you sfExperts have an > opinion on this? Would it be better to override the forward method in > my own Actions class? > I'm running Symfony 1.1 on OS: Red Hat Enterprise Linux Server release > 5.3 (Tikanga) 54 and PHP Version: 5.2.10 (eAccelerator is not > installed) > Thanks, > -ollie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
