[wp-trac] [WordPress Trac] #14729: Fatal errors after [15531] when conditional tags are used too early

WordPress Trac wp-trac at lists.automattic.com
Mon Aug 30 14:55:38 UTC 2010


#14729: Fatal errors after [15531] when conditional tags are used too early
--------------------------+-------------------------------------------------
 Reporter:  zamoose       |       Owner:              
     Type:  defect (bug)  |      Status:  new         
 Priority:  normal        |   Milestone:  3.1         
Component:  General       |     Version:              
 Severity:  critical      |    Keywords:  dev-feedback
--------------------------+-------------------------------------------------

Comment(by demetris):

 Replying to [comment:1 nacin]:
 > I have an interesting idea for this -- we leave this as is until late in
 the dev cycle. Hopefully that fixes up a good number of plugins including
 BuddyPress. And then we add sanity checks before release. Perhaps crazy,
 but at least it'll fix up a lot of code along the way.

 Another idea would be to make a post on wpdevel, '''from now''', tagged
 ''31compat'' and going something like:

 Please check your plugins/themes with WP_DEBUG on WordPress 3.0.  If you
 get “Trying to get property of non-object” notices in WP 3.0, that means
 that your plugin/theme will cause FATAL ERRORS in WP 3.1.

 Why this happens: Blah blah.

 How to fix: Blah blah.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14729#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list