Diagnostics, and reading one before you share it

Quick answer

The diagnostic pages show what the plugin actually resolved on your server — paths, batch rows, which files are loaded — and they are off by default because that is more detail than needs to be reachable day to day.

Turn them on under Settings when you are investigating something, and turn them off again afterwards.

Three locks, not one

Reaching a diagnostic page requires all of:

• administrator access;
• a signed link, generated from the Settings page — the URL cannot be guessed or bookmarked indefinitely;
• either the Settings toggle, or WPBR_ENABLE_DIAGNOSTICS defined in wp-config.php.

The toggle alone does not open anything to anybody who is not already an administrator. It exists because a page that prints server paths should not be reachable on a whim, even by someone entitled to see it.

What they show

Resolved staging and backup paths as the plugin computed them, which is usually the answer when uploads land somewhere unexpected. The raw rows of a batch, including the stored paths and statuses, which is the answer when a row behaves differently from how it reads on screen. And which plugin files are loaded, which is the answer when an extension is or is not doing what you expect.

Before you share one

Read it first. These pages show absolute server paths and your site's directory layout. None of it is a credential, and none of it should be a surprise — but it describes your server, and a screenshot pasted into a public forum describes it to everybody.

What is deliberately not on these pages: no database credentials, no API keys, no wp-config.php contents, no post or user data beyond the batch rows themselves.

If you are sending something to support, send the specific page that shows the problem rather than everything, and say what you were doing when it happened. A resolved path plus the row that misbehaved is usually the whole answer.

The Activity Log is the other half

Under Bulk Replace → Activity Log, and it needs no toggle. Every replacement, rollback, verification and cleanup is recorded there with what happened and why — including the refusals. For "what did this batch actually do", the log is the record and the diagnostic pages are the explanation.