W3NetLab Debug Log Console

W3NetLab Debug Log Console helps administrators troubleshoot WordPress without exposing PHP errors on the public website.

It goes beyond a basic log viewer by combining controlled debug activation, automatic shutoff, runtime verification, protected storage, and memory-safe inspection in one dashboard tool.

Standout features

• Enable or disable debug logging from Tools > Debug Log Console.
• Keep frontend error display disabled while logging is active.
• Automatically stop logging after 10 minutes, 30 minutes, 1 hour, 6 hours, or 24 hours.
• See the local shutoff time and a live hh:mm:ss countdown.
• Search and filter complete multi-line entries without losing stack traces.
• Read only the newest 512 KB and display up to 1,500 lines to avoid large-log memory exhaustion.
• Download, clear, or rotate the active log through protected administrator actions.
• Verify that the loaded debug constants match the requested state and fail safely when they do not.
• Detect existing debug definitions and resolve only supported cases after explicit administrator approval.
• Store logs locally with no telemetry, tracking, remote assets, or external log service.

Protected log storage

Logs are stored in a w3netlab-debug-log-console folder under the runtime uploads directory resolved by WordPress. The active log uses a randomized filename.

The plugin creates Apache/OpenLiteSpeed and IIS access-control files plus an index file. It validates paths, rejects symbolic links, and never creates temporary PHP files beside wp-config.php.

Configuration safety

Automatic setup is available only when WordPress has safe direct access to a regular, writable wp-config.php file. Updates are limited to recognized debug definitions and the plugin-owned block, then read back and verified. If verification fails, the plugin attempts to restore the original content.

Normal enable, disable, and automatic-shutoff operations use a protected marker. If the requested configuration does not take effect, the marker is removed and logging is not reported as enabled.