外掛標籤
開發者團隊
原文外掛簡介
Working with WP_DEBUG 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.
All settings are available in Settings → GLOBUS Debug Control. No code editing needed.
Choose which errors to see
Turn off specific PHP error types independently:
Notices – informational messages that rarely indicate a real problem
Deprecated – warnings about outdated functions, usually from third-party code
Warnings – optional, keep them on if you’re actively debugging
Strict – PHP 7 strict standards messages (not applicable in PHP 8+)
Control error display
Three modes for showing errors on screen:
Inherit – follows your wp-config.php settings (default, non-intrusive)
On – always show errors, useful during active development
Off – hide all errors from screen even if WP_DEBUG_DISPLAY is on
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.
Error logging
Enable logging to capture errors in a file instead of – or in addition to – showing them on screen:
Set a custom log file path (absolute or relative to wp-content/)
Set a maximum log file size (1–100 MB); the file rotates automatically when the limit is reached
Defaults to wp-content/debug.log if no path is specified
Remove the php-error CSS class
When WordPress encounters a PHP error, it adds a php-error class to the
Early error interception (optional)
WordPress loads plugins in alphabetical order. If another plugin (such as Elementor, WooCommerce, or any “A…” plugin) throws an error before GLOBUS Debug Control initializes, those errors won’t be filtered. Enabling the MU-plugin dropin installs a small helper file into wp-content/mu-plugins/ that runs before any regular plugin – ensuring your filter settings apply to all PHP errors from the very start of the request.
