The Lodge is members-only design/dev videos and Office Hours.

Next Office Hours Session: "Programming Fundamentals" Dec 02 - 2:00 PM Eastern

Turn on WordPress Error Reporting

Last updated on:

Comment out the top line there, and add the rest to your wp-config.php file to get more detailed error reporting from your WordPress site. Definitely don't do this live, do it for local development and testing.

// define('WP_DEBUG', false);

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);


  1. Rakshit
    Permalink to comment#

    Nice one Chris. Thanks.

  2. geopaL
    Permalink to comment#

    for a live website I would recommend:

    define('WP_DEBUG', false);
    @ini_set('error_log','phperrors.log'); // path to server-writable log file

    don’t forget to drop a phperrors.log file inside your remote directory with write permissions

    • Willem-Siebe Spoelstra
      Permalink to comment#

      What does make you code any different then:

      define('WP_DEBUG', true);
      define('WP_DEBUG_LOG', true);
      define('WP_DEBUG_DISPLAY', false);


  3. sagalbot

    Not sure where the errors get reported to with this turned on.. is there a log file somewhere?

    • sagalbot

      Answered my own question on the codex.

      * This will log all errors notices and warnings to a file called debug.log in
      * wp-content (if Apache does not have write permission, you may need to create
      * the file first and set the appropriate permissions (i.e. use 666) )
      define(‘WP_DEBUG’, true);
      define(‘WP_DEBUG_LOG’, true);
      define(‘WP_DEBUG_DISPLAY’, false);

  4. Alice
    Permalink to comment#

    I need your help when I log in my dashboard is a blank page. I tried to rename my file via FTP using Filezilla but nothing is coming up. Do you have any advices for me. Thanks you.

  5. SoniNow
    Permalink to comment#


    you may try plugin to Debug all issues in WordPress site. and you not need to edit php code in wp-config file.

    • Jim Kyle
      Permalink to comment#

      SoniNow: Your “debug” plugin seems like the ideal solution to my own need, but I’ve not been able to get it to work. Initially it made it impossible to access my test site at all, but restoring config.php from the backup copy solved that and I discovered that the 0600 permission with which it wrote the changed config.php file prevented my server (on localhost) from accessing it at all. This might be what caused Alice’s situation. Changing the permission to 0664 eliminated the login problem but the plugin still failed under WordPress 4.3…

  6. Willem-Siebe Spoelstra
    Permalink to comment#

    Hi, I don’t understand the advice:

    Definitely don’t do this live, do it for local development and testing.

    I understand you don’t want to ‘show’ the errors to public and for that you define WP_DEBUG_DISPLAY to false. But why is it bad practice to ‘log’ the errors to a log file?

    Kind regards,


Leave a Comment

Posting Code

We highly encourage you to post problematic HTML/CSS/JavaScript over on CodePen and include the link in your post. It's much easier to see, understand, and help with when you do that.

Markdown is supported, so you can write inline code like `<div>this</div>` or multiline blocks of code in in triple backtick fences like this:

  function example() {
    element.innerHTML = "<div>code</div>";

There's a whole bunch of content on CSS-Tricks.

Search for Stuff   •   Browse the Archives

Get the Newsletter ... or get the RSS feed