How to set up error logging in WordPress

Enabling WP_DEBUG mode is a key step to troubleshoot WordPress website errors. First, change define('WP_DEBUG', false); to define('WP_DEBUG', true); in wp-config.php to enable debug mode. If you need to record errors instead of displaying them on the page, add define('WP_DEBUG_LOG', true); the error log will be saved in wp-content/debug.log. These settings should be turned off after troubleshooting is completed. Secondly, plug-ins such as WP Debugging or Error Log Monitor can be used to simplify management, which provide click-to-click activation, email notification and other functions. In addition, server-level logs such as /var/log/apache2/error.log can capture serious errors that cannot be recorded by WordPress, but their content is more technical and requires further analysis. Finally, the log itself is not a solution, but can significantly speed up the troubleshooting process according to the file path and line number positioning problems in the error message, such as PHP parsing errors, fatal errors, or undefined function calls.

When things go wrong on a WordPress site, knowing how to set up error logging can save you hours of frustration. It's one of the most straightforward ways to catch issues early and understand what's really going wrong behind the scenes.

Enable WP_DEBUG in wp-config.php

The first step is to turn on WordPress' built-in debugging mode. This doesn't log errors by default but enables them to be displayed or recorded.

To do this, open your wp-config.php file and look for a line that says:

 define('WP_DEBUG', false);

Change it to:

 define('WP_DEBUG', true);

If you want to log errors to a file instead of showing them on the screen (which is better for live sites), also add:

 define('WP_DEBUG_LOG', true);

This writes errors into a file located at wp-content/debug.log .

Pro tip: Don't forget to disable these settings after troubleshooting, especially on production sites.

Use a Plugin for Simpler Management

If editing configuration files feels risky or confusing, there are plugins that simplify error logging and reporting.

Some popular options include:

• WP Debugging by Delicious Brains – Sets up debug modes and logs with just a few clicks.
• Error Log Monitor – Watches your site and alerts you when new errors appear.

Plugins like these often come with extra features like email notifications or easier-to-read formatting. They're especially helpful if you manage multiple WordPress sites or aren't comfortable working directly with code.

Check Server-Level Logs

Sometimes WordPress won't catch everything, especially if the issue happens before WordPress loads — like during a fatal error or PHP syntax problem.

In those cases, server-level logs are your best bet. These are usually found in your hosting control panel under sections like “Error Logs” or “Raw Access Logs.” If you're on a VPS or managed hosting, you might need to check via SSH in locations like /var/log/apache2/error.log or similar, depending on your server setup.

These logs tend to be more technical, so don't worry if they look dense — just copy and paste any unfamiliar lines into a search engine or share them with someone who knows PHP.

Know What to Do With the Errors

Once you start seeing errors, the next challenge is interpreting them. Common ones include:

• PHP Parse error : Usually a typo or missing semicolon in a theme or plugin file.
• Fatal error : Often means a function was called that doesn't exist — maybe a plugin conflict or outdated code.
• Call to undefined function : Happens when a theme or plugin assumes another plugin is active.

Use the file path and line number included in the error message to locate where the problem is happening. From there, you can either fix the code yourself or temporarily deactivate the related plugin or theme to get your site back online.

Just remember — error logs are tools, not fixes. But they point you in the right direction faster than guessing.

Basically that's it.

The above is the detailed content of How to set up error logging in WordPress. For more information, please follow other related articles on the PHP Chinese website!