[wp-trac] [WordPress Trac] #36561: Deprecated notices should be classified as such.

WordPress Trac noreply at wordpress.org
Mon Oct 2 16:50:57 UTC 2017


#36561: Deprecated notices should be classified as such.
-----------------------------------+-----------------------------
 Reporter:  jrf                    |       Owner:
     Type:  enhancement            |      Status:  new
 Priority:  normal                 |   Milestone:  Future Release
Component:  General                |     Version:
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch 2nd-opinion  |     Focuses:
-----------------------------------+-----------------------------
Changes (by johnbillion):

 * keywords:  has-patch => has-patch 2nd-opinion
 * milestone:  4.9 => Future Release


Comment:

 I believe that the current error levels for deprecated calls, wrongdoings,
 etc is intentional. Note that the default error level used by
 `error_log()` is `E_NOTICE`.

 We can't upgrade anything to an `E_WARNING` because they can become
 visible on the front end of a poorly configured server (eg one that has
 `WP_DEBUG` correctly set to false but which has `display_errors` enabled,
 and it'll also cause logs to fill up if they're configured to only log
 warnings.

 If we downgrade the `E_NOTICE` triggered by deprecated calls to
 `E_DEPRECATED`, I'm wary of this change causing deprecated usage to go
 unnoticed when a server is configured to log notices but not deprecated
 notices. Is this a common configuration?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36561#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list