[wp-trac] [WordPress Trac] #28551: Add Better Debugging Documentation Into wp-config.php

[WordPress Trac]

#28551: Add Better Debugging Documentation Into wp-config.php
-------------------------------+-----------------------------
 Reporter:  philiparthurmoore  |       Owner:
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Future Release
Component:  Bootstrap/Load     |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  needs-patch        |     Focuses:  docs
-------------------------------+-----------------------------

Comment (by F J Kaiser):

 Replying to [comment:30 nacin]:
 > I'd like to make sure we are adequately weighing two competing things:

 Reasonable.

 >  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.)

 Not only that. With big log files on tiny shared hosts, some Marketplace
 theme & plugins and some "responsive", 10-sizes-per-image uploads, you can
 quickly produce incredibly heavy log files that could overflow a users
 available disk space.

 >  2. A developer saving a few precious seconds.

 Imo it's not only that. It's also making devs aware of what is possible.

 Replying to [comment:32 grantpalin]:
 > (...) so I'll point out that PHP is shipped with two configuration files
 > (...) Why not do something similar for WordPress' configuration, e.g.

 I see your point and it's valid. My 2 cents: By now we already got an
 example file where the user has to fill the blanks. I'd really not like to
 see three different config files shipped in the root dir. This is error
 prone (renaming the wrong file).

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