Opened 16 years ago
Closed 16 years ago
#9639 closed enhancement (fixed)
Error Reporting for Wp-load.php overrides E_DEPRECATED too late
Reported by: | jacobsantos | Owned by: | |
---|---|---|---|
Milestone: | 2.8 | Priority: | low |
Severity: | minor | Version: | 2.7 |
Component: | Warnings/Notices | Keywords: | has-patch tested commit |
Focuses: | Cc: |
Description
There is a problem with the wp-load.php for the administration where the bootstrap is not setting the E_DEPRECATED
and thus you get some notices about deprecation before wp-settings.php overrides the error reporting and stops it any further.
This is a strange error and might have to be with RC2-dev PHP version of PHP5.3.0. However, I am sending it here, just in case it is run-time verses compile-time settings (does not appear to be since moving the E_DEPRECATED
outside the if branch, does not remove the warnings.
The strange-ness of the notices is that the notices are in wp-settings.php lines 520+, whereas the error reporting is set in lines 220. There shouldn't be any notices displayed since the error reporting in lines 220 should prevent the notices from showing in 520.
Attachments (3)
Change History (13)
#1
@
16 years ago
Patch should apply to trunk as well. Let me know and I'll create another patch for trunk.
#2
@
16 years ago
Just checking... is this a dup of #8701, or a something specific to 2.7.1 (which will probably never be fixed).
#3
follow-up:
↓ 5
@
16 years ago
Yes, it's similar to #8701. However do we need all of these on a production install:
1 E_ERROR 2 E_WARNING 4 E_PARSE 16 E_CORE_ERROR 32 E_CORE_WARNING 64 E_COMPILE_ERROR 128 E_COMPILE_WARNING 256 E_USER_ERROR 512 E_USER_WARNING
Or perhaps we can stick to basic error reporting only:
error_reporting(E_ERROR | E_WARNING | E_PARSE);
Also if we need the long list, why are we "Xor" ^ E_STRICT
when we should be tuning it off "And Not" & ~E_STRICT
as proposed by westi. That makes the test for PHP 6.x redundant.
#4
@
16 years ago
It is basically the same as #8701 (why is that still open when it is fixed?) but for wp-load.php.
@azaozz That would work as well. A whitelist is starting to be less work and options than a blacklist.
#5
in reply to:
↑ 3
@
16 years ago
Replying to azaozz:
Also if we need the long list, why are we "Xor"
^ E_STRICT
when we should be tuning it off "And Not"& ~E_STRICT
as proposed by westi. That makes the test for PHP 6.x redundant.
In my tests, basically ^ E_STRICT
works the same as | ~E_STRICT
and same for the others.
#6
@
16 years ago
New error reporting replaces the tests and just displays the errors that we want to see.
Fix PHP deprecated notices based off of 2.7.1 tag.