Content locking (anti-concurrent editing)
This module prevents multiple users from editing the same content simultaneously. It can be configured to lock specific content types or input formats, and users are warned if they try to edit content already being edited. The module can also remind users to unlock content they've forgotten about and allows administrators to manage all locks.
Features
- Block concurrent editing: When a user is editing a node, any other user that attempts to edit the same node will be blocked from doing so, and notified that the content is already being edited.
- By node type: This module can be configured to only lock certain content types against concurrent editing.
- By format: This module can be configured to only lock specific input formats against concurrent editing.
- Avoid forgotten locks: Users are notified if they forget to unlock a node. They will be prompted to click on a link to unlock the node.
- Views integration: All open locks can be listed using Views.
Installation
- Download and activate the module as normal.
- Configure the user permissions:
- check out documents - This enables content locking when a user starts editing a node. Note that even without this permission, users are still able to edit contents, they're just not protected against concurrent edits.
- administer checked out documents - View and release locked contents of all users. This enables the administrative tab on
Content management >> Content. Note that even without this permission, users can manage their own content locks on their profile page.
Goals
Safe content editing
The main goal is to be 100% safe. That means that under no circumstances should a user be able to edit a node that another user is already editing. It was a design decision to prefer a somewhat heavy-handed approach rather than risk removing a lock too early. For example, a user can only remove their lock using the save or the cancel buttons, as opposed to simply closing their browser window.
API
API documentation can be found at: content_lock.api.php.
User Reports
Please post to the issue queue to help make the module better. Feel free to provide patches and suggestions too.