How to stop E_DEPRECATED messages in the PHP log?
in [General]
|
Prev: PHP SOAP Using SAML
Next: mysql cache query as xml
From: Jeff Weinberger on 7 Jul 2009 11:03 On Jul 7, 2009, at 5:50 AM, Richard Quadling wrote: > 2009/7/6 Jeff Weinberger <jeff(a)jeffweinberger.com>: >> Hi: >> >> I am hoping someone can help me figure this out.... >> >> I've just upgraded my PHP installation to 5.3.0. Now I am receiving >> thousands of log messages of the form "PHP Deprecated: ...". >> >> I know I have a number of scripts that use now-deprecated >> functions, etc. >> and I now know what those are, thanks to all the messages. >> >> However, this is now growing to (literally) gigabytes of log >> entries, so I'd >> like to stop the messages until I have the time to re-write all the >> offending scripts. >> >> I have tried the following error.reporting lines in php.ini: >> >> error_reporting = E_ALL & ~E_DEPRECATED & E_ERROR & E_WARNING & >> E_PARSE & >> E_NOTICE & E_CORE_ERROR & E_USER_ERROR & E_USER_WARNING & >> E_USER_NOTICE & >> E_COMPILE_ERROR & E_COMPILE_WARNING >> >> error_reporting = ~E_DEPRECATED & E_ALL & E_ERROR & E_WARNING & >> E_PARSE & >> E_NOTICE & E_CORE_ERROR & E_USER_ERROR & E_USER_WARNING & >> E_USER_NOTICE & >> E_COMPILE_ERROR & E_COMPILE_WARNING >> >> error_reporting = E_ALL & E_ERROR & E_WARNING & E_PARSE & E_NOTICE & >> E_CORE_ERROR & E_USER_ERROR & E_USER_WARNING & E_USER_NOTICE & >> E_COMPILE_ERROR & E_COMPILE_WARNING & ~E_DEPRECATED >> >> error_reporting = E_ERROR & E_CORE_ERROR & E_USER_ERROR & >> E_COMPILE_ERROR & >> E_COMPILE_WARNING & ~E_DEPRECATED >> >> error_reporting = ~E_DEPRECATED & E_ERROR & E_CORE_ERROR & >> E_USER_ERROR & >> E_COMPILE_ERROR & E_COMPILE_WARNING >> >> (as you can tell, I prefer verbose logs, but not that verbose...). >> >> None of these combinations have stopped the "PHP Deprecated: ..." >> messages. >> >> System info: Mac OS/X 10.5.7 Client version, PHP 5.3.0 running as a >> CGI >> under Apache 2.2.11 and as a CLI. Please let me know if there's any >> other >> info that might help. >> >> php_info() reports error.reporting as "0" >> >> Any help or guidance is appreciated!! >> >> Thanks, >> >> --Jeff >> >> >> >> No one ever achieved greatness by playing it safe. -Harry Gray >> >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > > Try ... > > error_reporting = 22527 > > > -- > ----- > Richard Quadling > Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 > "Standing on the shoulders of some very clever giants!" > I need a car : http://snipurl.com/l4pih > ZOPA : http://uk.zopa.com/member/RQuadling Richard (and Tom): This seemed like it would be the perfect solution...but alas it did not work. 22527 seems right, but after changing php.ini to that and restarting php and apache, I am still getting "Deprecated..." messages. :( I'll keep trying...and any other suggestions are much appreciated! Thanks! A wise man will make more opportunities than he finds. -Francis Bacon
From: Daniel Brown on 7 Jul 2009 11:38 On Tue, Jul 7, 2009 at 11:03, Jeff Weinberger<jeff(a)jeffweinberger.com> wrote: > > This seemed like it would be the perfect solution...but alas it did not > work. 22527 seems right, but after changing php.ini to that and restarting > php and apache, I am still getting "Deprecated..." messages. Dumb question, Jeff: are you sure you're editing the correct php.ini file? -- </Daniel P. Brown> daniel.brown(a)parasane.net || danbrown(a)php.net http://www.parasane.net/ || http://www.pilotpig.net/ Check out our great hosting and dedicated server deals at http://twitter.com/pilotpig
From: Jeff Weinberger on 7 Jul 2009 12:17 On Jul 7, 2009, at 8:38 AM, Daniel Brown wrote: > On Tue, Jul 7, 2009 at 11:03, Jeff > Weinberger<jeff(a)jeffweinberger.com> wrote: >> >> This seemed like it would be the perfect solution...but alas it did >> not >> work. 22527 seems right, but after changing php.ini to that and >> restarting >> php and apache, I am still getting "Deprecated..." messages. > > Dumb question, Jeff: are you sure you're editing the correct > php.ini file? > > -- > </Daniel P. Brown> > daniel.brown(a)parasane.net || danbrown(a)php.net > http://www.parasane.net/ || http://www.pilotpig.net/ > Check out our great hosting and dedicated server deals at > http://twitter.com/pilotpig > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php Daniel: Not a dumb question at all! I check every time (php_info()) to make sure the "loaded configuration file" is the one I'm editing. So, as far as I can tell, yes. Should I be looking at something else to be sure? Thanks! --Jeff > UNIX is the Klingon of cyberspace. -from The Cluetrain Manifesto
From: Tom Worster on 7 Jul 2009 12:38 On 7/7/09 11:38 AM, "Daniel Brown" <danbrown(a)php.net> wrote: > On Tue, Jul 7, 2009 at 11:03, Jeff Weinberger<jeff(a)jeffweinberger.com> wrote: >> >> This seemed like it would be the perfect solution...but alas it did not >> work. 22527 seems right, but after changing php.ini to that and restarting >> php and apache, I am still getting "Deprecated..." messages. > > Dumb question, Jeff: are you sure you're editing the correct php.ini file? i was about to ask the same. phpinfo() will tell you the path to the in-effect config file.
From: Tom Worster on 7 Jul 2009 15:30
On 7/7/09 12:17 PM, "Jeff Weinberger" <jeff(a)JeffWeinberger.com> wrote: > On Jul 7, 2009, at 8:38 AM, Daniel Brown wrote: > >> On Tue, Jul 7, 2009 at 11:03, Jeff >> Weinberger<jeff(a)jeffweinberger.com> wrote: >>> >>> This seemed like it would be the perfect solution...but alas it did >>> not >>> work. 22527 seems right, but after changing php.ini to that and >>> restarting >>> php and apache, I am still getting "Deprecated..." messages. >> >> Dumb question, Jeff: are you sure you're editing the correct >> php.ini file? >> >> -- >> </Daniel P. Brown> >> daniel.brown(a)parasane.net || danbrown(a)php.net >> http://www.parasane.net/ || http://www.pilotpig.net/ >> Check out our great hosting and dedicated server deals at >> http://twitter.com/pilotpig >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php > > Daniel: > > Not a dumb question at all! I check every time (php_info()) to make > sure the "loaded configuration file" is the one I'm editing. So, as > far as I can tell, yes. > > Should I be looking at something else to be sure? i've now had a look at http://www.php.net/manual/en/errorfunc.constants.php in your shoes i'd try out 2047 (with is everything up to and including E_USER_NOTICE) and possibly 6143 (=2047+4096) if you have your own error handler. if still no luck i can't think of anything else to suggest but work backwards: check the value returned by error_reporting() is the value you set in php.ini. binary decode it to double check. if it sill makes no sense, check the php bugs db. and if nothing, maybe report it. |