WordPress uses a PHP constant named WP_DEBUG to set whether WordPress is running in a debug mode. For most sites you’ll want to leave WP_DEBUG set to false, which is the default. But there are cases where it comes in handy.

Turning on WP_DEBUG

To turn on debug mode you’ll need to edit the wp-config.php file. This is a WordPress file that contains all of the information to allow WordPress to connect to the database among other things. For the most part we are going to ignore what’s already there because it is possible to break your WordPress site if you enter the wrong information into wp-config.php.

What you’re looking for is a line like the following.

define('WP_DEBUG', false);

Odds are that you won’t find it though. If it’s not there, you can just add the following line. If it is there, change it to match the following line.

define('WP_DEBUG', true);

A couple things to note. First, the line is case sensitive. PHP treats WP_DEBUG and wp_debug and Wp_DeBuG differently, and WordPress expects it all caps. Same is true of true and define. Also make sure the line ends with a semicolon.


Setting WP_DEBUG to true has a couple of effects on ProofBuddy. Most notably there will now be a Debug menu under settings where we put options that are rarely needed, but might be depending on how your server is setup.

Settings menu with WP_DEBUG enabled

ProofBuddy settings menu with WP_DEBUG enabled

The other effect, and one you may not notice, is that WordPress may display non-critical errors. By default WordPress hides non-critical errors, but with WP_DEBUG on they will show. For this reason though you don’t want to leave WP_DEBUG on longer than necessary.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>