Content locking (anti-concurrent editing) 7.x-1.1

This module is developed under github (http://github.com/EugenMayer/content_lock). Drupal CVS is only used for the releases.Features yet implemented * Concurrent editiing:The user gets notified when he trys to edit a node, which is edited by someone else. He cant enter the edit mode. * By node type: Configure content_lock to lock only specific nodes. * By format: Configure content_lock to lock only specific input formats. * No losing content by accident: User gets notified, if he wants to leave a edit form by abnormal conditions (close browser/window/link click). If the user confirms to leave, the edit lock gets automaticall removed by an ajax call. You can disable this behavior in the admin menu. * No forgotten locks: The user gets notified when he forgets to unlock a node (see below - uncleantransaction). He/she will be asked to click on a link to unlock this node. * Views integration: Show all open logs using any filters, as you have a views integration.Compatibility / DependenciesServer Dependencies- noneClient Browser Dependencies- noneInstallation 1. Just download and activate the module 2. Configure the user permissions 1. check out documents - This enables content locking when a user starts editing it. Note that even without this permission, users are still able to edit contents, they're just not protected against concurrent edits. 2. 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.GoalsBe safeThe main goal is to be 100% safe. That means that in no case a user should be able to edit a node, which is currently edited. Its rather chosen to be more user-unfriendly then removing the edit lock to early. In example the user can only remove that lock using save or the cancel button. Moving backwards in the browser or closing the browser does not yet unlock the node. Therefore the user will be notified and he can use a simple link to unlock the node (if he wishes too).API (from 2.0)hook_content_lock_skip_locking($node, $form_id, $form, $form_state)Implement this hook if you want to force the skipping of a lock out of any reasons or logic you want.Be sure to check $node for null, as it might no always be an object.If you return true, the lock wont be applied (so skipped).hook_content_lock_form_id_blacklist_alter($blacklist, $node = null)Implement this hook to be able to alter the blacklist of form_ids, where locking will be skipped.As parameter you get the current node, if the object is preset. You can implement your own logic hereIf you want to blacklist a node type, add $blacklist['your_form_id'] = TRUE;hook_content_lock_node_type_blacklist_alter($blacklist,$node)Implement this hook to be able to alter the blacklist of node_types, where locking will be skipped.This hook only gets called if a node object is set at all (as otherwise types wont be able to be checked).If you want to blacklist a node type, add $blacklist['your_type_machine_name'] = TRUE;hook_content_lock_locked($nid,$uid)This hook gets called, when a lock gets set. Implement this if you want to trigger any actions when a lock gets applied.Maintainers * Eugen Mayer * Nathan Phillip BrinkThis plugin was sponsored by KontextWork GbR for Drupal WikiIf you like the module, please write a comment here http://drupal.org/node/711000 to motivate people working on it!

Requirements:	No special requirements
Platforms:	PHP
Keyword:	Blacklist,  Called,  Check,  Click,  Configure,  Content,  Contents,  Dependencies,  Documents,  Enables,  Locking,  Locks,  Logic,  Module,  Notified,  Object,  Unlock,  Users
Users rating:	0/10