Andy Fragen

This plugin sets the following debug constants in <code>wp-config.php</code> on plugin activation and removes them on plugin deactivation. Any errors will result in a PHP Exception being thrown. Debug constants per <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/" rel="nofollow ugc">Debugging in WordPress</a>.
Default settings:
<pre><code>define( 'WP_DEBUG_LOG', true );
define( 'SCRIPT_DEBUG', true );
define( 'SAVEQUERIES', true );
</code></pre>
  
 @ini_set( ‘display_errors’, 1 ); is set when the plugin is active. <code>WP_DEBUG</code> is set to true when the plugin is first run, thereafter it can be turned off in the Settings.
The Settings page allows the user to set the following.
<pre><code>define( 'WP_DEBUG', true ); // Default on initial plugin installation.
define( 'WP_DEBUG_DISPLAY', false ); // Default when not declared is true.
define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); // WordPress 5.2 WSOD Override.
</code></pre>
When the plugin is deactivated best efforts are made to re-add pre-existing constants to their former state. When the plugin is activated the default settings and any saved settings are restored.
This plugin uses the <a href="https://github.com/wp-cli/wp-config-transformer" rel="nofollow ugc">wp-cli/wp-config-transformer</a> command for writing constants to <code>wp-config.php</code>.
<a href="https://github.com/norcross/debug-quick-look" rel="nofollow ugc">Debug Quick Look</a> from Andrew Norcross is included with this plugin to assist in reading the debug.log file. If you already have this plugin installed you should delete it when WP Debugging is not active.
<a href="https://wordpress.org/plugins/query-monitor/" rel="ugc">Query Monitor</a> and <a href="https://wordpress.org/plugins/debug-bar/" rel="ugc">Debug Bar</a> plugins are optional dependencies to aid in debugging and troubleshooting. The notice for installation will recur 45 days after being dismissed.
If you have a non-standard location for your <code>wp-config.php</code> file you can use the filter <code>wp_debugging_config_path</code> to return the file path for your installation.
The filter <code>wp_debugging_add_constants</code> allows the user to add constants to <code>wp-config.php</code>.
The filter returns an array where the key is the name of the constant and the value is an array of data containing the value as a string and a boolean to indicate whether or not the value should be passed without quotes.
<pre><code>$my_constants = [
 'my_test_constant' =>
 [
 'value' => 'abc123',
 'raw' => false,
 ],
 'another_test_constant' => [ 'value' => 'true' ],
];
</code></pre>
The <code>value</code> option contains the constant’s value as a string.
The <code>raw</code> option means that instead of placing the value inside the config as a string it will become unquoted. The default is <code>true</code>. Set as <code>false</code> for non-boolean values.
Example:
<pre><code>add_filter(
 'wp_debugging_add_constants',
 function( $added_constants ) {
 $my_constants = [
 'my_test_constant' => [
 'value' => '124xyz',
 'raw' => false,
 ],
 'another_test_constant' => [ 'value' => 'true' ],
 ];
 return array_merge( $added_constants, $my_constants );
 },
 10,
 1
);
</code></pre>
This will create the following constants.
<pre><code>define( 'MY_TEST_CONSTANT', '124xyz' );
define( 'ANOTHER_TEST_CONSTANT', true );
</code></pre>
<h3>Development</h3>
PRs are welcome against the <a href="https://github.com/afragen/wp-debugging" rel="nofollow ugc">develop branch on GitHub</a>.

WP Debugging

This helps me support customers and get better debugging information about errors happening on their site without having to ask for sensitive login info. Simple and does a great job, I've used it or recommended it a dozen times in the last month.

Great support tool

I can't tell you the number of times I've had to handle a support request that involved a white screen. Thank you, @afragen, for building this awesome tool to help define constants for a file that isn't easily accessible without passing around credentials.

Super Handy!

Thanks for the useful plugin, we're going to start recommending this to our customers.

Useful Plugin

Thank you for this useful and beautiful plugin, helps me a lot.

Very useful

Quick access to the log files speeds up development!

Great plugin

With this plugin it's at last possible to debug a remote site wihtout having access to the cpanel!

Very useful!


Every time I come across an obscure problem on WordPress sites, I start looking for it by installing this plugin.Thanks to the developers for a great tool!


Perfect tool for debug.

Yet another one of your plugins that I love and use all the time!  Thank you.  (Side note: is there a place to buy you a coffee or donate for your time?)

Another great debugging plugin


I've been using the WP Debugging plugin since 2024, and it has been a lifesaver. The error log feature alone helped me track down several issues that would have taken hours to find manually.



The fact that it integrates with Query Monitor is a nice bonus too. If you do any WordPress development or troubleshooting, just install this plugin. Five stars, no hesitation.


Absolutely essential for debugging – saved me countless times!

A support/troubleshooting plugin for WordPress.

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!


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

WP Debugging vs Debug Log Manager Tool