[wp-trac] [WordPress Trac] #48720: Define all debugging constants for developers in wp-config.php
WordPress Trac
noreply at wordpress.org
Tue Nov 19 07:35:48 UTC 2019
#48720: Define all debugging constants for developers in wp-config.php
----------------------------+------------------------------
Reporter: davidnash | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Bootstrap/Load | Version: 5.3
Severity: normal | Resolution:
Keywords: | Focuses:
----------------------------+------------------------------
Changes (by SergeyBiryukov):
* component: General => Bootstrap/Load
Comment:
Hi there, welcome to WordPress Trac! Thanks for the report.
Just noting that there was a previous discussion on this in #28551.
Per nacin's comment in comment:30:ticket:28551:
> My only other comment here still stands: I'm still not sure I'd advocate
for any changes here.
>
> I'd like to make sure we are adequately weighing two competing things:
> 1. Giving more things users can either be confused about or possibly do
damage with. (For example, WP_DEBUG_LOG produces what would be a public
log file, SCRIPT_DEBUG can slow down their dashboard, and SAVEQUERIES can
slow down their site.)
> 2. A developer saving a few precious seconds.
>
> At ''most'', I'd suggest we add a link to
http://codex.wordpress.org/Debugging_in_WordPress and close this out.
The link was added in [32479] and changed to HelpHub in [32479].
--
Ticket URL: <https://core.trac.wordpress.org/ticket/48720#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list