DebugBoy
“Safely toggle WordPress debug mode from your dashboard, auto-revert on a timer, and read your debug.log in a clear, color-coded view.“
Debug WordPress without leaving debug mode on by accident
DebugBoy is a WordPress plugin that gives you full control of your site’s debugging constants from a clean admin screen, then switches them back off for you when the session is over. No more editing wp-config.php over FTP, no more forgetting that WP_DEBUG_DISPLAY is still printing file paths to every visitor three weeks later. You turn debugging on, pick how long it should stay on, and get on with finding the problem.
One screen for every debug constant
The Debug Constants tab puts the three constants you reach for most, WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY, front and center, each with a plain-language description of what it does. Four more live in a collapsible Advanced section so they stay out of the way until you need them: SCRIPT_DEBUG, SAVEQUERIES, WP_DISABLE_FATAL_ERROR_HANDLER and CONCATENATE_SCRIPTS. Tick what you want, press Apply, and DebugBoy writes the change into wp-config.php for you.
An explainer at the top of the tab tells you what the plugin is doing and why it matters. Debug output on a live server can expose file paths and error details to anyone who visits, and verbose options like SAVEQUERIES add overhead to every request. DebugBoy treats debug mode as a diagnostic tool, not a default state.
An auto-revert timer that does the remembering for you
This is the feature that sets DebugBoy apart. Before you apply your settings, choose how long debugging should stay active: 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 8 hours, 12 hours or 24 hours. When the time is up, a scheduled WP-Cron event sets every enabled constant back to false automatically. You can also pick Closed to turn everything off right away, or Keep open if you are actively watching a long session and want no automatic revert.
A status bar at the top of the page always tells you whether debug mode is currently on or off. While a timer is running it shows a live countdown and the exact clock time the revert will happen, in your site’s own timezone. A Disable now button lets you end the session early with one click. An indicator in the WordPress admin bar also lets you see at a glance, from any screen in the dashboard, that debugging is active.
The timer runs entirely inside the plugin through WP-Cron. DebugBoy never touches your theme’s functions.php, so switching themes or updating your theme cannot break or bypass it.
Safe edits to wp-config.php, every time
Editing wp-config.php is the riskiest part of debugging, so DebugBoy is built around not breaking it. Before every single write, a timestamped backup of your configuration file is saved to a protected folder inside wp-content, and the 20 most recent backups are kept. That folder is locked down against direct web access.
All of DebugBoy’s changes live inside a clearly marked block in wp-config.php, so you can always see exactly what the plugin added. If your file already defines one of these constants elsewhere, DebugBoy comments the original line out instead of deleting it, so nothing is lost and the conflict cannot silently override your choice. If wp-config.php is not writable by the web server, the plugin tells you plainly on the settings page and makes no changes until permissions allow it.
When you uninstall the plugin, it removes its own block, restores any lines it had commented out, and leaves your site in a clean, debug-off state.
A debug log viewer you will actually want to read
Switch to the Debug Log tab and DebugBoy reads your debug.log file and presents it in two ways, each with its own strengths.
The Stacked view groups entries by where they came from: plugins, themes, must-use plugins, WordPress core or other. Each group is an accordion that opens to show its individual entries, with a count so you can see which plugin is making the most noise. Entries are color coded by severity, from fatal errors and warnings to deprecations, notices and general info, and multi-line stack traces are folded back into a single readable entry instead of being scattered across the file.
The Raw view is a dark, terminal-style console with the same color-coded levels, for when you want the log exactly as it was written. It stretches to the bottom of your screen rather than trapping you in a tiny scrolling box.
Smarter blame, fewer wild goose chases
A lot of WordPress notices point at core files even when a plugin or theme is the real cause. The most common example is the “translation loading triggered too early” warning, which fires inside WordPress itself but is actually caused by whichever plugin or theme loaded its text domain at the wrong moment. DebugBoy reads the text domain named in the message and attributes the entry to the right plugin or theme, so you are not left chasing core.
Copy, refresh and clear with one click
Every entry has its own Copy button, so you can paste a single error into a support ticket or a message to a plugin developer without selecting text by hand. A Copy all button grabs the whole log, Refresh pulls in the latest entries, and Clear log empties the file when you are done. Timestamps are shown in your site’s configured timezone and date format rather than the server’s raw log time, so the times you see match the times you remember things happening.
Built to match the way you work: dark mode, docs and changelog
DebugBoy ships with a polished, branded admin interface. A dark mode toggle in the header switches the whole screen to a dark theme, and your choice is saved to your WordPress user profile, so it follows you across devices and browsers instead of resetting every time you clear your cache. Dark mode only affects DebugBoy’s own screen, so the rest of your WordPress dashboard stays exactly as it was.
A Documentation button opens a searchable help panel with sections for getting started, the debug constants, the auto-revert timer, the log viewer, backups and safety, and dark mode. Type a few words and the panel filters instantly to the matching topics. A Changelog button shows the full version history in a tidy overlay, with the latest release dated at the top.
Made for developers, agencies and site owners
If you build and maintain WordPress sites for a living, DebugBoy turns a fiddly, risky chore into a routine one. Agencies can hand a client a safe way to capture an error without giving them file access. Developers can switch on SAVEQUERIES for an hour of performance profiling and trust it to turn itself off. Site owners troubleshooting a white screen can enable logging, reproduce the issue and read the result in plain, organized language.
Requirements and a smooth switch from WP Debug
DebugBoy needs WordPress 5.8 or later and PHP 7.4 or later, and it needs wp-config.php to be writable by the web server while you make changes. It lives in its own top-level item in the admin menu, with its own icon, so it is always one click away.
If you used the earlier release of this plugin under the name WP Debug, DebugBoy picks up where it left off. Any leftover block from the old plugin in your wp-config.php is detected and cleaned up automatically the first time you apply settings, so stale values can never quietly override your new ones. Deactivate and remove the old plugin first, install DebugBoy, and you are ready to go.
Turn debugging on when you need it, and let DebugBoy turn it off
Debugging is essential, but leaving it running is a risk. DebugBoy gives you the tools to investigate quickly and the safety net to make sure the investigation ends cleanly. Install it, set a timer, and find the problem.
Get it now.
License:
You can use this plugin on as many sites as you want, but future updates are not included.
Free
Other products