[opencms-dev] locking and stealing locks within projects

Leon Oosthuizen@iCommerce Leon.Oosthuizen at za.didata.com
Wed Aug 15 11:26:57 CEST 2001


A few questions (OpenCMS version 4.4.0):

1)  Why can anyone able to lock a resource (when unlocked), steal the lock
when it's already locked by someone else?  This defeats the purpose of
locking in the first place.

2)  Shouldn't steal lock only be available to the Admin group and the
current project admin group for resources of the current project?

3)  The current locking of a resource is allowed if:
     - cur proj is NOT online proj
     - cur user has access to cur proj
     - resource is part of cur proj
     - no parent folders of resource is locked by another user
    This doesn't give the project's manager any more rights than a project's
user (except publishing).  If some else takes away a resource's 'group write
access', the project manger cannot edit it.  Why isn't project manager
status taken into account for locking/stealing lock/editing access?
According to the user manual it should be taken into account.

4)  Is there a way to structure a project (folder) in such a way that a
project user can only lock and change (including transfer of ownership)
resources they own (i.e. curent user is resource owner), while a project
manager of the project can lock/steal lock/change any resource in the


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.


More information about the opencms-dev mailing list