Grow your CSS skills. Land your dream job.

Last updated on:

Turn on WordPress Error Reporting

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

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

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

Leave a Comment

Posting Code

Markdown is supported in the comment area, so you can write inline code in backticks like `this` or multiline blocks of code in in triple backtick fences like ```this```. You don't need to escape code in backticks, Markdown does that for you.

Sadly, it's kind of broken. WordPress only accepts a subset of HTML in comments, which makes sense, because certainly some HTML can't be allowed, like <script> tags. But this stripping happens before the comment is processed by Markdown (via Jetpack). It seems to me that would be reversed, because after Markdown processes code in backticks, it's escaped, thus safe. If you think you can fix this issue, get in touch!

If you need to make sure the code (typically HTML) you post absolutely posts correctly, escape it and put it within <pre><code> tags.

Current ye@r *

*May or may not contain any actual "CSS" or "Tricks".