hi, On 8 May 2010 14:34, Jeff Waugh <[email protected]> wrote: > <quote who="justin randell"> > >> > [Sun May 02 16:17:47 2010] [error] [client 10.0.0.2] PHP Warning: >> > session_start() [<a href='function.session-start'>function.session- >> > start</a>]: Cannot send session cache limiter - h >> > [Sun May 02 16:17:55 2010] [error] [client 10.0.0.2] PHP Deprecated: >> > Function set_magic_quotes_runtime() is deprecated in /var/www/blog/wp- >> > settings.php on line 27, referer: http://sl >> >> what that's telling you is that wordpress core code will not run on >> php 5.3 without throwing heaps of warnings. > > That is not the case, however, certainly not with WordPress 2.9 (and I'm > pretty sure, all the way back to 2.7 and earlier)... in normal operation, > there should be *no* warnings whatsoever running WordPress core.
i stand corrected. wordpress will throw E_DEPRECATED for php 5.3, not warnings, so its possible to adjust your error_reporting settings to deal with that without ignoring warnings. > The second last log line, and inaccuracy of "line 27" (given that call is on > line 18 in WordPress 2.9), seem suspicious to me... sounds like Richard has > something else running on every request? Notably session_start is not called > in the WordPress codebase. well colour me surprised, i'd just ass u me'd that session_start was wordpress code. learn something new about wordpress every day. that really got me curious, so i had a poke around the 2.9.2 code base. jeff, i'm wondering what led to a decision to reimplement php session handling in custom code? seems the code that leads to pulling the $user from a permanent store via an encrypted cookie value is exactly what sessions are for? was it a desire to use a non-file based store and an aversion to using custom session handlers? was it a desire to control the strength of the cookie hash? cheers justin -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
