| 开发者 | globusstudio |
|---|---|
| 更新时间 | 2026年11月18日 21:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
WP_DEBUG into a focused debug dashboard - without SSH, SQL, or editing files. Filter noisy PHP error types, toggle debug constants, read debug.log, and inspect cron, transients, autoloaded options, outgoing HTTP calls, and runtime constants from the WordPress admin.
You enable WP_DEBUG to track down a bug in your code - and immediately get buried under hundreds of notices and deprecation warnings from third-party plugins and themes. Things you did not write. Things you cannot fix. The real error you are looking for is lost in the noise.
GLOBUS Debug Control solves this. Pick exactly which PHP error types you want to see, silence the rest, and get a full debug dashboard - error logs, cron health, transients, database bloat, outgoing HTTP calls, and wp-config constants - all in one place, all from the admin panel.
No SSH. No file editing. No installing five separate plugins for five separate problems.
Why developers keep it installed
php-error CSS class to <body> when a PHP error occurs, which can shift your page layout. This plugin removes it automatically via CSS and JavaScript.WP_DEBUG, you SSH into the server, find wp-config.php, and edit a constant by hand. This plugin does it from a checkbox in the admin panel.wp-config.php settings (default, non-intrusive)WP_DEBUG_DISPLAY is onwp-content/)wp-content/debug.log if no path is specifiedphp-error class to the <body> tag whenever a PHP error occurs. This shifts margins and breaks your page layout - both on the front-end and in the admin. This option removes it via both CSS and JavaScript so your site looks normal even with errors present.
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
Normally, toggling WP_DEBUG means SSH access, finding wp-config.php, and editing PHP constants by hand. This tab lets you flip the five most important debug constants from the admin panel:
WP_DEBUG - master debug switchWP_DEBUG_LOG - write errors to a log file (supports a custom log path)WP_DEBUG_DISPLAY - show errors on screenSCRIPT_DEBUG - use unminified core JS/CSSSAVEQUERIES - log all database querieswp-config.php automatically and patches it in place, adding the constant if it is missing or updating the existing value. A timestamped backup copy of wp-config.php is created before the first write so the file can always be restored. 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.
MCP and REST abilities
On WordPress 6.9+ the plugin registers abilities for MCP and REST clients:
gdc/get-schema - every option with its type, default and allowed values, plus supported wp-config constantsgdc/get-options - all plugin options and the effective runtime state (error_reporting, display_errors, log_errors, error_log, resolved log file, mu-plugin status, API context)gdc/update-options - patch any option by key; values are sanitised and applied immediatelygdc/reset-options - restore defaults, requires confirm=truegdc/get-log - tail of the error log with severity levels, optional substring filtergdc/clear-log - truncate the log file, requires confirm=truegdc/get-wp-config - current values of WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG, SAVEQUERIESgdc/update-wp-config - write those constants into wp-config.php, requires confirm=truegdc/enable-debug-logging - one-click enable WP_DEBUG + WP_DEBUG_LOG, requires confirm=truegdc/get-transients - database transients with summary and storage diagnosticsgdc/purge-expired-transients - delete expired transients, requires confirm=truegdc/get-constants - every runtime constant grouped by category, with secrets maskedmanage_options capability. The early-loader dropin is regenerated automatically after a plugin update - no manual re-save is needed. gdc/update-wp-config keeps a timestamped backup of wp-config.php before writing.
Error Log tab
Your debug.log file can grow to hundreds of megabytes without you noticing. This tab displays it 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. When WP_DEBUG is off, the tab explains why no new lines arrive, disables the test-error generator, and offers a one-click fix that writes the debug constants to wp-config.php.
Cron Tasks tab
WordPress cron runs silently. When events are overdue, hooks are orphaned, or schedules are duplicated, there is no built-in way to see it. This tab lists all scheduled 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
Expired transients pile up in the database, and without raw SQL you have no way to see or clean them. This tab displays database-stored WordPress transients from the options table with key name, data size, and expiration time. On multisite, network transients from the sitemeta table are included too. Transients stored in an external object cache (Redis, Memcached) are not shown; when such a cache is detected, the tab says so instead of showing a bare empty state. Database errors and unexpected transient-like rows are also surfaced in the notice area. Expired transients are highlighted. You can delete individual transients or purge all expired ones in one click, including network site transients. Summary cards show total count, expired count, and total data size.
Autoloaded tab
Every autoloaded option is fetched on every single page load. When plugins leave behind large serialised blobs, your site slows down and there is no obvious way to find the culprit. This tab lists autoloaded options from wp_options sorted by data size (top 200). Summary cards display total autoloaded row count and total payload size with warnings when thresholds are exceeded (over 800 KB or over 100 rows).
HTTP Log tab
Plugins and themes silently make outgoing HTTP calls - license checks, update pings, API syncs - and a slow or failing endpoint can stall your entire page load. This 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, error message, transport class, and response duration. Sensitive query parameters (key, token, secret, password, etc.) are automatically masked before an entry is stored.
Constants tab
When you need to check what debug, performance, or security constants are active at runtime, you normally have to grep through wp-config.php and hope nothing is overridden elsewhere. This tab displays every user-defined PHP constant at runtime, grouped by category: Debug, Performance, Security, Database, Auth and Salts, Paths, Other WP_* constants, and Plugin & Theme constants from plugins, themes and custom code. A name filter and collapsible groups keep large lists manageable. Sensitive values (database password, auth keys, salts, and names containing PASSWORD, SECRET, TOKEN, API_KEY, and similar markers) are automatically masked.
globus-debug-control folder to the /wp-content/plugins/ directory.This is exactly what GLOBUS Debug Control is built for. Go to Settings - GLOBUS Debug Control, enable the plugin, and uncheck the error types you want to suppress (Notices, Deprecated, Warnings). You will only see the errors that matter to your own code.
The plugin automatically suppresses error display during AJAX requests, REST API calls, WP-Cron, WP-CLI, XML-RPC, and other non-HTML contexts. No configuration needed - it happens as soon as the plugin is active.
Use the WP_DEBUG tab. It reads and writes debug constants directly in your wp-config.php from the admin panel. No terminal, no file manager, no FTP.
The plugin is always active, but error filtering and test errors only take effect when WP_DEBUG is true. The Settings and Error Log tabs show the current WP_DEBUG and WP_DEBUG_LOG state and offer a one-click fix that writes the constants to wp-config.php after creating a backup. You can also toggle them from the WP_DEBUG tab at any time.
WordPress loads plugins in alphabetical order. Enable the MU-plugin dropin in the Settings tab - it installs a small helper into wp-content/mu-plugins/ that runs before any regular plugin, so your filter settings apply from the very first line of the request. The dropin is removed automatically on deactivation or uninstall.
The Error Log tab shows it in the admin with color-coded lines and pagination. Files over 2 MB are read from the tail so the page loads fast. You can download the full file or clear it with one click.
Check the Cron Tasks tab for overdue or orphaned events. Check the Autoloaded tab for oversized options that load on every request. Check the Transients tab for expired entries piling up in the database. All three are read-only and safe to use on a live site.
Yes. The recommended setup: 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 at any time.
The plugin is a debug control panel, so it intentionally sets error_reporting, display_errors, log_errors, and the error_log path for the current request. The changes are scoped to that request and apply only while the plugin is enabled; wp-config.php remains the source of truth for the next request. Each change is guarded by WP_DEBUG and the plugin options, and can be reverted from the Settings screen or by disabling the plugin.
Yes. Before the plugin writes a debug constant it creates a timestamped wp-config.php.gdc-backup-YYYYMMDD-HHMMSS copy next to the file. The plugin does not restore it automatically: rename the backup over wp-config.php if you need to roll back. The same backup runs for the admin form, the one-click debug fix, and the gdc/update-wp-config ability.
It is an admin-only tool in the Error Log tab. It requires manage_options and a valid nonce, and writes one sample line so you can confirm that logging works. It is not available on the front end and never runs automatically.
gdc/enable-debug-logging, gdc/get-transients, gdc/purge-expired-transients, and gdc/get-constantsgdc/get-log also returns the effective debug and logging state, so MCP clients can explain an empty loggdc/get-schemagdc/get-options: error_reporting, display_errors, log_errors, error_log, log size and API contexterror_log to the OS null device, so direct error_log() calls stop writing to debug.loggdc/update-wp-config creates a timestamped wp-config.php backup before writing