Alan Fuller

<p>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.</p>
<p>This plugin should only be activated when instructed by plugin support personnel for diagnostic purposes.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Automatic plugin discovery</strong> – Detects compatible plugins with support-config.json files</li>
<li><strong>System information collection</strong> – Gathers essential WordPress environment data</li>
<li><strong>wp-config.php debug management</strong> – Safely modify debug constants with automatic backups</li>
<li><strong>Shortcode scanning</strong> – Identifies shortcodes used across your site</li>
<li><strong>Freemius integration</strong> – Collects license status and Freemius state for premium plugins</li>
<li><strong>REST API endpoints</strong> – Allows secure remote diagnostics with temporary access links</li>
<li><strong>Sensitive data protection</strong> – Masks API keys and other confidential information</li>
<li><strong>Debug log monitoring</strong> – Checks and displays the most recent log entries</li>
</ul>
<h4>Debug Management</h4>
<p>The plugin can safely manage debug constants in wp-config.php:</p>
<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><strong>Only install when directed by support personnel</strong></li>
<li>Go to Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> 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>
<p>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.</p>


Fullworks Support Diagnostics

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

Yevhen Leonidov

<p>Working with <code>WP_DEBUG</code> enabled often floods the screen with notices and deprecation warnings from third-party plugins and themes – things you neither wrote nor can fix. GLOBUS Debug Control lets you filter out the noise and focus on what actually matters.</p>
<p>All settings are available in <strong>Settings – GLOBUS Debug Control</strong>. The plugin provides eight tabs: Settings, WP_DEBUG, Error Log, Cron Tasks, Transients, Autoloaded, HTTP Log, and Constants. No code editing needed.</p>
<h4>Settings tab</h4>
<p><strong>Choose which errors to see</strong></p>
<p>Turn off specific PHP error types independently:</p>
<ul>
<li>Notices – informational messages that rarely indicate a real problem</li>
<li>Deprecated – warnings about outdated functions, usually from third-party code</li>
<li>Warnings – optional, keep them on if you are actively debugging</li>
<li>Strict – PHP 7 strict standards messages (not applicable in PHP 8+)</li>
</ul>
<p><strong>Control error display</strong></p>
<p>Three modes for showing errors on screen:</p>
<ul>
<li><strong>Inherit</strong> – follows your <code>wp-config.php</code> settings (default, non-intrusive)</li>
<li><strong>On</strong> – always show errors, useful during active development</li>
<li><strong>Off</strong> – hide all errors from screen even if <code>WP_DEBUG_DISPLAY</code> is on</li>
</ul>
<p>Errors are always hidden automatically during AJAX requests, REST API calls, WP-Cron, and WP-CLI, so your API responses stay clean regardless of the display setting.</p>
<p><strong>Error logging</strong></p>
<p>Enable logging to capture errors in a file instead of (or in addition to) showing them on screen:</p>
<ul>
<li>Set a custom log file path (absolute or relative to <code>wp-content/</code>)</li>
<li>Set a maximum log file size (1-100 MB); the file rotates automatically when the limit is reached</li>
<li>Defaults to <code>wp-content/debug.log</code> if no path is specified</li>
</ul>
<p><strong>Remove the php-error CSS class</strong></p>
<p>When WordPress encounters a PHP error, it adds a <code>php-error</code> class to the <code><body></code> tag, which can break your page layout. This option removes it via both CSS and JavaScript so your front-end and admin look normal even in debug mode.</p>
<p><strong>Early error interception (optional)</strong></p>
<p>WordPress loads plugins in alphabetical order. If another plugin throws an error before GLOBUS Debug Control initialises, those errors will not be filtered. Enabling the <strong>MU-plugin dropin</strong> installs a small helper file into <code>wp-content/mu-plugins/</code> that runs before any regular plugin, ensuring your filter settings apply from the very start of the request. The dropin is removed automatically when the plugin is deactivated or uninstalled.</p>
<h4>WP_DEBUG tab</h4>
<p>Toggle the five most important debug constants directly from the admin panel without editing <code>wp-config.php</code>:</p>
<ul>
<li><code>WP_DEBUG</code> – master debug switch</li>
<li><code>WP_DEBUG_LOG</code> – write errors to a log file</li>
<li><code>WP_DEBUG_DISPLAY</code> – show errors on screen</li>
<li><code>SCRIPT_DEBUG</code> – use unminified core JS/CSS</li>
<li><code>SAVEQUERIES</code> – log all database queries</li>
</ul>
<p>The plugin locates your <code>wp-config.php</code> automatically and patches it in place, adding the constant if it is missing or updating the existing value. Commented-out defines and block-comment sections are never touched. The current status of <code>WP_DEBUG</code> is always visible as a badge in the plugin header.</p>
<h4>Error Log tab</h4>
<p>Displays the contents of your <code>debug.log</code> file directly in the admin panel using a CodeMirror editor with line numbers. Lines are color-coded by severity: fatal/parse errors, warnings, notices/deprecations, and cron-related messages. The log is paginated (200 lines per page), supports live polling for new entries, and can be downloaded or cleared with one click. Large log files (over 2 MB) are read from the tail to keep memory usage low.</p>
<h4>Cron Tasks tab</h4>
<p>Lists all scheduled WordPress cron events with hook name, next run time, recurrence interval, and arguments. Summary cards show total events, overdue count, orphaned hooks, and duplicates. Overdue events are highlighted. You can run any event immediately or delete orphaned hooks directly from the table.</p>
<h4>Transients tab</h4>
<p>Displays database-stored WordPress transients from the options table with key name, data size, and expiration time. Transients stored in an external object cache (Redis, Memcached) are not shown. Expired transients are highlighted. You can delete individual transients or purge all expired ones in one click. Summary cards show total count, expired count, and total data size.</p>
<h4>Autoloaded tab</h4>
<p>Lists autoloaded options from <code>wp_options</code> sorted by data size (top 200). Shows the option name and value size. Summary cards display total autoloaded row count and total payload size with warnings when thresholds are exceeded (over 800 KB or over 100 rows). This is a read-only diagnostic view to help identify options that inflate every WordPress request.</p>
<h4>HTTP Log tab</h4>
<p>Captures outgoing WordPress HTTP API requests (<code>wp_remote_get</code>, <code>wp_remote_post</code>, etc.) via the <code>http_api_debug</code> hook. Capturing must be explicitly enabled and stores up to 100 entries (6-hour TTL). Each entry shows the request URL, HTTP method, status code, response time, and transport class. Useful for spotting slow or failing external API calls.</p>
<h4>Constants tab</h4>
<p>Displays all WordPress-related PHP constants defined at runtime, grouped by category: Debug, Performance, Security, Database, Auth and Salts, Paths, and Other WP_* constants. Sensitive values (database password, auth keys, salts) are automatically masked. This is a read-only reference view.</p>


GLOBUS Debug Control

WordPress debug toolkit: filter errors, toggle WP_DEBUG, view error logs, monitor cron, transients, HTTP requests, and more.

Fullworks Support Diagnostics vs GLOBUS Debug Control