Select one or more tags, then press “Search Plugins”

Find Plugin with any / all of the selected criteria
Search Plugin

BlogSafe Debug 360 Wordpress Plugin - Rating, Reviews, Demo & Download

BlogSafe Debug 360 Preview Wordpress Plugin - Rating, Reviews, Demo & Download
No ratings yet
Free
Follow for free plugins, new theme releases and theme news

Plugin Description

WordPress’s own debug log writes errors to wp-content/debug.log. On most servers anyone who knows the address can download that file, and it can reveal file paths, plugin names and other details that help an attacker.

BlogSafe Debug 360 is not a log reader. It replaces PHP’s error logging with its own error handler and its own shutdown handler, so once it has loaded, errors go straight into your site’s database the moment they happen. Anything earlier is picked up from debug.log and imported. You read them in the WordPress admin; nothing is left in a public file.

Features

  • Its own error handler. From the moment the plugin loads, PHP hands every warning, notice, deprecation and error directly to Debug 360, and none of them is written to debug.log.
  • Its own shutdown handler. Fatal errors stop PHP before an ordinary handler can see them. Debug 360’s shutdown handler records them as the request ends, with the message, file and line, and removes the copy PHP itself wrote to debug.log.
  • No public log file. What can still reach debug.log is errors raised before Debug 360 loads or while the database is unavailable, and messages code writes directly with error_log(), such as WordPress’s own background-update messages when WP_DEBUG_LOG is on. Debug 360 imports all of it into the database and deletes the file, normally in the same page load. A fatal error before Debug 360 loads leaves the file in place until the next page load.
  • Everything WordPress can report. Switching on Debug 360 also switches on WP_DEBUG and WP_DEBUG_LOG, and switches off WP_DEBUG_DISPLAY. WordPress only raises its own deprecation and misuse warnings with WP_DEBUG on, and errors from before Debug 360 loads are only saved with WP_DEBUG_LOG on.
  • See it work. One click raises a few harmless test errors, so you can watch them arrive in the log before your site has a real one.
  • Log viewer. Log and table views, filters by error level, sorting by date or level, and syntax highlighting.
  • History. Clear Debug Log gives you a fresh start without losing anything: switch on History to see cleared entries again. Cleared entries are kept for 30 days, and at most 5,000, then deleted oldest first.
  • Ignore rules. Ignore one exact message, or any message containing a phrase: noise from plugins, themes or WordPress itself that you can’t change. Adding a phrase also removes matching entries already in the log.
  • Email alerts. Email the users you choose when an error at or above a chosen level occurs. Repeats of the same error are throttled.
  • Debug switches. Turn WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY and SCRIPT_DEBUG on or off without editing files. Switching off WP_DEBUG also switches off WP_DEBUG_LOG and WP_DEBUG_DISPLAY, which do nothing without it. Switching off WP_DEBUG or WP_DEBUG_LOG switches off Debug 360.
  • Stray error logs. Find, import and remove error.log and error_log files across your site on an hourly, daily, weekly or monthly schedule, or at once with Check now, while Debug 360 is switched on. When a file repeats the same error many times, it is stored once with a count, so a flooded log stays readable.
  • Access control. Choose the minimum role that can view the log. Only administrators can change settings.

What Debug 360 changes on your site

  • wp-config.php. When an administrator switches on Debug 360 or flips one of the four WordPress debug switches and clicks Save Settings, Debug 360 edits those define() lines in wp-config.php. It saves a backup first (it keeps the newest three) and replaces the file in a single step, so a failed write cannot leave it broken. Before its first change it records your original settings, and deactivating Debug 360 puts them back. If wp-config.php is read-only, the switches are locked and Debug 360 shows the lines to change by hand.
  • PHP settings. Debug 360 does not change PHP’s settings. Which errors are reported, whether they are shown and where PHP writes them come from WordPress’s own WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY, which the switches above set.
  • Log files. It deletes wp-content/debug.log after importing it. With a scan schedule set and Debug 360 switched on, it also deletes each error.log and error_log file after a successful import. Scanning is off by default.

Privacy

  • Logs are stored only in your site’s own database. The log keeps at most 50,000 entries; once a day the oldest beyond that are deleted, so a flood of errors cannot fill your database.
  • Clear Debug Log hides entries rather than deleting them. They are deleted after 30 days, or sooner once more than 5,000 have been cleared. To remove entries immediately, use Delete or Bulk actions > Delete.
  • The free plugin does not connect to any outside service and sends nothing anywhere. Email alerts go through your site’s own mail, to the users you choose.
  • Error messages can contain text sent by visitors, file paths and other site details. Limit log access to people you trust.
  • The free plugin stores each error’s message, level, time and the logged-in user’s ID. BlogSafe Debug 360 Pro also stores where each error came from: the kind of request (for example cron, AJAX or the admin area), the WordPress hooks that were running, and a random ID shared by errors from the same page load. Hook names can include text from the request.

BlogSafe Debug 360 Pro

BlogSafe Debug 360 Pro is a separate, paid edition for sites that need more than a log. It adds:

  • Grouped view. Repeated errors are stacked into one row, with an occurrence count and first and last seen times.
  • Where each error came from. See the cron job, AJAX or REST request and WordPress hooks behind every error, and every other error from the same page load.
  • Stack traces. Optionally record the full call stack, including argument values, for new errors.
  • Log export. Download the current view or the whole log as CSV, JSON or plain text.
  • Team alerts. Send error alerts to Slack, Microsoft Teams, Discord or Google Chat.
  • GitHub monitoring. Upload new log entries to a private GitHub repository you own, for review by you or an AI assistant.

Pro comes with a 30-day money-back guarantee. Everything in this free plugin stays free. To upgrade, upload the Pro ZIP from Plugins > Add New; WordPress offers to replace the free plugin, and your settings and logs are kept. This free plugin never downloads code or contacts blogsafe.org on its own. Learn more at blogsafe.org.

Third-party code

The log viewer’s syntax highlighting uses Prism 1.30.0 (MIT licence). The bundled files are the unmodified minified files from the official prismjs package; the readable source is at github.com/PrismJS/prism.

Screenshots

  1. The log view, with syntax highlighting and level filters.

    The log view, with syntax highlighting and level filters.

  2. The table view, with sorting, View More and per-entry Delete and Ignore.

    The table view, with sorting, View More and per-entry Delete and Ignore.

  3. The Settings page: access level, email alerts and error.log scanning.

    The Settings page: access level, email alerts and error.log scanning.

  4. The Ignores page: phrases that keep matching messages out of the log, each with Disable, Edit and Delete.

    The Ignores page: phrases that keep matching messages out of the log, each with Disable, Edit and Delete.


Reviews & Comments