[symfony-users] Re: a blank white screen

On Fri, 20 Mar 2009, Lee Bolding wrote: > Better to dump to a text file - the only thing that can go wrong with > that is permissions error or disk error (full/failure). Possibly > automatically fire it off in an email... We usually fire off an email with a stack trace that goes to our deve

[symfony-users] Re: a blank white screen

Is doesn't seem silly to anybody else that an error handler that relies on a DB connection is itself, yet another single point of failure? If you've experienced a fatal error, or even a badly handled non-fatal error, I can't see this is going to help you much. Heh, if the error is because

[symfony-users] Re: a blank white screen

Hi, I got the exact same problem. I tried to look at the code, but without any success. Did you find a solution? Thanks, Saad On Feb 28, 8:26 pm, Brian Racer wrote: > There is sfErrorLogger > and > sfDoctrineErrorLogger >

[symfony-users] Re: a blank white screen

There is sfErrorLogger and sfDoctrineErrorLogger . However when I was testing sfErrorLogger with Propel(Symfony 1.2 and Propel 1.3), it would break with database exc

[symfony-users] Re: a blank white screen

I had a white screen too. My problem was a too old PHP-Version. Did you run that lib\vendor\symfony\data\bin\check_configuration.php script. It's good to see, if your server is ready for symfony. --~--~-~--~~~---~--~~ You received this message because you are subscr

[symfony-users] Re: a blank white screen

On Fri, 27 Feb 2009, Lawrence Krubner wrote: > 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. Or look at your logs. -- --~--~-~--~~~---~--~~ You re

[symfony-users] Re: a blank white screen

> "Exception in sfCache". So? What should I do with that info? It took > me a while to figure out what the real problem was - a permissions > conflict. So, you should get stack trace rather than just short error like that! Your user should not see any error (which is what sfErrorHandlerPlugin doe

[symfony-users] Re: a blank white screen

On Feb 27, 8:57 pm, Sid Bachtiar wrote: > 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 wou

[symfony-users] Re: a blank white screen

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

[symfony-users] Re: a blank white screen

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

[symfony-users] Re: a blank white screen

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 wrote: > > Or, install sfErrorHandlerPlugin > > http:/

[symfony-users] Re: a blank white screen

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