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:
Control error display
Three modes for showing errors on screen:
wp-config.php settings (default, non-intrusive)WP_DEBUG_DISPLAY is onErrors 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:
wp-content/)wp-content/debug.log if no path is specifiedRemove the php-error CSS class
When WordPress encounters a PHP error, it adds a php-error class to the <body> 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.
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.