You are here

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

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

Same filename in this branch
  1. 7.2 README.txt
  2. 7.2 modules/content_lock_timeout/README.txt
Same filename and directory in other branches
  1. 6.2 README.txt
  2. 6 README.txt
  3. 7.3 README.txt
  4. 7 README.txt
The "Content Lock" module

SUMMARY
=======
The purpose of this module is to avoid the situation where two people
are editing a single node at the same time. On busy sites with dynamic
content, edit collisions are a problem and may frustrate editors with
an error stating that the node was already modified and can't be
updated. 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.

Content locks that have been "forgotten" can be automatically released
after a configurable time span using the bundled content_lock_timeout
sub module.

Installation and configuration
==============================
https://www.drupal.org/project/content_lock

LINKS
=====

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

File

README.txt
View source 
  1. 

  2. The "Content Lock" module

  3. 

  4. SUMMARY

  5. =======

  6. The purpose of this module is to avoid the situation where two people

  7. are editing a single node at the same time. On busy sites with dynamic

  8. content, edit collisions are a problem and may frustrate editors with

  9. an error stating that the node was already modified and can't be

  10. updated. This module implements a pessimistic locking strategy, which

  11. means that content will be exclusively locked whenever a user starts

  12. editing it. The lock will be automatically released when the user

  13. submits the form or navigates away from the edit page.

  14. 

  15. Content locks that have been "forgotten" can be automatically released

  16. after a configurable time span using the bundled content_lock_timeout

  17. sub module.

  18. 

  19. Installation and configuration

  20. ==============================

  21. https://www.drupal.org/project/content_lock

  22. 

  23. LINKS

  24. =====

  25. 

  26. For a full description, visit the project page

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

  28. 

  29. Bug reports, feature suggestions, and latest developments:

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