First of all...the content locking functionality is working perfectly, thanks for such a great module!

I noticed that if a user is trying to edit a locked node, the user does not get the red box error ("This document is locked for editing by xxx since xxx") unless the role they belong to has the "administer checked out documents" permission granted. If they don't have that permission and they try to edit a locked node, the edit button does nothing and no error is displayed.

In my install the "Show lock / unlock messages" is checked and the "check out documents" permission is checked for users.

Am I missing something in the permissions or is this the intended behavior? I don't want to give the users administer rights to unlock the nodes.

It's a minor UI issue..just want to avoid users bombarding me with emails asking why the edit button doesn't work :)

Comments

EugenMayer’s picture

EugenMayer commented

Actually this sounds like a bug. Sure the user should be notified when he cant edit a node, not matter he can administer the lock or not. I will look into that, thanks for the good catch!

EugenMayer’s picture

EugenMayer commented
Priority: Normal » Minor
bdanin’s picture

bdanin commented

Ran across the same issue, and am interested to hear about the fix. Thanks for the module though, very effective (this would ideally be part of Core imo)!

omaster’s picture

omaster commented

oh hey all I had the same problem.

I posted the solution in this issue.

http://drupal.org/node/926258

It is actually quite a simple fix for the owner to make this work properly.

EugenMayer’s picture

EugenMayer commented
Status: Active » Closed (duplicate)

dublicate of http://drupal.org/node/914342

Will be fixed in the upcoming release