I think log4php is not really needed as symfony has built in logging capability. But sending error to an email address is definitely missing from Symfony.
Any website owner would want to know if there's an error on their website because it would affect their users/visitors. On Sat, Feb 28, 2009 at 2:50 PM, Lee Bolding <[email protected]> wrote: > > I started thinking about that - look in SVN, and you'll see I started > adding Log4PHP ;) > > I never got round to finishing it though. Ideally, Log4PHP wouldn't be > integrated in this plugin anyway - it would be another plugin to > dynamically replace Symfony's built in logging classes... a job for > another day ;) > > At the moment it works as-is - I'm concerntrating on > sfDynamicFormsPlugin at the moment :) > > On 28 Feb 2009, at 00:36, Sid Bachtiar wrote: > >> >> Hey, that's a nice plugin! >> >> One very very useful feature that could be added is send stack trace >> error to an email address, e.g.: when there's error (any error), send >> email to the developer/admin. >> >> On Sat, Feb 28, 2009 at 1:28 PM, Lee Bolding <[email protected]> wrote: >>> >>> Or, install sfErrorHandlerPlugin >>> >>> http://www.symfony-project.org/plugins/sfErrorHandlerPlugin >>> >>> :) >>> >>> On 28 Feb 2009, at 00:21, Lawrence Krubner wrote: >>> >>>> >>>> What a mess. >>>> >>>> I post this as a warning for others. >>>> >>>> I did something that caused Symfony to crash. It might have been a >>>> change to a yaml file. I ended up facing a pure white screen. No >>>> error >>>> messages. I was looking at the development controller. Nothing. >>>> >>>> I got an earlier version of my yaml file out of Subversion. I >>>> cleared >>>> the cache several times - no help. >>>> >>>> I lost over a day trying to figure out the problem. >>>> >>>> Finally, I realized that me, Subversion and PHP were having a >>>> dispute >>>> over permissions, regarding the cache. Symfony wasn't able to clear >>>> the cache, because Subversion had ended up with some rights to the >>>> folder. I chmoded the cache to 777, cleared the cache, and got >>>> things >>>> working again. >>>> >>>> So here is the moral of this story: when facing a blank white >>>> screen, >>>> chmod the cache folder to 777. At least you can remove that as a >>>> potential problem. >>>>> >>> >>> >>>> >>> >> >> >> >> -- >> Blue Horn Ltd - System Development >> http://bluehorn.co.nz >> >> > > > > > > -- Blue Horn Ltd - System Development http://bluehorn.co.nz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
