Description
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.
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.
Screenshots
Installation
- Upload the
pressbrakedirectory to/wp-content/plugins/, or install the ZIP from Plugins > Add New > Upload Plugin. - Activate PressBrake.
- Review Settings > PressBrake.
- Use the PressBrake Protection panel on content and the PressBrake control links on the Plugins screen.
FAQ-e
-
Does PressBrake create redirects after a URL change?
-
No. Version 1.0 only confirms the change.
-
Are plugin notes public?
-
No. Notes are rendered only in plugin administration to users with plugin-management capabilities.
-
What happens on deactivation or uninstall?
-
Deactivation keeps all data. Uninstall also keeps data unless “Delete PressBrake data when uninstalled” was deliberately enabled. On multisite, each site is evaluated independently; network plugin records are removed only when every site opted into cleanup. Eligible cleanup removes
pressbrake_settings,pressbrake_data_version, plugin records, and_pressbrake_protectedpost metadata. It does not delete unrelated data. -
Does PressBrake block WP-CLI, imports, cron, autosaves, or revisions?
-
No by default. Background and programmatic updates are left alone. Developers can opt into guarding programmatic post updates with the documented filter.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“PressBrake” is open source software. The following people have contributed to this plugin.
Contributors
Translate “PressBrake” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.0
- Initial release with URL Brake, Content Brake, and Plugin Brake.