[wp-trac] [WordPress Trac] #20361: Deal with FALSE value of wp_get_theme() in ~/wp-admin/includes/dashboard.php to avoid making sad owls.

WordPress Trac wp-trac at lists.automattic.com
Mon Apr 30 19:26:47 UTC 2012


#20361: Deal with FALSE value of wp_get_theme() in ~/wp-
admin/includes/dashboard.php to avoid making sad owls.
-----------------------------+---------------------
 Reporter:  georgestephanis  |       Owner:
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  3.4
Component:  Themes           |     Version:  3.4
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |
-----------------------------+---------------------

Comment (by nacin):

 Replying to [comment:16 emiluzelac]:
 > I understand deprecated notices and of course they will be changed in
 3.4 no doubt about that, but that wasn't my point at all. Anyone with the
 basic knowledge of WordPress will tell you that deprecated notices will
 not produce "white screen" upon Theme upload/activation. Notice: Undefined
 index: can but not deprecated functions.

 The point that jkudish was trying to make is that they were unrelated,
 because they were.

 The deprecated notices did not cause a whitescreen. It was apparent that a
 fatal error (undefined method exists()) caused the white-screen. There
 also just happened to be unrelated notices on the page. They did not
 prevent the activation.

 You were testing on [20521]. This was fixed in [20524]. I wanted
 confirmation that it was fixed for you. The expectation was that it was
 and you would not be able to break it again. :-)

 Thanks for your help, all of you. Leaving as fixed.

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


More information about the wp-trac mailing list