Skip to content

WordPress Debug Log: 8 Tabs Without SSH

A debug.log on a live site usually starts as a good idea and becomes a ten-megabyte file nobody opens, because reading it means SSH, tail and a mental filter for four thousand notices about a deprecated function. A wordpress debug log is only useful when it is filtered, bounded and reachable from the admin.

Code: GLOBUS Debug Control, GPLv2 or later.

WordPress 5.2 and newer, PHP 7.4 and newer, eight tabs under Settings, and no file editing.

Tab 1: what gets suppressed

Notices, deprecations, warnings and strict errors switch off independently. Display mode has three states: inherit, on, off.

The separation is the point. One plugin on a modern PHP emits hundreds of deprecations while the site works correctly, and a log full of those hides the one warning that matters. Turning off deprecations keeps the warning visible.

Tab 2: the constants, from the admin

WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG and SAVEQUERIES toggle from a page. wp-config.php is patched in place with a timestamped backup, and commented-out defines are never touched.

That last rule is what makes it safe on a server where someone keeps a disabled line as documentation. A plugin that rewrites commented code breaks the record of why it is there.

Tabs 3 and 4: the log and the schedule

The log opens in an editor with line numbers, severity colours, pagination, live polling, download and one-click clear. Large files are read from the tail, so a 200 MB log does not exhaust memory_limit before the page renders.

Cron shows every scheduled event, highlights overdue and orphaned hooks, finds duplicates, and can run an event now or delete an orphan. An orphaned hook is one of the quiet ways a site slows down: the event fires, the callback is gone, and nobody sees it.

Tabs 5, 6 and 7: what inflates a request

Transients list with size and expiry, and expired entries purge in one click. Autoloaded options show the heaviest two hundred, which is where a page builder hides a serialised blob that loads on every request.

HTTP Log captures outgoing WordPress HTTP API calls through http_api_debug: method, status, response time, transport class, and masked query parameters. A checkout that waits four seconds for a payment provider shows up here as one line.

Tab 8 and the rule behind all of them

Constants groups runtime values by category and masks database passwords, auth keys and salts automatically.

Errors are suppressed in AJAX, REST, WP-Cron, WP-CLI and XML-RPC contexts regardless of the display setting. That is the decision that keeps API responses valid JSON, and it is the difference between a debug plugin and a debug plugin that breaks an integration once a week.

What to do with the error you find

Read the stack trace from the bottom up: the frame closest to your code is at the top, and the plugin or theme name in the path is the first suspect. Then reproduce it once with the suppression off, so the line numbers match.

Write down the timestamp before you clear the log. A cleared log with no note is how a bug becomes unfixable a week later.

What it does not do

It does not fix the code, does not replace a profiler and does not read server logs outside WordPress. It also does not hide errors from a developer who needs them: the suppression is a setting, and the log stays available.

Related: log retention for how the security plugin stores its own records, and key php configuration variables for the settings this dashboard reads.