Alan Fuller

Fullworks Support Diagnostics makes it easier for plugin developers to troubleshoot issues by automatically collecting diagnostic information and providing powerful debugging tools. It discovers installed plugins and provides a framework for plugin-specific diagnostic data collection.
This plugin should only be activated when instructed by plugin support personnel for diagnostic purposes.
<h4>Key Features</h4>
<ul>
<li>Automatic plugin discovery – Detects compatible plugins with support-config.json files</li>
<li>System information collection – Gathers essential WordPress environment data</li>
<li>wp-config.php debug management – Safely modify debug constants with automatic backups</li>
<li>Shortcode scanning – Identifies shortcodes used across your site</li>
<li>Freemius integration – Collects license status and Freemius state for premium plugins</li>
<li>REST API endpoints – Allows secure remote diagnostics with temporary access links</li>
<li>Sensitive data protection – Masks API keys and other confidential information</li>
<li>Debug log monitoring – Checks and displays the most recent log entries</li>
</ul>
<h4>Debug Management</h4>
The plugin can safely manage debug constants in wp-config.php:
<ul>
<li>Enable/disable WordPress debugging with a single click</li>
<li>Automatically creates backups of wp-config.php before any modifications</li>
<li>Clearly marks all changes with comment blocks for easy identification</li>
<li>Safely removes all modifications when the feature is disabled</li>
<li>Monitors debug log files for recent entries</li>
</ul>
<h4>Security Considerations</h4>
<ul>
<li>All wp-config.php modifications require explicit admin confirmation</li>
<li>Access keys can be regenerated at any time</li>
<li>Temporary access links expire after 24 hours</li>
<li>API keys and sensitive data are masked in diagnostic reports</li>
<li>REST API endpoint can be disabled if not needed</li>
</ul>
<h3>Usage Instructions</h3>
<h4>For Site Owners</h4>
<ol>
<li>Only install when directed by support personnel</li>
<li>Go to Tools → Plugin Support Diagnostics in your WordPress admin</li>
<li>If instructed, enable debug management and select appropriate debug constants</li>
<li>Click “Generate Diagnostic Data”</li>
<li>Share the diagnostic information with support using one of these methods:
<ul>
<li>Copy to clipboard</li>
<li>Download as JSON</li>
<li>Use the temporary direct access link (valid for 24 hours)</li>
</ul>
</li>
<li>When troubleshooting is complete, disable any debug options and consider deactivating the plugin</li>
</ol>
<h4>For Plugin Developers</h4>
To make your plugin compatible with Support Diagnostics, create a <code>support-config.json</code> file in your plugin’s root directory. See the example-support-config.json file included in the plugin for reference.

Fullworks Support Diagnostics

A diagnostic tool that helps plugin developers provide better support by collecting relevant system information and managing debug constants.

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.

Fullworks Support Diagnostics vs Developer Debug Mode