Comments on: DOING_AUTOSAVE E_WARNING http://www.mittineague.com/blog/2009/08/doing_autosave-e_warning/ Random rants and rambling ons, Observations and Opinion, Information and Instigation Wed, 22 Dec 2010 02:48:09 -0500 hourly 1 http://wordpress.org/?v=2.1 By: Mittineague http://www.mittineague.com/blog/2009/08/doing_autosave-e_warning/comment-page-1/#comment-944 Mittineague Fri, 18 Sep 2009 00:52:23 +0000 http://www.mittineague.com/blog/?p=159#comment-944 I find that most of the E_NOTICE errors result from WordPress continuing it's support for PHP 4 I don't really understand why anyone would still want to use old PHP after this long, but I'm guessing it's similar to some users not ugrading WordPress even when it's for a security patch. I find that most of the E_NOTICE errors result from WordPress continuing it's support for PHP 4

I don't really understand why anyone would still want to use old PHP after this long, but I'm guessing it's similar to some users not ugrading WordPress even when it's for a security patch.

]]> By: Giles http://www.mittineague.com/blog/2009/08/doing_autosave-e_warning/comment-page-1/#comment-942 Giles Thu, 17 Sep 2009 16:12:09 +0000 http://www.mittineague.com/blog/?p=159#comment-942 I wish the WP team would be a bit more rigorous about coding standards. WP throws slews of E_NOTICE errors, which might not be annoying on a standard PHP config but which makes it very frustrating to embed into a site which has a stricter error reporting level. Don't even get me started on the huge list of global variables it uses - like $request, which is like dropping $email into the global namespace and hoping nobody else wanted to use that variable. Really, doing v3 properly (e.g. OO, everything neatly encapsulated and modular) would be a revelation. They could provide an optional file which defined legacy global functions & variables so that themes didn't break. I wish the WP team would be a bit more rigorous about coding standards. WP throws slews of E_NOTICE errors, which might not be annoying on a standard PHP config but which makes it very frustrating to embed into a site which has a stricter error reporting level.

Don't even get me started on the huge list of global variables it uses – like $request, which is like dropping $email into the global namespace and hoping nobody else wanted to use that variable.

Really, doing v3 properly (e.g. OO, everything neatly encapsulated and modular) would be a revelation. They could provide an optional file which defined legacy global functions & variables so that themes didn't break.

]]>