I've been working w/ the 1.2 branch and find myself wanting to see the standard HTML exception page when an exception is thrown with a sf_format parameter set. Perhaps we should assume a human will be reading the exception response when a project is in debug mode and always render HTML?
Kris On Sep 10, 12:17 am, Fabien Potencier <[EMAIL PROTECTED] project.com> wrote: > Definitely. > > -- > Fabien Potencier > Sensio CEO - symfony lead developer > sensiolabs.com | symfony-project.com | aide-de-camp.org > Tél: +33 1 40 99 80 80 > > Francois Zaninotto wrote: > > Kris introduced a great new plugin today which makes working with > > non-HTML exceptions much easier. > > > Is there a chance to see that integrated into the core in symfony 1.2? > > > François > > > ---------- Forwarded message ---------- > > From: Kris Wallsmith <[EMAIL PROTECTED]> > > Date: 2008/9/9 > > Subject: [symfony-users] Introducing sfExceptionFormatsPlugin > > To: [EMAIL PROTECTED] > > > I've just released a new plugin called sfExceptionFormatsPlugin, > > available on symfony-projects.org. This plugin extends the request > > formats feature added in symfony 1.1 to include the error 500 and > >exceptionpages. With this plugin installed, any uncaught exceptions > > thrown will render as the appropriate content type, per the > > sfWebRequest format option. > > >http://www.symfony-project.org/plugins/sfExceptionFormatsPlugin/1_0_0... > > > Kris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
