ETBS Edit Conflict Guard
| 开发者 | etbsjp |
|---|---|
| 更新时间 | 2026年9月4日 22:10 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
WordPress already tells you when someone else is editing a post: the "currently editing" notice under the post title. That notice is only a warning, though. It does not stop the second editor from clicking Update or Publish, and it does not stop the save. If two people edit the same post around the same time, whoever saves last silently overwrites the other person's changes, and nothing in WordPress core prevents that.
ETBS Edit Conflict Guard adds a real, per-post exclusive lock on top of that notice. While one user has a post open for editing, it blocks every other user from saving it, and it tells them clearly why.
How it works
- Opening a post's edit screen tries to acquire a lock on that post (first person to open it gets the lock).
- While the edit screen stays open, the lock is automatically extended through the standard WordPress Heartbeat API.
- Clicking Save Draft, Update, or Publish (Classic Editor or Block Editor) checks the lock. If someone else holds it, the save is blocked and a modal explains why.
- The lock is released automatically when the save succeeds, or when Heartbeat stops (for example the tab is closed) and the lock's expiration time passes.
- The block is enforced on the server as well, on the Classic Editor's post save and the Block Editor's REST save, so the lock still holds even with JavaScript disabled or the connection unreliable.
- Lock expiration, in seconds.
- Post types to exclude from locking.
- Whether moving a locked post to trash is also blocked (off by default; when on, any move-to-trash of a locked post is blocked, even from the lock holder's own other tab — force delete is not affected).
- A live table of every post currently locked, with a per-row Force Release button for administrators.
- Block Editor trash notice. When the "Move to trash" action is blocked, the server correctly rejects it (the post stays published), but the Block Editor itself may briefly show a "Moved to trash" success notice anyway. This is WordPress core's own optimistic UI, not a lock failure — reloading the post list confirms the post was never actually moved.
- Bulk trash actions. If the trash guard is enabled and a bulk "Move to Trash" action from the post list includes a locked post, processing stops at that post; posts later in the batch are left unprocessed.
- Permanent deletion bypasses the trash guard. The trash guard only covers moves to the trash. A permanent delete that skips the trash entirely — for example
wp.deletePostover XML-RPC on a custom post type, which WordPress core deletes outright instead of trashing — is not blocked, even while the post is locked. - No Multisite support. Locks are not aware of, or shared across, sites in a Multisite network.
- Locks apply to the holder too. By design, even the user who holds the lock is blocked from saving the same post from a second tab or window. This is deliberate, not a bug — the plugin cannot tell two tabs from two different editors.
安装:
- Upload the plugin files to the
/wp-content/plugins/etbs-edit-conflict-guarddirectory, or install the plugin directly through the WordPress plugins screen. - Activate the plugin through the "Plugins" screen in WordPress.
- Go to Settings > Edit Conflict Guard to review the lock expiration, excluded post types, and trash guard option.
屏幕截图:
常见问题:
How is this different from the "Someone else is editing this" notice WordPress already shows?
That built-in notice is informational only; it does not stop a second user from saving. This plugin adds an actual block: if someone else holds the lock, clicking Save/Update/Publish is refused (the request is rejected with an HTTP 409 response) and the user sees a modal explaining why, instead of silently overwriting the other person's changes.
A lock seems stuck. How do I clear it?
Locks release automatically once their expiration time (set under Settings > Edit Conflict Guard) passes without the holder's edit screen sending a Heartbeat, for example if their browser tab was closed without saving. If you need it cleared immediately, an administrator can open Settings > Edit Conflict Guard and use the Force Release button next to that post in the "Currently Locked Posts" table.
Does this plugin work on Multisite?
Not currently. Locks are per-site; there is no cross-site awareness in a Multisite network.
I blocked a trash action, but the screen still said "Moved to trash". Did it fail?
No — the post was not moved. This happens only in the Block Editor: WordPress core shows an optimistic success notice before the server response arrives, and the server has already rejected the request. Reloading the post list will show the post still in its original status.
Can the person who holds the lock still lock themselves out?
Yes, deliberately. If the same user opens the same post in a second tab, the second tab is blocked from saving just like any other user would be. The plugin has no way to tell that both tabs belong to the same person, so it applies the same rule to everyone.
更新日志:
1.1.1
- Added a bundled Japanese translation. Translations delivered by translate.wordpress.org still take precedence once they are available.
- Renamed the plugin to ETBS Edit Conflict Guard.
- Translated all UI strings to English; translations are now handled through translate.wordpress.org instead of bundled files.
- Removed the bundled update checker (plugin-update-checker).
- Removed the dashboard widget.
- Removed the donation link from the Plugins list row.
- Moved the settings screen's inline script and styles into enqueued asset files.
- Renamed the plugin's PHP classes and constants so this plugin can be installed alongside its predecessor without a fatal error. Option keys and the lock table are unchanged, so existing settings are kept.
- The lock table and the cleanup task are now restored automatically if they go missing.
- Fix: uninstalling the plugin no longer deletes settings you configured (lock expiration, excluded post types). Only the plugin's own temporary lock data and its cleanup cron event are removed.
- Removed the "Requires at least" (WordPress) declaration. No verified minimum WordPress version exists for the APIs this plugin uses.
- Lowered the declared "Requires PHP" from 8.3 to 7.4.
- Added a "Request development" / donation link on the Plugins list row and the settings page footer.
- Initial release.