Debug log viewer

When WP_DEBUG_LOG is enabled, WordPress writes PHP notices, warnings and fatal errors to wp-content/debug.log. Reading that file normally means an FTP client or a host file manager, which is enough friction that most people never look until something is badly broken.

This feature shows the file inside wp-admin. You get the last 200 lines, plus a button to clear the file.

It requires WP_DEBUG_LOG to be enabled in wp-config.php. If the file does not exist, Vectro tells you so rather than showing an empty panel that looks like a bug.

The Maintenance module is off by default on a new install. Switch it on from the Vectro dashboard before this feature can run.

The debug log is where a site tells you what is wrong: the deprecated function that will break on the next PHP upgrade, the plugin throwing a notice on every page load, the fatal error behind an intermittent white screen. All of it is recorded and almost none of it is read, because reading it means going and getting it.

A debug.log that has quietly reached several hundred megabytes is both a disk problem and a sign that something is erroring constantly. Vectro reads only the end of the file, so even a log that size opens quickly.

Vectro reads wp-content/debug.log from the end rather than loading the whole file into memory: it seeks to the last 512 KB and ignores everything before it, which is what makes it safe to open a log that has grown very large. Only the last 200 lines are rendered.

Access is restricted to users with the capability to manage options, so the log is not exposed to lower-privileged accounts. Debug logs routinely contain file paths, query fragments and occasionally credentials in a stack trace, so this restriction matters.