Sanctuary Ranger Crash Recorder
| 开发者 | rachelmharrisoncoaching |
|---|---|
| 更新时间 | 2026年10月13日 15:18 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Which WordPress milestone the request reached (plugins_loaded, init, template_redirect and so on)
- Outbound HTTP calls: host, path, status and duration. Query strings are never stored.
- PHP warnings, notices and deprecations (file, line, message)
- Failed emails (error message only)
- Request method, path, PHP and WordPress version
- The list of active plugins and the theme name (stored in the snapshot on your own site, used to build a replay)
- Which plugin, theme or WordPress core file the error came from
- Email alert when a fatal error is recorded (max one every 10 minutes)
- Webhook alert: sends a one-line summary to an HTTPS URL you provide
- Auto-quarantine: deactivates a plugin you have explicitly ticked if it causes repeated fatal errors within a time window you choose
- Replay in WordPress Playground: build a throwaway copy of the crash environment to experiment in. Clearly labelled as approximate
- Early recorder (optional): one small must-use file that starts the recorder before other plugins, installed and removed with a button
- Hook trace (developer option): also records the last WordPress hooks that ran in the crashing request. It adds some overhead, so leave it off on busy sites
安装:
- Upload the plugin folder to
/wp-content/plugins/or install it from the Plugins screen. - Activate it.
- Open Tools > Sanctuary Ranger to view snapshots and adjust settings.
常见问题:
Where is the data stored?
In a protected folder inside your uploads directory. By default events are kept in two rotating files of about 512 KB each, and the 20 newest crash snapshots are kept. Both sizes can be changed in the settings. Uninstalling the plugin deletes everything.
Can I try it in WordPress Playground?
Yes. Recording, snapshots, the crash screen box and quarantine all work in Playground. Email cannot be sent from Playground, webhooks may be blocked by the browser, and recorded data lasts only for the Playground session.
Does Replay copy my site?
No. It rebuilds the PHP version and the active plugins that can be installed from WordPress.org, at their latest versions. Your content, settings, custom or paid plugins and the request that crashed are not copied, so the crash may not reproduce. It is a quick throwaway place to experiment.
What does the early recorder change?
Only if you click "Install early recorder" does it add one small file, wp-content/mu-plugins/sanctuary-ranger-early.php, which starts this plugin before other plugins. It does nothing while this plugin is deactivated. "Remove early recorder" or deleting this plugin removes it.
Are there hooks for developers?
Yes. The bbcr_snapshot_saved action fires after a snapshot is saved (arguments: snapshot ID, snapshot data). The bbcr_webhook_body filter changes the webhook payload before it is sent. Others: bbcr_max_snapshots, bbcr_buffer_max_bytes, bbcr_max_events, bbcr_alert_throttle.
Are any features limited or locked?
No. Every feature in this plugin is included and free. The only limits are the storage settings above, which control disk space. Sanctuary Ranger Pro is a separate paid add-on with additional features (crash grouping, Slack/Discord/Teams alert formats and a weekly digest); it does not unlock or remove anything here.
What does Sanctuary Ranger Pro add?
Crash grouping (identical errors counted together with first seen and last seen), Slack, Discord and Microsoft Teams formats for the webhook alert, and a weekly digest email. It is a separate plugin that needs this one and a license key.
Can auto-quarantine break my site?
It only deactivates plugins you tick, and only after repeated fatal errors. Do not tick plugins that must stay running, such as payment or checkout plugins.
Does it catch errors from plugins that load before it?
It records fatal errors from any code that runs after Sanctuary Ranger loads, including earlier-loading plugins' fatals at shutdown, but it cannot log events from before it was loaded.
更新日志:
- Fix: a syntax error on the snapshot screen's replay help text that could stop the plugin from loading.
- New: a Settings link on the Plugins screen.
- New: a short, plain note about the optional Pro add-on on the Sanctuary Ranger screen. Nothing in this plugin is locked.
- Tested up to WordPress 7.0.
- New: "Replay in WordPress Playground" on every crash snapshot. Builds an approximate copy (PHP version plus the active plugins that are on WordPress.org) in a throwaway Playground site. Open it with one click or download the blueprint.
- New: "Likely cause" now recognises themes, must-use plugins and WordPress core, not only plugins.
- New: optional early recorder, a single must-use file you install or remove with a button. Never installed automatically.
- Snapshots now store the list of active plugins and the theme name, on your site only, so a replay can be built.
- Added developer hooks: the bbcr_snapshot_saved action and the bbcr_webhook_body filter.
- Webhook alerts now use wp_safe_remote_post, which refuses private network addresses.
- New: optional hook trace (developer setting, off by default) records the last hooks that ran in the crashing request.
- Works in WordPress Playground: recording no longer depends on file locking, and the screen explains Playground limits.
- Snapshot retention, log size, quarantine threshold and window are now fully configurable. No arbitrary caps.
- Added filters: bbcr_max_snapshots, bbcr_buffer_max_bytes, bbcr_max_events, bbcr_alert_throttle.
- Clearer wording in the quarantine settings.
- Renamed to Sanctuary Ranger Crash Recorder. Settings and data carry over.
- New: "Latest crash" banner at the top of the Sanctuary Ranger screen.
- Crash screen box and snapshots now show a short error headline; the stack trace is stored separately.
- Server paths are trimmed from messages, traces and file locations.
- Fix: snapshots now show the milestone where the crash happened instead of "shutdown".
- Fix: each request's summary line is now timestamped at the start of the request.
- New: administrators see a Sanctuary Ranger box with the error and a snapshot link on the crash screen.
- Fix: fatal errors are now recorded when WordPress's own fatal error handler ends the request.
- Fix: uninstall cleanup no longer depends on GLOB_BRACE.
- Replace error_reporting() call.
- Add status line to the Sanctuary Ranger screen.
- Initial release.