PressBrake adds a lightweight safety layer around three common administrative mistakes:

changing a published URL without considering existing links;
trashing, deleting, unpublishing, or restructuring important content; and
deactivating or deleting a plugin without remembering why it is required.

Each brake is independent and can be disabled under Settings > PressBrake. Disabled brakes do not register their operational hooks or load their assets.

Optional deletion confirmation code

By default, PressBrake works exactly as before: its existing confirmation paths remain available and no code is required. A super admin can optionally set a deletion confirmation code in Settings > PressBrake.

When a code is set, strict mode is active. Only super admins can change PressBrake settings or manage content and plugin protection controls. Users who already have the normal WordPress permission to delete content or manage plugins still use the usual WordPress screens, but protected content trash/permanent deletion and protected plugin deactivation/deletion require the code. The code is stored only as a WordPress password hash. On multisite, one code applies across the network.

Strict mode is an administrative safety control, not a boundary against a site owner with server access or someone able to deactivate PressBrake. The documented PRESSBRAKE_BYPASS recovery mechanism remains available for emergencies.

URL Brake

Warns before a slug or parent change alters the URL of published posts, pages, or supported public custom post types. It shows the existing and proposed URL when WordPress can calculate both. PressBrake does not create redirects.

Content Brake

Adds a PressBrake Protection panel to supported content. Protected items require a deliberate, action-specific override before destructive or structural changes. The configured static front page and posts page receive enhanced warnings without being silently marked as manually protected.

Plugin Brake

Adds a private administrative note and optional protection control to each installed plugin. Protected plugins require a deliberate override before individual deactivation or deletion and are skipped by bulk actions. Multisite network controls use network-scoped data and capabilities.

PressBrake is not a security firewall. It does not prevent a determined administrator with server access from changing the site. It prevents accidental actions through supported WordPress administrative workflows.

No data leaves the website. PressBrake makes no external requests, adds no frontend cookies, and stores no personal data. Protection settings, post metadata, and private plugin notes remain inside WordPress.

Emergency recovery

If a protected plugin causes a problem, add this line to wp-config.php above the line that says to stop editing:

define( 'PRESSBRAKE_BYPASS', true );

All PressBrake protections are then bypassed and an administrator notice is shown. Settings, notes, and protection records remain intact. Remove the constant after recovery. Server access can also be used to rename or remove PressBrake itself; this plugin is an accident-prevention layer, not an access-control boundary.