GLOBUS Debug Control
WordPress debug toolkit: filter errors, toggle WP_DEBUG, view error logs, monitor cron, transients, HTTP requests, and more.
Use with caution
GLOBUS Debug Control works, but test it on a staging site before relying on it in 2026. It runs on 50+ sites and was last updated 6 months ago, and scores 46/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 GLOBUS Debug Control stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| cron | >100 |
| debug | #68 |
| error log | >100 |
| transients | >100 |
| wp-config | >100 |
Version adoption
Share of active sites per release.
About GLOBUS Debug Control
From the official readme · v2.2.5Description
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. The plugin provides eight tabs: Settings, WP_DEBUG, Error Log, Cron Tasks, Transients, Autoloaded, HTTP Log, and Constants. No code editing needed.
Settings tab
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 are 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.phpsettings (default, non-intrusive) - On – always show errors, useful during active development
- Off – hide all errors from screen even if
WP_DEBUG_DISPLAYis 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.logif no path is specified
Remove 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 throws an error before GLOBUS Debug Control initialises, those errors will not 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 from the very start of the request. The dropin is removed automatically when the plugin is deactivated or uninstalled.
WP_DEBUG tab
Toggle the five most important debug constants directly from the admin panel without editing wp-config.php:
WP_DEBUG– master debug switchWP_DEBUG_LOG– write errors to a log fileWP_DEBUG_DISPLAY– show errors on screenSCRIPT_DEBUG– use unminified core JS/CSSSAVEQUERIES– log all database queries
The plugin locates your wp-config.php 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 WP_DEBUG is always visible as a badge in the plugin header.
Error Log tab
Displays the contents of your debug.log 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.
Cron Tasks tab
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.
Transients tab
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.
Autoloaded tab
Lists autoloaded options from wp_options 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.
HTTP Log tab
Captures outgoing WordPress HTTP API requests (wp_remote_get, wp_remote_post, etc.) via the http_api_debug 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.
Constants tab
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.
Installation
- Upload the
globus-debug-controlfolder to the/wp-content/plugins/directory. - Activate the plugin through the Plugins menu in WordPress.
- Go to Settings – GLOBUS Debug Control and configure as needed.
Frequently asked questions
Does the plugin require WP_DEBUG to be enabled?
The plugin is always active, but error filtering only takes effect when WP_DEBUG is set to true in wp-config.php. Error display and logging settings work independently of WP_DEBUG. You can toggle WP_DEBUG and related constants from the WP_DEBUG tab without editing any files manually.
Will it hide errors in AJAX or REST API responses?
Yes. Errors are always suppressed from output during AJAX requests, REST API calls, WP-Cron, and WP-CLI regardless of your display settings. This prevents broken JSON responses.
What is the MU-plugin dropin and do I need it?
It is an optional small file installed into wp-content/mu-plugins/. It makes GLOBUS Debug Control run earlier than any regular plugin, so errors thrown during early plugin initialisation are also filtered. Enable it if you see errors from plugins that load before this one. The dropin is removed automatically when the plugin is deactivated or uninstalled.
Where is the log file saved?
By default, errors are logged to wp-content/debug.log. You can set a custom path in the plugin settings. The log file rotates automatically once it exceeds the size limit you set. The Error Log tab lets you read, download, and clear the log directly from the admin panel.
Can I see scheduled cron tasks?
Yes. The Cron Tasks tab lists all registered WordPress cron events with their next run time, interval, and arguments. Overdue events are highlighted. You can run individual events immediately or delete orphaned hooks.
Can I inspect transients and autoloaded options?
Yes. The Transients tab shows all transients with size and expiry info and lets you delete individual entries or purge all expired ones. The Autoloaded tab lists the heaviest autoloaded options so you can identify what inflates your option payload.
What does the HTTP Log tab do?
It captures outgoing HTTP requests made by WordPress core, plugins, and themes. Enable capturing, then reload a page to see which URLs are being called, their status codes, and response times. Up to 100 entries are stored for 6 hours.
Can I use this on a live site?
Yes. The recommended setup for a production site is: suppress all error types, disable error display, enable logging to a file, and keep the php-error class removal active. The diagnostic tabs (Cron Tasks, Transients, Autoloaded, HTTP Log, Constants) are read-only and safe to use at any time.
Changelog
Major update: eight admin tabs including WP_DEBUG toggle, error log viewer, cron monitor, transient manager, autoloaded options inspector, HTTP request logger, and constants viewer.
2.2.5
- Added WP_DEBUG tab: toggle WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG, SAVEQUERIES directly from the admin panel
- WP_DEBUG status indicator badge shown in plugin header
- Added Error Log viewer with color-coded lines, pagination, live polling, download, and one-click clear
- Added Cron Tasks viewer with summary cards, overdue highlighting, immediate run, and orphan cleanup
- Added Transients viewer with size/expiry info, per-row delete, and bulk purge of expired entries
- Added Autoloaded Options viewer showing the heaviest autoloaded rows with size warnings
- Added HTTP Log tab for capturing outgoing WordPress HTTP API requests with status codes and timing
- Added Constants viewer displaying all WP-related PHP constants grouped by category with sensitive value masking
- Plugin settings UI reorganised into eight tabs: Settings, WP_DEBUG, Error Log, Cron Tasks, Transients, Autoloaded, HTTP Log, Constants
- Improved error log rendering for large files (tail-read for files over 2 MB)
- Added nonce verification to log status polling endpoint
- Switched log download to streaming output for lower memory usage
2.2.4
- Replaced inline style/script output with wp_add_inline_style() and wp_add_inline_script()
- Renamed option key from gdc_options to globus_debug_control_options with automatic migration
- Updated Author URI
2.2.3
- Fixed minor bugs
2.2.2
- Removed deprecated load_plugin_textdomain() call (auto-loaded since WP 4.6)
- Improved output escaping
- Added singleton protection
- Added index.php files for directory listing protection
2.2.1
- Fixed minor bugs
2.2.0
- Added optional MU-plugin dropin for early error interception
- Improved log file management
- Added automatic log file rotation
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 GLOBUS Debug Control alternatives
All cron plugins →
FAQ
GLOBUS Debug Control: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 29, 2026
Is GLOBUS Debug Control free?
Yes. GLOBUS Debug Control is free to download and use from the official WordPress.org plugin directory.
Is GLOBUS Debug Control safe to use in 2026?
GLOBUS Debug Control works, but test it on a staging site before relying on it in 2026. It runs on 50+ sites and was last updated 6 months ago, and scores 46/100 on our health check.
How many websites use GLOBUS Debug Control?
GLOBUS Debug Control is active on 50+ WordPress websites and has been downloaded 504 times since it launched in April 2026. It was downloaded 90 times in the last 30 days.
Does GLOBUS Debug Control work with WordPress 7.1?
GLOBUS Debug Control 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 GLOBUS Debug Control need?
GLOBUS Debug Control requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was GLOBUS Debug Control last updated?
The latest version, 2.2.5, was released on April 13, 2026 (6 months ago).
Who makes GLOBUS Debug Control?
GLOBUS Debug Control is developed and maintained by Yevhen Leonidov.
What are the best alternatives to GLOBUS Debug Control?
The most popular alternatives to GLOBUS Debug Control are WP Crontrol (300K+ installs), Advanced Cron Manager (30K+ installs) and Missed Scheduled Posts Publ… (30K+ 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
