| 开发者 | miriyamcore |
|---|---|
| 更新时间 | 2026年9月23日 02:25 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
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.
pressbrake directory to /wp-content/plugins/, or install the ZIP from Plugins > Add New > Upload Plugin.No. Version 1.0 only confirms the change.
No. Notes are rendered only in plugin administration to users with plugin-management capabilities.
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_protected post metadata. It does not delete unrelated data.
No by default. Background and programmatic updates are left alone. Developers can opt into guarding programmatic post updates with the documented filter.
There is intentionally no public reset route. A super admin can change or remove a known code by entering the current code in PressBrake settings. If it is forgotten, a site owner with server access can use the documented PRESSBRAKE_BYPASS recovery mechanism temporarily, remove or update the code in a controlled maintenance session, and then remove the bypass constant.