Opened 4 years ago
Closed 4 years ago
#9871 closed enhancement (invalid)
Avoid those PHP errors to be logged
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Warnings/Notices | Version: | |
| Severity: | normal | Keywords: | dev-feedback |
| Cc: |
Description (last modified by dd32)
It is very surprising to log errors detected by php when under admin.
Removing those errors would help WordPress to be
* faster (php not trying to log those errors) * more reliable * compliant for PHP future versions !
hereattached, log file produced for each admin screen !
Attachments (9)
Change History (15)
- Component changed from Optimization to Warnings/Notices
- Keywords needs-patch added
- Milestone changed from Unassigned to Future Release
- Owner Denis-de-Bernardy deleted
- Type changed from defect (bug) to enhancement
instanceof is php5.
Logedit_posts.txt contains a few notices.
Logdashboard.txt contains a warning.
Can you confirm this is with 2.8? E_STRICT shouldn't be raised in trunk.
- Description modified (diff)
Due to PHP4 support, Its impossible not to trigger E_STRICT level warnings.
comment:3
peaceablewhale — 4 years ago
- Keywords dev-feedback added; needs-patch removed
is_a is no longer deprecated in PHP 5.3.0: http://www.php.net/manual/en/function.is-a.php
Since most E_STRICT messages are caused by it, I think this report can be resolved as "won't fix" until support to PHP 4 can be dropped.
Agreed, but there actually are a few notices and warnings, so I had kept it open:
comment:5
peaceablewhale — 4 years ago
The E_WARNING is actually a timed out error.
I am not able to reproduce the E_NOTICE message anyway...
- Milestone Future Release deleted
- Resolution set to invalid
- Status changed from new to closed
let's close then.
arriving on admin logging page