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

Debug Log Manager Tool is a debug log viewer and WP_DEBUG manager for WordPress. Read, search, group, and clear <code>wp-content/debug.log</code> from inside wp-admin; toggle WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG, and SAVEQUERIES from explicit UI controls instead of editing <code>wp-config.php</code>; capture the last fatal error during shutdown; and review slow database queries with their stack trace. Useful as a lightweight alternative to Query Monitor or Debug Bar when you mainly need a clean debug.log reader and explicit debug-constant control.
The plugin focuses on safe first-run behavior: activation does not automatically turn debug mode on, deactivation does not automatically turn it off, and existing debug constants or custom log paths are preserved until you choose to change them.
Use it to inspect the current debug log, search and group log entries, copy useful error details, and make explicit debug configuration changes from the WordPress admin when needed. Advanced tools such as terminal commands, database inspection, Safe Mode, and notifications are available as optional helpers.
<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>Safe First Run: Activating the plugin does not automatically change WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG, SAVEQUERIES, or existing log paths.</li>
<li>Explicit Debug Controls: Review current debug constant values and update them only through intentional UI actions.</li>
<li>Modern Debug Log Viewer: View, search, filter, group, copy, and clear debug log entries from a compact WordPress admin interface.</li>
<li>Readable Timeline Rows: Scan log entries with severity labels, occurrence counts, plugin/source hints, exact timestamps, and copy-as-JSON actions.</li>
<li>Stack Trace Analysis: Format PHP stack traces and database call chains so long fatal errors are easier to read.</li>
<li>Last Fatal Snapshot: Capture the latest fatal error during shutdown and show it in the log screen when wp-admin is available again.</li>
<li>Large Log File Preview: Open the current debug log file inside a modal and safely read the latest 1 MB of large files.</li>
<li>Smooth Upgrade Behavior: Upgrades preserve existing constants and custom debug log locations instead of replacing your current configuration.</li>
<li>Query Inspector: Optionally examine database queries when SAVEQUERIES is enabled, including SQL, caller, execution time, and stack trace details.</li>
<li>WP-CLI Style Terminal: Optionally run guarded WordPress-style commands directly from the browser with command history and auto-completion.</li>
<li>Terminal Settings: Enable or disable terminal access and database commands from a dedicated settings screen.</li>
<li>Safe Mode: Optionally isolate plugin conflicts by keeping selected plugins active and restoring the previous state when Safe Mode is turned off.</li>
<li>Email Notifications: Optionally configure notification email settings, daily summaries, and test email delivery for debug activity.</li>
<li>Admin Bar Debug Toggle: Quickly review and change WP_DEBUG from the WordPress admin bar when you explicitly choose to.</li>
<li>Dashboard Widget: See recent debug log activity from the WordPress dashboard.</li>
<li>Custom Log Path Support: Keep existing custom log paths and use filters to customize the debug log location.</li>
<li>Hardened Admin Routes: AJAX actions use nonce and capability checks, with guarded file path handling for debug log access.</li>
</ul>
<h4>Debug Constants Available</h4>
These constants can be reviewed and changed from the plugin UI. The plugin does not change them on activation or deactivation.
<ul>
<li>WP_DEBUG – Enables WordPress debug mode</li>
<li>WP_DEBUG_LOG – Saves errors to the configured debug log destination</li>
<li>SCRIPT_DEBUG – Uses development versions of core JS and CSS files</li>
<li>WP_DEBUG_DISPLAY – Controls whether debug messages display on screen</li>
<li>SAVEQUERIES – Saves database queries for analysis</li>
</ul>
<h4>Developer Tools</h4>
<ul>
<li>Terminal Commands: Optionally use WP-CLI style commands like <code>wp core version</code> or <code>wp plugin list</code></li>
<li>Database Explorer: Optionally 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>
<li>Copy JSON: Copy structured log entries for support tickets or developer handoff</li>
<li>File Viewer: Inspect the debug log file without leaving the WordPress admin screen</li>
</ul>
<blockquote>
Developer API: Use filters like <code>wp_dlct_log_file_path</code> and <code>dlct_debug_file_path</code> to customize log path behavior.
</blockquote>
Please note: Configuration changes are made only by explicit UI actions. Deactivating the plugin does not automatically restore, remove, enable, or disable WordPress debug constants.

Debug Log Manager Tool

Awesome!

Helps us a lot with development :)

it's exactly what i am after for. instead of connecting to ftp, opening wp-config.php, editing the constants, saving, uploading, reloading site, opening debug.log and deleting it and so on … you simple enable the toggle and look into the logs right in wordpress with nice styling so you can easily distinguish between warning and errors. 
in the future i would like to see more toggles for instance for WP_DEBUG_DISPLAY. for some reason this is missing?! 

simple but good


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


Super useful


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


Fantastic & easy to use.


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.



--- EDIT ---



Recently I tested the plugin again and it has improved by a lot. I see new functions and - so far - zero bugs. Well done. I improve my rating. Keep up the good work.


Much improved over time


Using this plugin for more than 3 years, and its my favourite one to debug!


Great plugin

Read, search, and clear WordPress debug logs from wp-admin. Toggle WP_DEBUG and inspect errors without FTP.

WP Debug Logger vs Debug Log Manager Tool