Is this how it should work?
Vako - September 17, 2009 - 17:42
| Project: | Checkout (Content locking) |
| Version: | 6.x-2.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I get the following message after I click on Edit for one of the nodes:
This document is now locked against simultaneous editing. It will unlock when you navigate elsewhere.
However when I log-in to the same node with a different user I get the same message and still can edit the document.
Is this how it should work? is there a way that the second user will can get a message that another user has it open if we need to be notified when it is released.
thanks!
#1
We are having the same issue on our site. The user who goes into the node first gets the message, but anyone coming behind them can edit the node while the first person is in the node editing it.
I thought that user 2 was supposed to get a message stating the node was locked for editing by someone else.
#2
We have the same problem.
When a user starts editing a node a correct record is inserted in the table checkout.
But immediately after the insert this funktion
checkout.module line 214
function checkout_handle_request($uid) {...
// Check whether to release a previously edited node.
if ($previous_nid && (!$current_nid || $current_nid != $previous_nid)) {
checkout_release($previous_nid, $uid);
}
deletes the record.
We uncommented the line
//checkout_release($previous_nid, $uid);and it worked so far for us.
The problem is now that if the user navigates from the edit form without submitting, the node is still locked.
#3
I have also experienced a similar problem.
Checkout did not lock the node or update the table checkout, when editing in IE7/IE8. But worked fine in Firefox and Chrome.
Our site used the Clean-template.
After deactivating the Clean-template and using Garland instead, content lock works in IE also.
Seems to be a problem with this module and some themes...
Anyone experienced something similar?
#4
Subscribing.... Ran into this today.
#5
I went through a lot of testing by disabling various modules to see if I could find a culprit. For me, it was removing the Persistant Login as well as another content security module. I then rebuilt permissions and Content Locking appears to work again.
#6
This damn gremlin has returned. I wanted to verify if persistent login caused this so I reinstalled it. Now, even after uninstalling it, a locked document (according to the message) can still be edited by someone else while it is in a locked state.
Help???