[wp-trac] [WordPress Trac] #12395: WP should also catch E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR

WordPress Trac wp-trac at lists.automattic.com
Fri Mar 12 22:10:13 UTC 2010


#12395: WP should also catch E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR
-------------------------------+--------------------------------------------
 Reporter:  Denis-de-Bernardy  |        Owner:  westi   
     Type:  defect (bug)       |       Status:  reopened
 Priority:  normal             |    Milestone:  2.9.3   
Component:  Warnings/Notices   |      Version:  2.9.2   
 Severity:  normal             |   Resolution:          
 Keywords:  has-patch          |  
-------------------------------+--------------------------------------------
Changes (by nacin):

  * keywords:  needs-patch => has-patch


Comment:

 It's not a security hole, but since there are fatal errors we're declining
 to report, we can cause annoying white screens of death.

 This includes blank iframes when showing a fatal compile error generated
 by a plugin. This was seen on wp-hackers when a plugin used a function
 name that was already being used elsewhere. We made another change in
 [13167] that prevents the error scrape from overriding WP_DEBUG, which
 would otherwise have shown the compile error.

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


More information about the wp-trac mailing list