WordPress plugin
BlogSafe Debug 360
Keep WordPress debugging enabled without leaving a persistent public debug.log. Capture errors in your dashboard and receive email alerts.
- Version
- 1.0.4
- Last updated
- Nov 17, 2026
- Tested up to
- WordPress 7.1.5
- Requires
- WP 6.2 · PHP 8.2
Health check
Is BlogSafe Debug 360 safe to rely on?
Our reading of the public WordPress.org data: maintenance, compatibility, ratings and support.
Actively maintained
Last updated on November 17, 2026. Regular updates usually mean bugs and security reports get fixed.
Tested with current WordPress
The author has tested it up to WordPress 7.1.5.
Requires PHP 8.2 or newer
Check your hosting PHP version before installing. Modern PHP is faster and receives security fixes.
Rank tracker
Where BlogSafe Debug 360 ranks in WordPress.org search
Its position in WordPress.org plugin search for its tags and name, refreshed weekly so you can see how its visibility changes.
| Keyword | Position | Change | Trend | Current #1 |
|---|---|---|---|---|
| debug | ||||
| debug log | ||||
| error log | ||||
| php errors | ||||
| troubleshooting | ||||
| blogsafe debug 360 |
Checked against the top 100 WordPress.org search results.
Overview
What BlogSafe Debug 360 does
Leave debugging on. Stop leaving the debug log exposed.
Turning off WordPress debugging on a live site means losing the details you need when something goes wrong. Leaving it enabled can create another problem: wp-content/debug.log may be accessible from the web and reveal server paths, plugin names and other sensitive information.
BlogSafe Debug 360 lets you keep collecting PHP errors without using a persistent public log file as your record. Once loaded, it captures reportable errors directly into your WordPress database. It also imports and removes the standard debug.log file when necessary. You can inspect errors and receive notifications from within WordPress instead of checking files on your server.
What you can do
Catch errors as they happen. Record PHP errors, warnings, notices, deprecations and fatal errors, including those caught by a shutdown handler.
Find what matters. Use log and table views, error-level filters, date or level sorting, and syntax highlighting.
Get email alerts. Choose recipients and a minimum severity level; repeated notifications are throttled.
Description from the author's listing. Read the full listing on WordPress.org
Screenshots
BlogSafe Debug 360 in action



FAQ
BlogSafe Debug 360: questions and answers
What is BlogSafe Debug 360?
BlogSafe Debug 360 is a WordPress plugin by BlogSafe.org. Keep WordPress debugging enabled without leaving a persistent public debug.log. Capture errors in your dashboard and receive email alerts.
Is BlogSafe Debug 360 free?
BlogSafe Debug 360 is listed in the WordPress.org plugin directory, so the version there is free to download and use. Some authors also sell paid add-ons or a premium edition with more features and support.
Is BlogSafe Debug 360 still maintained?
BlogSafe Debug 360 was last updated on November 17, 2026. The current version is 1.0.4. Check the changelog on WordPress.org and test updates on a staging site before applying them to a live site.
What does BlogSafe Debug 360 require?
BlogSafe Debug 360 requires WordPress 6.2 or newer and PHP 8.2 or newer. It has been tested up to WordPress 7.1.5.
Can Codefreex set up or customize BlogSafe Debug 360?
Yes. Codefreex installs, configures and customizes WordPress plugins including BlogSafe Debug 360, fixes conflicts and performance problems, and builds custom features when a plugin does not do exactly what you need. Send your site URL for a free review.
Free expert review
Need BlogSafe Debug 360 set up, customized or fixed?
Tell us about your site and what you need this plugin to do. A senior WordPress developer replies within one business day with a plan and a quote.