On 4 September 2012 15:09, Lester Caine <les...@lsces.co.uk> wrote: > Pierre Joye wrote: >> >> On Tue, Sep 4, 2012 at 2:51 PM, Lester Caine<les...@lsces.co.uk> wrote: >> >>> >??? OH YES IT DOES !!! >>> >MANY times I get a a few lines of text on a white screen ... >>> >Switch off E_STRICT and everything works fine ... as it was on PHP5.2 >> >> If you have any doubts about how to configure your development or >> production servers, how to use logs or how to effectively debug php >> applications, please ask questions on php-general or php-setup mailing >> lists. >> >> Thanks for your understanding, > > Butt out Pierre ... > > I keep being told that there is nothing wrong with E_STRICT, and again > someone has said that it does NOT cause crashes. I beg to differ here - IT > DOES! > Now if you are saying that I need to document these crashes as they SHOULD > not be happening then I'll roll things back and start doing that, but *I* > thought that these crashes were simply a known effect of using E_STRICT? And > so I followed the directions, and switched E_STRICT off. On production > machines of PHP5.3 with E_STRICT enabled and on PHP5.4 one gets white screen > crashes using older code ... as far as I was concerned that was a known > fact. Switch it off and everything runs fine! >
>From php.ini: ; display_errors ; Default Value: On ; Development Value: On ; Production Value: Off In a production environment with display_errors off, E_STRICT doesn't crash anything. Actually, even with it on, it doesn't crash anything - shitty code does, by creating notices and then using header() calls afterwards to create redirects. Solution: fix your server. Fix your code. It worked for the rest of us. Regards Peter -- <hype> WWW: plphp.dk / plind.dk CV: careers.stackoverflow.com/peterlind LinkedIn: plind Twitter: kafe15 </hype> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
