Glimbyte

Stop editing wp-config.php every time you need to debug your WordPress site.
Developer Debug Mode lets you toggle all WordPress debug constants directly from your dashboard with beautiful toggle switches. Changes save automatically — no clicking save buttons, no FTP access needed, no risk of syntax errors in your config file.
<h4>🎯 The Problem This Plugin Solves</h4>
Every WordPress developer knows the pain:
<ol>
<li>Something breaks on your site</li>
<li>You need to enable WP_DEBUG to see the error</li>
<li>You open FTP/File Manager, find wp-config.php, edit it carefully</li>
<li>Debug the issue</li>
<li>Remember to turn debug off before visitors see ugly error messages</li>
<li>Repeat next time something breaks</li>
</ol>
Developer Debug Mode eliminates steps 2-5 entirely. Toggle debug on, find the error, toggle off. Done in seconds.
<h4>✨ Key Features</h4>
One-Click Debug Toggles 
Control all six WordPress debug constants from a clean, modern interface:
<ul>
<li>WP_DEBUG — Master switch for WordPress debugging</li>
<li>WP_DEBUG_LOG — Save errors to wp-content/debug.log</li>
<li>WP_DEBUG_DISPLAY — Show errors on screen (careful on production!)</li>
<li>SCRIPT_DEBUG — Use unminified core CSS/JS files</li>
<li>SAVEQUERIES — Log database queries for performance analysis</li>
<li>WP_DISABLE_FATAL_ERROR_HANDLER — See raw PHP fatal errors instead of recovery mode</li>
</ul>
Admin Bar Quick Toggle (New in 1.2.0!) 
Toggle any debug constant directly from the WordPress admin bar — no need to visit the settings page. Perfect for quick debugging sessions.
Built-in Debug Log Viewer 
View, search, download, and clear your debug.log without leaving WordPress:
<ul>
<li>Color-coded entries (fatal, error, warning, notice)</li>
<li>Search with highlighting</li>
<li>Auto-refresh option for real-time monitoring</li>
<li>One-click download and clear</li>
</ul>
Auto-Save Technology 
Changes save instantly as you toggle. No save button, no page refresh, no waiting.
Frontend Debug Warning 
A tasteful notification bar appears when WP_DEBUG_DISPLAY is active, reminding you to turn it off before visitors see error messages.
Cross-Tab Synchronization 
Toggle debug in one browser tab and watch other open tabs update instantly.
Automatic Backups 
Every change creates a backup of wp-config.php. The plugin keeps the 5 most recent backups, so you can always recover if something goes wrong.
<h4>🔧 Perfect For</h4>
<ul>
<li>Theme developers debugging template issues</li>
<li>Plugin developers testing new code</li>
<li>Site administrators troubleshooting problems</li>
<li>Agencies managing multiple client sites</li>
<li>Freelancers who need quick debugging without FTP access</li>
<li>Anyone tired of manually editing wp-config.php</li>
</ul>
<h4>💡 Why Choose Developer Debug Mode?</h4>
Unlike other debug plugins, we focus on user experience:
✅ Instant toggles — No save buttons, changes apply immediately 
✅ Visual feedback — Clear status indicators show exactly what’s enabled 
✅ Admin bar access — Toggle debug from anywhere in WordPress 
✅ Production-safe — Frontend warnings prevent accidentally exposing errors 
✅ Modern design — Beautiful UI that fits naturally in your dashboard 
✅ Lightweight — No bloat, loads only where needed
<h4>🔒 Built With Security In Mind</h4>
<ul>
<li>Capability checks ensure only administrators can change settings</li>
<li>Nonce verification on all AJAX requests</li>
<li>Automatic wp-config.php backups before every change</li>
<li>No data sent to external servers</li>
<li>Clean uninstall removes all plugin data</li>
</ul>
<h4>📚 Debug Constants Explained</h4>
Not sure what each constant does? Here’s a quick guide:
WP_DEBUG 
The master switch. When enabled, WordPress will display PHP errors, notices, and warnings. Required for the other debug constants to work.
WP_DEBUG_LOG 
Saves all debug messages to <code>/wp-content/debug.log</code>. Essential for debugging issues that happen in the background (AJAX, cron jobs, REST API).
WP_DEBUG_DISPLAY 
Shows errors directly on your web pages. Useful during development but never enable on production — it can expose sensitive information to visitors.
SCRIPT_DEBUG 
Forces WordPress to use the development versions of core CSS and JavaScript files instead of minified versions. Helpful when debugging scripts.
SAVEQUERIES 
Stores database queries in a global array for later analysis. Useful for identifying slow queries but adds overhead — disable when not needed.
WP_DISABLE_FATAL_ERROR_HANDLER 
Disables WordPress’s “recovery mode” so you see the actual PHP fatal error instead of “There has been a critical error on this website.”
<h4>🤝 Support & Documentation</h4>
Need help? We offer:
<ul>
<li>Free Support — Post in the <a href="https://wordpress.org/support/plugin/developer-debug-mode/" rel="ugc">WordPress.org support forum</a></li>
<li>Documentation — Visit <a href="https://glimbyte.ie" rel="nofollow ugc">glimbyte.ie</a> for guides and tutorials</li>
<li>Express Support — Fast turnaround for urgent issues via <a href="https://glimbyte.ie/support" rel="nofollow ugc">glimbyte.ie/support</a></li>
</ul>
<h4>🌐 Works Great With</h4>
<ul>
<li>Query Monitor — Use alongside for deeper debugging</li>
<li>Debug Bar — Compatible with Debug Bar and its add-ons</li>
<li>Any caching plugin — Clear cache after toggling debug constants</li>
<li>Managed WordPress hosts — Works on most hosts including Kinsta, WP Engine, SiteGround</li>
</ul>
<h3>Credits</h3>
Developed with ❤️ by <a href="https://glimbyte.ie" rel="nofollow ugc">Glimbyte</a> — WordPress Development & Support.
Special thanks to the WordPress community for feedback and suggestions.
<h3>Privacy Policy</h3>
Developer Debug Mode does not collect, store, or transmit any personal data. All settings are stored locally in your WordPress database and wp-config.php file.
The optional support contact form (available in the plugin settings) sends data directly to Glimbyte’s support team. This data is handled according to <a href="https://glimbyte.ie/privacy" rel="nofollow ugc">Glimbyte’s Privacy Policy</a>.
<h3>Additional Info</h3>
<h4>Contribute</h4>
Found a bug or have a feature request? We’d love to hear from you!
<ul>
<li>Support Forum: <a href="https://wordpress.org/support/plugin/developer-debug-mode/" rel="ugc">wordpress.org/support/plugin/developer-debug-mode</a></li>
<li>Website: <a href="https://glimbyte.ie" rel="nofollow ugc">glimbyte.ie</a></li>
</ul>
<h4>Translations</h4>
Want to help translate Developer Debug Mode into your language? Visit <a href="https://translate.wordpress.org/projects/wp-plugins/developer-debug-mode/" rel="nofollow ugc">translate.wordpress.org</a> to contribute.

Developer Debug Mode


Well-designed plugin! Minimalist UI, perhaps a bit dated, but performs its task very well.


Amazing

Toggle WordPress debug mode instantly. No wp-config.php editing needed. Features auto-save, admin bar quick toggle, and debug log viewer.

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.

Developer Debug Mode vs Debug Log Manager Tool