Bowo

<p>Debug Log Manager allows you to:</p>
<ul>
<li><strong>Enable <a href="https://wordpress.org/support/article/debugging-in-wordpress/" rel="ugc">WP_DEBUG</a> with one click to log PHP, database and JavaScript errors</strong> when you need to, and disable it when you’re done. No need to manually edit wp-config.php file. </li>
<li><strong>Create the debug.log file for you</strong> in a non-default location with a custom file name for enhanced security. </li>
<li><strong>Copy the content of the default / existing debug.log file</strong> into the custom debug.log file, and delete the default / existing debug.log file. So there is continuation in logging and enhanced security going forward.</li>
<li>Parse the debug.log file and <strong>view distinct errors and when they last occurred</strong>, which is better than looking at the raw log file (potentially) full of repetitive errors. </li>
<li><strong>Quickly find and filter more specific errors</strong> for your debugging work.</li>
<li><strong>Make error details easier to read</strong> by identifying error source (core / plugin / theme) and separating file path and line number.</li>
<li><strong>Easily view files where PHP errors occurred</strong>. This includes WordPress core, plugin and theme files.</li>
<li><strong>Enable auto-refresh</strong> to automatically load new log entries. No need to manually reload the browser tab, or to <code>tail -f</code> the log file on the command line.</li>
<li><strong>Easily clear the debug.log file</strong> to save disk space and more easily observe newly occurring errors on your site.</li>
<li><strong>Show an indicator on the admin bar</strong> when error logging is enabled.</li>
<li><strong>Add a dashboard widget</strong> showing the latest errors logged.</li>
<li><strong>Use <code>error_log()</code></strong> to output error info into your debug log. e.g. <code>error_log( $error_message )</code> for simple, string-based error message, or <code>error_log( json_encode( $error ) )</code> when inspecting a more complex error info, e.g. array or object.</li>
<li><strong>Auto-trim debug.log file size</strong> so it does not grow larger than the available memory. This prevents out-of-memory error when trying to parse and view the debug.log file.</li>
</ul>
<p>A simpler and more compact version of Debug Log Manager is included as part of the <a href="https://wordpress.org/plugins/system-dashboard/" rel="ugc">System Dashboard plugin</a>, should you prefer a single plugin that does more.</p>
<h3>What Users Say</h3>
<p><em>“This is <strong>a great plugin for dev</strong> especially for people who tinker in the code.”</em> ~<a href="https://wordpress.org/support/topic/great-for-dev/" rel="ugc">PK Son</a></p>
<p><em>“I have used a couple of other logger plugins and <strong>this is by far the best one</strong>.”</em> ~<a href="https://wordpress.org/support/topic/must-have-plugin-485/" rel="ugc">Brian Henry</a></p>
<p><em>“<strong>Another massive time-saving tool.</strong>“</em> ~<a href="https://digwp.com/2023/06/plugins-troubleshoot-debug-wordpress/" rel="nofollow ugc">Jeff Starr</a></p>
<h3>Give Back</h3>
<ul>
<li><a href="https://bowo.io/review-dlm" rel="nofollow ugc">A nice review</a> would be great!</li>
<li><a href="https://bowo.io/feedback-dlm" rel="nofollow ugc">Give feedback</a> and help improve future versions.</li>
<li><a href="https://translate.wordpress.org/projects/wp-plugins/debug-log-manager/" rel="nofollow ugc">Help translate</a> into your language.</li>
<li><a href="https://bowo.io/github-dlm" rel="nofollow ugc">Github repo</a> to contribute code.</li>
<li><a href="https://bowo.io/dotorg-sponsor-dlm" rel="nofollow ugc">Sponsor</a> my work.</li>
</ul>
<h3>Check These Out Too</h3>
<ul>
<li><a href="https://wordpress.org/plugins/system-dashboard/" rel="ugc">System Dashboard</a>: Central dashboard to monitor various WordPress components, processes and data, including the server.</li>
<li><a href="https://wordpress.org/plugins/variable-inspector/" rel="ugc">Variable Inspector</a>: Inspect PHP variables on a central dashboard in wp-admin for convenient debugging.</li>
<li><a href="https://wordpress.org/plugins/admin-site-enhancements/" rel="ugc">Admin and Site Enhancements</a> helps you to easily enhance various admin workflows and site aspects while replacing multiple plugins doing it.</li>
<li><a href="https://www.wpnewsboard.com/" rel="nofollow ugc">WordPress Newsboard</a>: The latest news, articles, podcasts and videos from 100+ WordPress-focused sources.</li>
</ul>


Debug Log Manager – Conveniently Monitor and Inspect Errors

A stitch in time saves nine.

This plugin is so important I have it as the #2 item in my admin menu (below only Dashboard). 

Proactively finding and fixing errors is essential to running a successful site.

This plugin does a simple job, and it does it very well. Some niceties are the JavaScript logging, and the counting of log occurrences. The UI is simple, but appropriate. The developer is responsive. 

I have used a couple of other logger plugins and this is by far the best one.

Must-have plugin


I wish I had found out about this plugin a long time ago. It saves time when debugging client sites.


Such a help

handy plugin


I've been switching from a custom Docker Compose environment to @wordpress/env (aka wp-env) which I still fail to figure out how to quickly tail the PHP debug logs. Is it even possible? They say it is, yet I only ever see the HTTP logs from the web server...



I've added this plugin to my .wp-env.json file so that I always have it available in my test environment now. I'm amazed the infamous Debug Bar plugin doesn't seem to have a way to see the tail of the PHP debug log file..?



My favorite part about this plugin is that repetitive log lines are grouped together in the display, with a note of the number of occurrences. Makes reading the logs much easier at quick glance!



The downside of this plugin is just by the nature that it's a plugin—if you're trying to debug PHP Fatal errors that happen early in execution, they won't be accessible since they would prevent this plugin from running. However, I didn't have a problem with this because I'd let the PHP Fatal happen and then just undo whatever I did to cause the fatal error. After that, I'd just go back to review the error in this plugin's page. Easy!


Makes Debugging in @wordpress/env Possible

Log PHP, database and JavaScript errors via WP_DEBUG with one click. Conveniently create, view, filter and clear the debug.log file.

phpguard1

<p>PHPGuard Lite helps prevent white screens and fatal errors by allowing you to scan WordPress plugins and PHP code for syntax issues before they are activated or used.</p>
<p>It provides three main tools:</p>
<ul>
<li>Scan installed plugins for PHP syntax errors  </li>
<li>Scan a plugin ZIP file before installing it  </li>
<li>Scan pasted PHP code snippets  </li>
</ul>
<p>All scans run locally on your server. No code is executed. No data leaves your site.</p>
<p>The plugin uses a safe, non-executing PHP parser to detect parse errors and fatal syntax issues that would otherwise crash WordPress when a plugin or snippet is loaded.</p>
<h3>Privacy & Security</h3>
<p>PHPGuard Lite is fully self-contained.</p>
<ul>
<li>No telemetry  </li>
<li>No accounts  </li>
<li>No email collection  </li>
<li>No licensing calls  </li>
<li>No remote servers  </li>
<li>No background connections  </li>
</ul>
<p>All scanning is done locally on your WordPress installation.</p>
<h3>About base64 in snippet scanning</h3>
<p>When scanning pasted code snippets, the browser may send the code using base64 encoding. This is only used to safely transport pasted text through an HTTP request without breaking due to special characters or encoding issues.</p>
<p>The base64 data is immediately decoded back into plain text and passed to the PHP parser. The code is never executed, stored, or sent anywhere.</p>
<p>This is a transport mechanism only — not obfuscation, encryption, or remote communication.</p>
<h3>PHPGuard Pro</h3>
<p>An optional commercial version, PHPGuard Pro, is planned. It will provide advanced automation and safety features for professional and agency workflows. Information about PHPGuard Pro is available on the project website.</p>
<h3>Usage</h3>
<p>After activation, open PHPGuard in the WordPress admin menu.</p>
<p>You can:</p>
<ul>
<li>Select an installed plugin and run a syntax scan</li>
<li>Upload a plugin ZIP and scan it before installation</li>
<li>Paste PHP code into the snippet scanner</li>
</ul>
<p>Results will show any detected syntax errors or potential issues.</p>
<h3>Support</h3>
<p>Documentation and project updates are available on the PHPGuard website.</p>


PHPGuard Lite

Check WordPress plugins and PHP code for syntax errors before activating or using them.

Debug Log Manager – Conveniently Monitor and Inspect Errors vs PHPGuard Lite