Automattic

Donncha O Caoimh (a11n)

This plugin logs the activity of supported plugins to a file, making it easier to figure out why there’s a problem.
If you have been asked to install this plugin because of a support issue then installing this plugin is just like installing any other plugin. Once installed, go to Settings->WP Logger and enable logging. If you have a number of supported plugins enable the one you are interested in.
Developers who want to use this plugin to add logging to their own plugin should see the Developers section of this documentation.
Mark Jaquith’s <a href="https://wordpress.org/extend/plugins/monitor-pages/" rel="ugc">Monitor Pages</a> plugin was used as a template for this plugin. Thanks Mark!
<h4>Developers</h4>
Other plugins can use this plugin to record important events which are then dumped to a log file. Plugins must add the event to a global array in the following way:
<pre><code>$GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = 'Some important event';
</code></pre>
Plugins must also add themselves to a list of enabled plugins. This will make it easier for blog owners to filter out which plugin they want to debug on the settings page. Add and edit the following code so it is executed when the plugin is loaded.
<pre><code>$GLOBALS[ 'wp_log_plugins' ][] = 'name_of_plugin';
</code></pre>
A hypothetical example might be a plugin (let’s call it “Big A”) that uses the output buffer to change the letter “a” to “A”. The events recorded by this might include the following:
<pre><code>$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Created output buffer';
$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Output buffer callback';
$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Replaced a with A in page';
</code></pre>
This plugin takes the “wp_log” array and dumps it to a file in the upload directory of the blog it’s activated on. The file is linked from the plugin settings page and can be deleted on that page too. The file is a simple text file and is not protected in any way so be careful if auth cookies are logged by a plugin.
A “log” function isn’t included but if you want to add one to your plugin check the constant WP_DEBUG_LOG is defined before adding to the log array. If your plugin doesn’t use a class make sure that you call the log function a unique name so it doesn’t conflict with other plugins.
<pre><code>function log( $message ) {
 if ( defined( 'WP_DEBUG_LOG' ) )
 $GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = $message;
}
</code></pre>

WP Debug Logger

A plugin that makes it easy to log code activity to a file.

Lukman Nakib

A comprehensive debugging toolkit for WordPress developers and site administrators. This plugin gives you complete control over WordPress debugging without editing wp-config.php files or using FTP.
<h4>Quick Demo</h4>
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/D4K5zsLnILw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h4>Key Features</h4>
<ul>
<li>WP-CLI Style Terminal: Execute WordPress commands directly from your browser with syntax highlighting and auto-completion</li>
<li>Database Tools: Run SQL queries, view table structures, and optimize your database (super admin only)</li>
<li>Debug Constants Manager: Toggle all WordPress debug constants with a single click</li>
<li>Log Viewer: View, filter, and analyze debug logs with syntax highlighting and error categorization</li>
<li>Query Inspector: Examine database queries with SAVEQUERIES support</li>
<li>Email Notifications: Get alerts when new errors appear in your logs</li>
<li>Safe Mode: Quickly disable all plugins except selected ones for troubleshooting</li>
<li>Custom Log Paths: Set custom log file locations with filter support</li>
</ul>
<h4>Debug Constants Available</h4>
<ul>
<li>WP_DEBUG – Default Value: true – Enables WordPress debug mode</li>
<li>WP_DEBUG_LOG – Default Value: true – Saves all errors to a debug.log file</li>
<li>SCRIPT_DEBUG – Default Value: false – Uses development versions of core JS and CSS files</li>
<li>WP_DEBUG_DISPLAY – Default Value: false – Controls whether debug messages display on screen</li>
<li>SAVEQUERIES – Default Value: false – Saves database queries for analysis</li>
</ul>
<h4>Developer Tools</h4>
<ul>
<li>Terminal Commands: Use WP-CLI style commands like <code>wp core version</code> or <code>wp plugin list</code></li>
<li>Database Explorer: Run SELECT queries and view results in a formatted table</li>
<li>Stack Trace Analysis: Visualize error stack traces for easier debugging</li>
<li>Hook Inspector: View all registered hooks and their callbacks</li>
<li>Environment Detection: Development features are automatically hidden in production</li>
</ul>
<blockquote>
Developer API: Apply custom filters like <code>apply_filters('wp_debuglog_log_file_path', $file);</code> to extend functionality
</blockquote>
Please note: Constant values will be restored on plugin deactivation as it was before activating the plugin.

Debug Log – Manager Tool

Awesome!

Helps us a lot with development :)


My go-to debugging plugin for 500 internal server errors and anything that's trickier to track. Good job.


Super useful


The plugin used to work very well, but with the latest update the debug log cannot be cleaned. This has been reported as a bug 2 months ago with no response and no other update. This is why I'm giving the plugin 2 stars. There are other plugins that work better.


Works but has bugs and bad support


Fantastic plugin with an easy interface for browsing. Thank you so much for making it available for free!


Fantastic & easy to use.

The "Debug Log Config Tool" simplifies debugging. Toggle logging,queries , view levels, clear logs from dashboard.

WP Debug Logger vs Debug Log – Manager Tool