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.<\/p>","2.2.0":"
Added optional MU-plugin dropin to catch errors from plugins that load before GLOBUS Debug Control.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3501690,"resolution":"128x128","location":"assets","locale":""},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3501690,"resolution":"256x256","location":"assets","locale":""}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.2.4","2.2.5"],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[4567,94,14925,12113,19330],"plugin_category":[59],"plugin_contributors":[250136],"plugin_business_model":[],"class_list":["post-295328","plugin","type-plugin","status-publish","hentry","plugin_tags-cron","plugin_tags-debug","plugin_tags-error-log","plugin_tags-transients","plugin_tags-wp-config","plugin_category-utilities-and-tools","plugin_contributors-globusstudio","plugin_committers-globusstudio"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/globus-debug-control\/assets\/icon-128x128.png?rev=3501690","icon_2x":"https:\/\/ps.w.org\/globus-debug-control\/assets\/icon-256x256.png?rev=3501690","generated":false},"screenshots":[],"raw_content":"\n
Working with All settings are available in 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>\n\n Choose which errors to see<\/strong><\/p>\n\n Turn off specific PHP error types independently:<\/p>\n\n Control error display<\/strong><\/p>\n\n Three modes for showing errors on screen:<\/p>\n\n 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>\n\n Error logging<\/strong><\/p>\n\n Enable logging to capture errors in a file instead of (or in addition to) showing them on screen:<\/p>\n\n Remove the php-error CSS class<\/strong><\/p>\n\n When WordPress encounters a PHP error, it adds a Early error interception (optional)<\/strong><\/p>\n\n 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<\/strong> installs a small helper file into Toggle the five most important debug constants directly from the admin panel without editing The plugin locates your Displays the contents of your 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>\n\n 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>\n\n Lists autoloaded options from Captures outgoing WordPress HTTP API requests ( 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>\n\n\n The plugin is always active, but error filtering only takes effect when 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.<\/p><\/dd>\n It is an optional small file installed into By default, errors are logged to Yes. The Cron Tasks<\/strong> 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.<\/p><\/dd>\n Yes. The Transients<\/strong> tab shows all transients with size and expiry info and lets you delete individual entries or purge all expired ones. The Autoloaded<\/strong> tab lists the heaviest autoloaded options so you can identify what inflates your option payload.<\/p><\/dd>\n 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.<\/p><\/dd>\n Yes. The recommended setup for a production site is: suppress all error types, disable error display, enable logging to a file, and keep the 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>\n\nSettings tab<\/h4>\n\n
\n
\n
wp-config.php<\/code> settings (default, non-intrusive)<\/li>\nWP_DEBUG_DISPLAY<\/code> is on<\/li>\n<\/ul>\n\n\n
wp-content\/<\/code>)<\/li>\nwp-content\/debug.log<\/code> if no path is specified<\/li>\n<\/ul>\n\nphp-error<\/code> class to the <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>\n\nwp-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>\n\nWP_DEBUG tab<\/h4>\n\n
wp-config.php<\/code>:<\/p>\n\n\n
WP_DEBUG<\/code> - master debug switch<\/li>\nWP_DEBUG_LOG<\/code> - write errors to a log file<\/li>\nWP_DEBUG_DISPLAY<\/code> - show errors on screen<\/li>\nSCRIPT_DEBUG<\/code> - use unminified core JS\/CSS<\/li>\nSAVEQUERIES<\/code> - log all database queries<\/li>\n<\/ul>\n\nwp-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 WP_DEBUG<\/code> is always visible as a badge in the plugin header.<\/p>\n\nError Log tab<\/h4>\n\n
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>\n\nCron Tasks tab<\/h4>\n\n
Transients tab<\/h4>\n\n
Autoloaded tab<\/h4>\n\n
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>\n\nHTTP Log tab<\/h4>\n\n
wp_remote_get<\/code>, wp_remote_post<\/code>, etc.) via the 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>\n\nConstants tab<\/h4>\n\n
\n
globus-debug-control<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n\n
Does the plugin require WP_DEBUG to be enabled?<\/h3><\/dt>\n
WP_DEBUG<\/code> is set to true<\/code> in wp-config.php<\/code>. Error display and logging settings work independently of WP_DEBUG<\/code>. You can toggle WP_DEBUG<\/code> and related constants from the WP_DEBUG<\/strong> tab without editing any files manually.<\/p><\/dd>\nWill it hide errors in AJAX or REST API responses?<\/h3><\/dt>\n
What is the MU-plugin dropin and do I need it?<\/h3><\/dt>\n
wp-content\/mu-plugins\/<\/code>. 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.<\/p><\/dd>\nWhere is the log file saved?<\/h3><\/dt>\n
wp-content\/debug.log<\/code>. 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<\/strong> tab lets you read, download, and clear the log directly from the admin panel.<\/p><\/dd>\nCan I see scheduled cron tasks?<\/h3><\/dt>\n
Can I inspect transients and autoloaded options?<\/h3><\/dt>\n
What does the HTTP Log tab do?<\/h3><\/dt>\n
Can I use this on a live site?<\/h3><\/dt>\n
php-error<\/code> class removal active. The diagnostic tabs (Cron Tasks, Transients, Autoloaded, HTTP Log, Constants) are read-only and safe to use at any time.<\/p><\/dd>\n\n<\/dl>\n\n\n2.2.5<\/h4>\n\n
\n
2.2.4<\/h4>\n\n
\n
2.2.3<\/h4>\n\n
\n
2.2.2<\/h4>\n\n
\n
2.2.1<\/h4>\n\n
\n
2.2.0<\/h4>\n\n
\n
2.1.0<\/h4>\n\n
\n
2.0.0<\/h4>\n\n
\n