[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 Feb 26 22:26:01 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: new
Priority: normal | Milestone: 3.0
Component: Warnings/Notices | Version: 2.9.2
Severity: normal | Keywords: has-patch
-------------------------------+--------------------------------------------
When writing PHP 5 code, and using the static operator, you can end up
with a blank screen in WP. Inheriting a class with a static function and
overriding it with a non-static function, for instance, triggers an
E_COMPILE or E_CORE (not sure which one exactly), and this leads to a
blank screen unless WP_DEBUG is switched on.
The attached patch (it's against 2.9.2, but I take it that it'll apply
fine to trunk) adds E_CORE and E_COMPILE to the errors reported by WP.
It also fixes an E_NOTICE when COOKIEHASH is already defined.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/12395>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list