Am 18.03.2012 18:53, schrieb Lester Caine: > Ferenc Kovacs wrote: >> * *|E_ALL|* now includes *|E_STRICT|* level errors in the error_reporting >> >> <http://docs.php.net/manual/en/errorfunc.configuration.php#ini.error-reporting> >> configuration >> directive. >> >> I would guess your code was running clean, because you didn't have E_STRICT >> in >> your error_reporting, now in php 5.4, E_ALL includes that by default, and if >> you >> don't explicitly mask it, you will see those messages. > > This yet another example of subtle problems being created by not > understanding when > settings get overriden without it being obvious!
for you, yes > My 5.3 servers are set up to ( E_ALL | E_STRICT ), and I was checking THAT in > phpinfo, but a > 'fix' for the strict errors had been applied elsewhere in the codebase which > simply > over-rid error_reporting one of the big DO NOT therefore exists <Directory> in httpd > SO my original question still applies, but for different reasons ... > is there a crib sheet to help eliminate strict code errors in legacy code > bases? damned DISABLE display_errors what should NEVER be enabled in prdouction and start reading your error-log - why the hell do you need any generic sheet if your logfile tells you existing problems?
signature.asc
Description: OpenPGP digital signature
