Developer Debug Mode
Toggle WordPress debug mode instantly. No wp-config.php editing needed. Features auto-save, admin bar quick toggle, and debug log viewer.
Use with caution
Developer Debug Mode works, but test it on a staging site before relying on it in 2026. It runs on 50+ sites, is rated 5/5 and was last updated 8 months ago, and scores 47/100 on our health check.
- Small user base (50+ active installs)
- Very few reviews so far
- Only tested up to WordPress 6.9 (latest is 7.1)
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Developer Debug Mode stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| debug | #24 |
| developer-tools | #16 |
| error log | >100 |
| troubleshooting | >100 |
| wp-config | #84 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 1 reviews
About Developer Debug Mode
From the official readme · v1.2.5Description
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.
🎯 The Problem This Plugin Solves
Every WordPress developer knows the pain:
- Something breaks on your site
- You need to enable WP_DEBUG to see the error
- You open FTP/File Manager, find wp-config.php, edit it carefully
- Debug the issue
- Remember to turn debug off before visitors see ugly error messages
- Repeat next time something breaks
Developer Debug Mode eliminates steps 2-5 entirely. Toggle debug on, find the error, toggle off. Done in seconds.
✨ Key Features
One-Click Debug Toggles
Control all six WordPress debug constants from a clean, modern interface:
- WP_DEBUG — Master switch for WordPress debugging
- WP_DEBUG_LOG — Save errors to wp-content/debug.log
- WP_DEBUG_DISPLAY — Show errors on screen (careful on production!)
- SCRIPT_DEBUG — Use unminified core CSS/JS files
- SAVEQUERIES — Log database queries for performance analysis
- WP_DISABLE_FATAL_ERROR_HANDLER — See raw PHP fatal errors instead of recovery mode
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:
- Color-coded entries (fatal, error, warning, notice)
- Search with highlighting
- Auto-refresh option for real-time monitoring
- One-click download and clear
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.
🔧 Perfect For
- Theme developers debugging template issues
- Plugin developers testing new code
- Site administrators troubleshooting problems
- Agencies managing multiple client sites
- Freelancers who need quick debugging without FTP access
- Anyone tired of manually editing wp-config.php
💡 Why Choose Developer Debug Mode?
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
🔒 Built With Security In Mind
- Capability checks ensure only administrators can change settings
- Nonce verification on all AJAX requests
- Automatic wp-config.php backups before every change
- No data sent to external servers
- Clean uninstall removes all plugin data
📚 Debug Constants Explained
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 /wp-content/debug.log. 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.”
🤝 Support & Documentation
Need help? We offer:
- Free Support — Post in the WordPress.org support forum
- Documentation — Visit glimbyte.ie for guides and tutorials
- Express Support — Fast turnaround for urgent issues via glimbyte.ie/support
🌐 Works Great With
- Query Monitor — Use alongside for deeper debugging
- Debug Bar — Compatible with Debug Bar and its add-ons
- Any caching plugin — Clear cache after toggling debug constants
- Managed WordPress hosts — Works on most hosts including Kinsta, WP Engine, SiteGround
Credits
Developed with ❤️ by Glimbyte — WordPress Development & Support.
Special thanks to the WordPress community for feedback and suggestions.
Privacy Policy
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 Glimbyte’s Privacy Policy.
Additional Info
Contribute
Found a bug or have a feature request? We’d love to hear from you!
- Support Forum: wordpress.org/support/plugin/developer-debug-mode
- Website: glimbyte.ie
Translations
Want to help translate Developer Debug Mode into your language? Visit translate.wordpress.org to contribute.
Installation
Automatic Installation (Recommended)
- Go to Plugins → Add New in your WordPress admin
- Search for “Developer Debug Mode”
- Click Install Now then Activate
- Go to Settings → Debug Mode to start debugging
Manual Installation
- Download the plugin ZIP file
- Go to Plugins → Add New → Upload Plugin
- Choose the ZIP file and click Install Now
- Activate the plugin
- Go to Settings → Debug Mode
Requirements
- WordPress 5.0 or higher
- PHP 7.0 or higher
- Write access to wp-config.php (most hosts allow this)
After Activation
- Navigate to Settings → Debug Mode
- You’ll see the current status of all debug constants
- Toggle any switch to enable/disable that constant
- Changes save automatically — no save button needed!
Frequently asked questions
Does this plugin edit my wp-config.php file?
Yes. The plugin modifies wp-config.php to add or update debug constant definitions. This is the same thing you would do manually, just automated and safer because: A backup is created before every change The plugin keeps the 5 most recent backups Changes are validated before saving No risk of syntax errors from manual editing
Is it safe to use on a production/live site?
The plugin itself is completely safe. However, be careful with WP_DEBUG_DISPLAY on production sites — it can expose sensitive error information to visitors. That’s why the plugin shows a frontend warning bar when WP_DEBUG_DISPLAY is active. You’ll never forget to turn it off! For production debugging, we recommend enabling only WP_DEBUG and WP_DEBUG_LOG, then checking the debug.log file.
What if wp-config.php is not writable?
The plugin will show a warning message and disable the toggle switches. You’ll need to: Contact your hosting provider to enable write access, or Temporarily change file permissions to 644 or 664 Some managed WordPress hosts restrict wp-config.php access for security. Contact your host’s support for help.
Can I use this with Query Monitor or Debug Bar?
Absolutely! Developer Debug Mode manages the debug constants, while Query Monitor and Debug Bar provide additional debugging interfaces. They complement each other perfectly.
Will enabling debug mode slow down my site?
WP_DEBUG and WP_DEBUG_LOG have minimal performance impact. WP_DEBUG_DISPLAY can slightly slow page rendering if there are many errors. SAVEQUERIES does add overhead because it stores every database query — disable it when not actively debugging database performance.
How do I view the debug.log file?
Three options: Built-in viewer — Go to Settings → Debug Mode and scroll to the Debug Log Viewer section Direct access — Download from /wp-content/debug.log via FTP Admin bar — Click the debug log link in the admin bar menu
Can I toggle debug from the admin bar?
Yes! As of version 1.2.0, you can click any constant in the admin bar dropdown to toggle it on/off instantly. No need to visit the settings page.
Does it work with WordPress Multisite?
Yes! The plugin works on multisite installations. Each site administrator can manage debug settings for their site. Network-wide settings are not currently supported but planned for a future version.
What happens when I deactivate or uninstall the plugin?
Deactivation: Debug constants remain in wp-config.php at their current values. Uninstall: Plugin options are removed from the database. Debug constants in wp-config.php are NOT removed — we don’t want to accidentally disable debugging you intentionally enabled.
Can I customize which constants are shown?
Not currently, but this is planned for a future version. All six constants are shown by default as they’re the most commonly used for debugging.
The toggles aren’t saving. What’s wrong?
This usually means one of: wp-config.php isn’t writable — Check file permissions JavaScript error — Check browser console for errors Caching — Clear any caching plugins and try again Security plugin conflict — Temporarily disable security plugins to test
Does this work with custom wp-config.php locations?
Yes! The plugin checks both the standard location (WordPress root) and one directory up (common on some hosts).
How do I get support?
Check this FAQ first Search the support forum for similar issues Create a new support topic with details about your problem For urgent issues, contact us at glimbyte.ie/support
Changelog
WordPress.org compliance fixes. Recommended update for all users preparing for plugin directory submission.
1.2.5
- Fixed: Converted email templates to use fully inline styles instead of style blocks (WordPress.org compliance)
- Improved: Email compatibility across all major email clients
1.2.4
- Fixed: Removed Plugin URI to resolve duplicate URI error (Plugin URI and Author URI cannot be the same)
1.2.3
- Fixed: Plugin URI now points to valid URL (https://glimbyte.ie)
- Fixed: Inline styles now use wp_add_inline_style() instead of direct output (WordPress.org compliance)
- Fixed: JavaScript object names now use consistent dev_debug_mode prefix
- Improved: Code compliance with WordPress coding standards
1.2.2
- Fixed: Translators comments now properly placed directly above each __() call with placeholders
- Fixed: Updated “Tested up to” to WordPress 6.9
- Fixed: Shortened plugin short description to comply with 150 character limit
1.2.1
- Fixed: Added missing translators comments for i18n compliance (WordPress plugin check)
1.2.0
- Added: Admin bar quick toggle — click any constant to toggle it directly without visiting settings
- Added: Visual feedback with hover effects and loading states in admin bar
- Added: Real-time notifications when toggling from admin bar
- Added: Cross-tab synchronization for admin bar toggles
- Improved: Admin bar menu now shows “Click to Toggle” header for clarity
- Improved: Better visual distinction between enabled and disabled states
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Developer Debug Mode alternatives
All debug plugins →
FAQ
Developer Debug Mode: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 29, 2026
Is Developer Debug Mode free?
Yes. Developer Debug Mode is free to download and use from the official WordPress.org plugin directory.
Is Developer Debug Mode safe to use in 2026?
Developer Debug Mode works, but test it on a staging site before relying on it in 2026. It runs on 50+ sites, is rated 5/5 and was last updated 8 months ago, and scores 47/100 on our health check.
How many websites use Developer Debug Mode?
Developer Debug Mode is active on 50+ WordPress websites and has been downloaded 595 times since it launched in February 2026. It was downloaded 95 times in the last 30 days.
Does Developer Debug Mode work with WordPress 7.1?
Developer Debug Mode is officially tested up to WordPress 6.9.9, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Developer Debug Mode need?
Developer Debug Mode requires PHP 7.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Developer Debug Mode last updated?
The latest version, 1.2.5, was released on February 6, 2026 (8 months ago).
Who makes Developer Debug Mode?
Developer Debug Mode is developed and maintained by Glimbyte.
What are the best alternatives to Developer Debug Mode?
The most popular alternatives to Developer Debug Mode are WP Crontrol (300K+ installs), Query Monitor (200K+ installs) and Debug Bar (20K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
