This is because the php engine shuts down completely when a fatal error is encountered. Symfony doesn't get to do anything after that point. What the error handler really handles are Exceptions, not fatal errors.
Daniel On May 10, 10:14 am, nurikabe <eaow...@gmail.com> wrote: > e.g.: sfErrorHandlerPlugin can't seem to trap errors like: "Fatal > error: Call to a member function xyz() on a non-object in file.php on > line ##" > > Is that to be expected, or is this possibly a limitation of the older > version of Symfony we are using (1.0.3)? > > Thanks > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > 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 > athttp://groups.google.com/group/symfony-users?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
