Posted by jbrauer on March 8, 2008 at 8:20pm
Status: rejected; module already exists, and scope of fixing module too small for SoC
The idea behind this project would be to enable an editor to 'check-out' a node (and possibly blocks etc) with a preemptive lock that would prevent anyone else with the edit content permission from editing that page at the same time. While Drupal 6 at least preserves your changes it's frustrating to get done with an extensive edit only to find out that somebody else has popped in and edited the document while you were working on a masterpiece. There will also need to be administrative overrides for clearing stale locks.
Comments
I like this, it's related to
I like this, it's related to http://groups.drupal.org/node/9510 (or at least where I hope that would eventually lead) so we might need to fight it out a bit though.
If we can get that...
If we can get the diffs (http://groups.drupal.org/node/9510) in that sounds good. There may still be an argument for adding the ability to lock but it becomes a much lower priority. I'm not sure if there would still be a need for preventing the case where two major changes prevent a diff-based methodology from reconciling the changes.
--
Blog: Adding Understanding | Drupal Developer Search | Drupal Services: Brauer Ranch
--
Blog: Joshua Brauer dot com
I'd love the locking
We have an editorial team of 4-5 people doing edits all the time, and we run into concurrence problems pretty frequently (this is on 5.x which exacerbates the problem.) Even if your changes are saved and revisions can be reviewed to merge, these are pretty non-technical users. A locking system would be the best solution for them because it just avoids the situation entirely. I can see making it optional through an admin setting, because it's probably overkill for a lot of people.
This already exists
http://drupal.org/project/checkout
FunnyMonkey
Tools for Teachers
FunnyMonkey
Checkout needs work
The check-out module does exactly that but it is currently unmaintained (as far as I experienced). You need a patch to get the dev version working. A good task might be to collaborate with the checkout maintainer, or to take over the module, and to enhance it.
Agreed
+1 on this, it shouldn't be horribly difficult either I wouldn't think (assuming the original maintainer is actually responsive)
(This should have been a response to wmostrey)
content_lock
Well as checkout is no longer maintained you might better try http://drupal.org/project/content_lock