Title: Sanctuary Ranger Crash Recorder
Author: rachelmharrisoncoaching
Published: <strong>October 13, 2026</strong>
Last modified: October 13, 2026

---

Search plugins

![](https://ps.w.org/sanctuary-ranger-crash-recorder/assets/banner-772x250.png?rev
=3743144)

![](https://ps.w.org/sanctuary-ranger-crash-recorder/assets/icon-256x256.png?rev
=3743144)

# Sanctuary Ranger Crash Recorder

 By [rachelmharrisoncoaching](https://profiles.wordpress.org/rachelmharrisoncoaching/)

[Download](https://downloads.wordpress.org/plugin/sanctuary-ranger-crash-recorder.zip)

 * [Details](https://wordpress.org/plugins/sanctuary-ranger-crash-recorder/#description)
 * [Reviews](https://wordpress.org/plugins/sanctuary-ranger-crash-recorder/#reviews)
 *  [Installation](https://wordpress.org/plugins/sanctuary-ranger-crash-recorder/#installation)
 * [Development](https://wordpress.org/plugins/sanctuary-ranger-crash-recorder/#developers)

 [Support](https://wordpress.org/support/plugin/sanctuary-ranger-crash-recorder/)

## Description

When a WordPress site hits a fatal error, you usually get a stack trace and nothing
about what led up to it. Sanctuary Ranger keeps a short rolling log of recent activity
and freezes a snapshot the moment a fatal error happens.

**What it records (cheap events only):**

 * 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

**What it never records:** cookies, authentication headers, POST bodies, query-string
values, email contents or recipients.

**Optional features (all off by default):**

 * 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

Sanctuary Ranger does not prevent crashes or fix them. It helps you find the cause
faster.

**Optional Pro add-on**

Everything described above is free and fully working. A separate add-on, Sanctuary
Ranger Pro, is sold on rachel-m-harrison.com and adds crash grouping, Slack, Discord
and Microsoft Teams alert formats, and a weekly digest email. It is installed as
its own plugin and needs a license key ($39 per year for one site). This plugin 
contains no locked features and works the same with or without it.

### External services

This plugin contacts no external service by default. If you click “Open in Playground”
on a snapshot, your browser opens https://playground.wordpress.net with a blueprint
in the link. The blueprint contains the PHP version and the WordPress.org slugs 
of your active plugins, and it stays in the part of the address after “#”, which
browsers do not send to servers. Playground then downloads those plugins from WordPress.
org. This plugin itself sends nothing, and nothing happens until you click. Playground
terms and privacy policy: https://wordpress.org/about/privacy/

The “Go Pro” button on the Tools > Sanctuary Ranger screen is a plain link to https://
rachel-m-harrison.com/rmh-shop/?buy=sanctuary-ranger-pro. Nothing is sent to that
address unless you click it.

If you enter a webhook URL in Tools > Sanctuary Ranger, the plugin sends a POST 
request containing a one-line error summary and your site URL to that address when
a fatal error occurs. You choose the destination; the plugin does not use any third-
party service of its own.

## Installation

 1. Upload the plugin folder to `/wp-content/plugins/` or install it from the Plugins
    screen.
 2. Activate it.
 3. Open Tools > Sanctuary Ranger to view snapshots and adjust settings.

## FAQ

### 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.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Sanctuary Ranger Crash Recorder” is open source software. The following people 
have contributed to this plugin.

Contributors

 *   [ rachelmharrisoncoaching ](https://profiles.wordpress.org/rachelmharrisoncoaching/)

[Translate “Sanctuary Ranger Crash Recorder” into your language.](https://translate.wordpress.org/projects/wp-plugins/sanctuary-ranger-crash-recorder)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/sanctuary-ranger-crash-recorder/),
check out the [SVN repository](https://plugins.svn.wordpress.org/sanctuary-ranger-crash-recorder/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/sanctuary-ranger-crash-recorder/)
by [RSS](https://plugins.trac.wordpress.org/log/sanctuary-ranger-crash-recorder/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.3.1

 * 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.

#### 0.3.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.

#### 0.2.1

 * 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.

#### 0.2.0

 * 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.

#### 0.1.8

 * 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.

#### 0.1.7

 * Clearer wording in the quarantine settings.

#### 0.1.6

 * Renamed to Sanctuary Ranger Crash Recorder. Settings and data carry over.

#### 0.1.5

 * New: “Latest crash” banner at the top of the Sanctuary Ranger screen.

#### 0.1.4

 * 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.

#### 0.1.3

 * 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.

#### 0.1.2

 * New: administrators see a Sanctuary Ranger box with the error and a snapshot 
   link on the crash screen.

#### 0.1.1

 * 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.

#### 0.1.0

 * Initial release.

## Meta

 *  Version **0.3.1**
 *  Last updated **1 day ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **7.0.7**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [crash](https://wordpress.org/plugins/tags/crash/)[debugging](https://wordpress.org/plugins/tags/debugging/)
   [fatal error](https://wordpress.org/plugins/tags/fatal-error/)[monitoring](https://wordpress.org/plugins/tags/monitoring/)
   [troubleshooting](https://wordpress.org/plugins/tags/troubleshooting/)
 *  [Advanced View](https://wordpress.org/plugins/sanctuary-ranger-crash-recorder/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/sanctuary-ranger-crash-recorder/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/sanctuary-ranger-crash-recorder/reviews/)

## Contributors

 *   [ rachelmharrisoncoaching ](https://profiles.wordpress.org/rachelmharrisoncoaching/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/sanctuary-ranger-crash-recorder/)