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

WordPress Trac noreply at wordpress.org
Mon Jun 16 08:18:38 UTC 2014


#28551: Add Better Debugging Documentation Into wp-config.php
-------------------------------+-----------------------------
 Reporter:  philiparthurmoore  |      Owner:
     Type:  enhancement        |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  General            |    Version:
 Severity:  normal             |   Keywords:
  Focuses:  docs               |
-------------------------------+-----------------------------
 WordPress has a number of fantastic constants available to it to assist
 with debugging, specifically `WP_DEBUG`, `WP_DEBUG_DISPLAY`,
 `WP_DEBUG_LOG`, and `SCRIPT_DEBUG`. There are more, to be sure, but these
 alone go a long way to making sure that publicly released themes and
 plugins are relatively sound.

 I suggest that `WP_DEBUG_DISPLAY`, `WP_DEBUG_LOG`, and `SCRIPT_DEBUG` are
 added into `wp-config.php` in the same manner that `WP_DEBUG` has been
 added into `wp-config.php`, with well-documented usage notes. As it stands
 now, it seems like the barrier to entry into debugging WordPress correctly
 is too high (seems, at least), leading new developers to release buggy
 plugins and themes.

 I do [https://gist.github.com/philiparthurmoore/d13a56c3006bd52554dd
 something like this]. I'm sure there's a better way to do this, and a
 better way to word things, but the sentiment is that it'd be very useful
 to put something like this inside of WordPress' config file.

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


More information about the wp-trac mailing list