You are here

Home » API reference » Content locking (anti-concurrent editing) 6

README.txt in Content locking (anti-concurrent editing) 6

Same filename in this branch
  1. 6 README.txt
  2. 6 modules/content_lock_timeout/README.txt
Same filename and directory in other branches
  1. 6.2 README.txt
  2. 7.3 README.txt
  3. 7 README.txt
  4. 7.2 README.txt
/* $Id$ */
-- Fork --

This module is a fork of the module http://drupal.org/project/checkout and has 
been nearly completely reweritten since then

-- SUMMARY --
This module implements a pessimistic locking strategy, which means that content
will be exclusively locked whenever a user starts editing it.  The lock will be
automatically released when the user submits the form or navigates away from
the edit page.

Users may also permanently lock content, to prevent others from editing it.  
Content locks that have been "forgotten" can be automatically released after a
configurable time span.

For a full description visit the project page:
  http://drupal.org/project/content_lock
Bug reports, feature suggestions and latest developments:
  http://drupal.org/project/issues/content_lock


-- INSTALLATION --

1. Install as usual, see http://drupal.org/node/70151 for further information.

2. Configure user permissions at User management >> Permissions:

   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.

   keep documents checked out - Whether to allow users to keep content locked
     across edits.  This will enable a similar named checkbox on the content
     edit form.

   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.

3. Configure the module at Content management >> Post settings.

   Show lock / unlock message - Make content_lock more verbose, informing a
     user when he locks a node and about his inconsideration when he visits
     one node while he has kept another node locked.

   Add cancel button - Adds a link in a node's edit form to cancel the edit,
     letting the user intentionally navigate away from the Edit page without
     being asked for confirmation by a javascript dialog.

-- CREDITS --
Current authors:
Eugen Mayer http://drupal.org/user/108406
Nathan Phillip Brink http://drupal.org/user/108406


Original authors:
Stefan M. Kudwien
Joël Guesclin

File

README.txt
View source 
  1. /* $Id$ */

  2. -- Fork --

  3. 

  4. This module is a fork of the module http://drupal.org/project/checkout and has 

  5. been nearly completely reweritten since then

  6. 

  7. -- SUMMARY --

  8. This module implements a pessimistic locking strategy, which means that content

  9. will be exclusively locked whenever a user starts editing it.  The lock will be

  10. automatically released when the user submits the form or navigates away from

  11. the edit page.

  12. 

  13. Users may also permanently lock content, to prevent others from editing it.  

  14. Content locks that have been "forgotten" can be automatically released after a

  15. configurable time span.

  16. 

  17. For a full description visit the project page:

  18.   http://drupal.org/project/content_lock

  19. Bug reports, feature suggestions and latest developments:

  20.   http://drupal.org/project/issues/content_lock

  21. 

  22. 

  23. -- INSTALLATION --

  24. 

  25. 1. Install as usual, see http://drupal.org/node/70151 for further information.

  26. 

  27. 2. Configure user permissions at User management >> Permissions:

  28. 

  29.    check out documents - This enables content locking when a user starts

  30.      editing it.  Note that even without this permission, users are still

  31.      able to edit contents, they're just not protected against concurrent

  32.      edits.

  33. 

  34.    keep documents checked out - Whether to allow users to keep content locked

  35.      across edits.  This will enable a similar named checkbox on the content

  36.      edit form.

  37. 

  38.    administer checked out documents - View and release locked contents of all

  39.      users.  This enables the administrative tab on Content management >>

  40.      Content.  Note that even without this permission, users can manage their

  41.      own content locks on their profile page.

  42. 

  43. 3. Configure the module at Content management >> Post settings.

  44. 

  45.    Show lock / unlock message - Make content_lock more verbose, informing a

  46.      user when he locks a node and about his inconsideration when he visits

  47.      one node while he has kept another node locked.

  48. 

  49.    Add cancel button - Adds a link in a node's edit form to cancel the edit,

  50.      letting the user intentionally navigate away from the Edit page without

  51.      being asked for confirmation by a javascript dialog.

  52. 

  53. -- CREDITS --

  54. Current authors:

  55. Eugen Mayer http://drupal.org/user/108406

  56. Nathan Phillip Brink http://drupal.org/user/108406

  57. 

  58. 

  59. Original authors:

  60. Stefan M. Kudwien

  61. Joël Guesclin