Bowo

Debug Log Manager allows you to:
<ul>
<li>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 when you need to, and disable it when you’re done. No need to manually edit wp-config.php file. </li>
<li>Create the debug.log file for you in a non-default location with a custom file name for enhanced security. </li>
<li>Copy the content of the default / existing debug.log file 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 view distinct errors and when they last occurred, which is better than looking at the raw log file (potentially) full of repetitive errors. </li>
<li>Quickly find and filter more specific errors for your debugging work.</li>
<li>Make error details easier to read by identifying error source (core / plugin / theme) and separating file path and line number.</li>
<li>Easily view files where PHP errors occurred. This includes WordPress core, plugin and theme files.</li>
<li>Enable auto-refresh 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>Easily clear the debug.log file to save disk space and more easily observe newly occurring errors on your site.</li>
<li>Show an indicator on the admin bar when error logging is enabled.</li>
<li>Add a dashboard widget showing the latest errors logged.</li>
<li>Use <code>error_log()</code> 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>
</ul>
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.
<h3>What Users Say</h3>
“This is a great plugin for dev especially for people who tinker in the code.” ~<a href="https://wordpress.org/support/topic/great-for-dev/" rel="ugc">PK Son</a>
“I have used a couple of other logger plugins and this is by far the best one.” ~<a href="https://wordpress.org/support/topic/must-have-plugin-485/" rel="ugc">Brian Henry</a>
“Another massive time-saving tool.“ ~<a href="https://digwp.com/2023/06/plugins-troubleshoot-debug-wordpress/" rel="nofollow ugc">Jeff Starr</a>
<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.

Leap Spark

Ferret is a simple wrapper for the Sentry PHP and JavaScript SDKs. It will catch all PHP errors, as well as JavaScript errors if the option is switched on. It utilizes the legacy PHP library by Sentry intentionally, in an effort to maximize compatibility. The newest SDK requires PHP^7.1 whereas the legacy requires minimum of 5.6
There are four settings that you can adjust.
<ul>
<li>The <code>DSN</code> – Your DSN key, this is required</li>
<li><code>Project ID</code> – The project key, this is also required</li>
<li><code>Enable JavaScript Logging</code> – Enable logging of JavaScript errors</li>
<li><code>Ignore WP Core Errors</code> – Prevent sending events to Sentry that originate from WordPress core (wp-admin, wp-includes)</li>
<li><code>Debug Environment</code> – Switch the Sentry environment to <code>Debug</code>, turning this off puts the environment to <code>Production</code></li>
</ul>
All three are accessible on the plugin settings page located in the <code>Settings -> Ferret Settings</code> page.
In the future we will add the ability to selectively ignore specific themes or plugins in a convenient way. We would also like to expose an internal API that can be used by other plugins/themes to capture errors or add context.

Ferret

Ferret is a simple wrapper for the Sentry PHP and JavaScript SDKs. It will catch all PHP errors, as well as JavaScript errors if the option is switche …

Debug Log Manager – Conveniently Monitor and Inspect Errors vs Ferret