BlogSafe Debug 360

By BlogSafe.org

0+ active installationsVersion 1.0.4

Keep WordPress debugging enabled without leaving a persistent public debug.log. Capture errors in your dashboard and receive email alerts.

Description

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.
  • Ignore known noise. Suppress an exact error message or messages containing a phrase. Adding a phrase also removes existing matching entries.
  • Keep useful history. Clearing the active log moves entries into History, where they remain for up to 30 days or 5,000 cleared entries. You can permanently delete entries when needed.
  • Test error capture. Generate harmless test errors with one click.
  • Find stray log files. Look for error.log and error_log files in your WordPress folder with Check now. With a scan schedule set (hourly, daily, weekly or monthly), Debug 360 imports their contents and deletes each file after a successful import. Scanning is off by default.
  • Manage debug settings. Control WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY and SCRIPT_DEBUG from the dashboard without manually editing wp-config.php.
  • Control access. Set the minimum role allowed to view and manage errors; only administrators can change settings.

Your site, your data

The free plugin stores logs in your own WordPress database and uses your site’s mail system for alerts. It requires no external monitoring account and does not upload logs or contact BlogSafe. The active log is limited to 50,000 entries; daily cleanup removes older entries beyond that limit.

Want deeper diagnostics?

BlogSafe Debug 360 Pro is a separate paid edition with:

  • Grouped errors with occurrence counts and first/last seen times.
  • Request and WordPress hook context, plus errors linked to the same page load.
  • Optional stack traces, including argument values.
  • CSV, JSON and plain-text exports.
  • Slack, Microsoft Teams, Discord and Google Chat alerts.
  • Uploads of new entries to a private GitHub repository you own, for review by you or an AI assistant.

Pro includes a 30-day money-back guarantee. All features in the free plugin remain free. Upgrading by uploading the Pro ZIP preserves your settings and logs.

Learn more: BlogSafe Debug 360 Pro.

Important technical and privacy details

  • Log-file cleanup: If wp-content/debug.log is created before Debug 360 loads, the plugin imports its contents into the database and deletes the file, normally during that same page load. If an error occurs after its shutdown handler has run, the file is imported and deleted on the next request. PHP or the server may also create separate error.log or error_log files in folders across your site. Debug 360’s scheduled scans, which are off by default, find those inside the WordPress folder, import them and delete them. A debug.log file may be briefly accessible before cleanup, so server-level access restrictions are still recommended.
  • WordPress configuration: Enabling Debug 360 switches on WP_DEBUG and WP_DEBUG_LOG and switches off WP_DEBUG_DISPLAY. Turning off either of the first two also turns off Debug 360. It backs up wp-config.php before changes, keeps the three newest backups and restores the original debug settings on deactivation. If the file is read-only, the switches are locked and manual instructions are shown. Debug 360 does not directly change PHP configuration settings.
  • Sensitive information: Error messages can include visitor-supplied text and site details. The free plugin records the message, level, time and logged-in user’s ID. Pro can additionally record request type, hook names, a page-load identifier and optional stack-trace arguments. Restrict log access to trusted users.
  • Third-party code: Syntax highlighting uses Prism 1.30.0 (MIT licence). Bundled minified files come unmodified from the official prismjs package; readable source.

Installation

  1. Go to Plugins > Add New, search for BlogSafe Debug 360, install it and activate it. Alternatively, upload the blogsafe-debug-360 folder into /wp-content/plugins/ and activate it.
  2. Open Debug 360 in the admin menu.
  3. Enable Debug 360 and click Save Settings.
  4. Configure viewing permissions, email alerts and optional stray-log scanning under Debug 360 > Settings.
  5. Use the test-error button to verify capture.

FAQ

Where are errors stored?

In two tables in your site’s WordPress database, not an external monitoring service.

Can I use it on a live site?

Yes. Enabling Debug 360 automatically turns off WP_DEBUG_DISPLAY, so PHP errors are not displayed to visitors by default. You can turn WP_DEBUG_DISPLAY back on using the settings switch, but that can expose error details to visitors on a live site. Restrict access to stored errors to trusted users.

What if wp-config.php is read-only?

Debug 360 locks its WordPress switches and explains how to change wp-config.php by hand; its own error capture keeps working. If WP_DEBUG is off, it can only capture errors PHP still reports, such as serious errors, and may miss warnings, notices and early errors.

What happens when I deactivate or uninstall it?

Deactivation restores the original debug settings where the file is writable. If it is not, Debug 360 shows manual restoration instructions. Uninstalling removes its database tables, settings, scheduled tasks, its own wp-config.php backups and leftover temporary import files, and makes a final attempt to restore those settings.

Can I stop recurring errors from filling the log?

Yes. Use Ignore for an exact message or add a phrase under Debug 360 > Ignores. Imported files containing repeated identical errors are also stored with occurrence counts.

Can I send alerts to Slack or Teams?

Email alerts are included in the free version. Slack, Microsoft Teams, Discord and Google Chat are available in Pro.

Screenshots

Changelog

1.0.4

  • Initial public release.