[opencms-dev] Disable lock stealing

[Bart Elberg]

I have modified the following workplace templates to disable the "Steal 
Lock" function, but have been unable to get the chances to take effect:
    explorer_files_contextmenu
    extended_backoffice
    explorer_files_new_folder
    tasks_contextmenu

In each of these files, the lines '<contextentry 
name="explorer.context.overridelock"...' have been removed.  The same 
change made in the template file for my custom Backoffice modules works 
correctly.  I have tried several approaches to get the changes to take 
effect in the Explorer view:
    - updated template files in VFS, published, restarted opencms (and 
tomcat)
    - copied updated files to 
.../webapps/opencms/WEB-INF/ocsetup/vfs/..., restarted opencms (and tomcat)
    - generated a new WAR file, removed opencms application from webapps 
directory, installed new WAR file in Tomcat

None of these approaches seem to work.  Am I doing something wrong or 
are these template files not used to generate the context menus?

Configuration:
  OpenCms 4.6.1
  Tomcat 4.0.3
  MySQL
  Linux

Thanks,

Bart

------------------------
Bart Elberg wrote:

> Thanks Jorg.  That is a good approach for individual content 
> definitions, but I was hoping to disable it for everything.  By 
> changing the template "Backoffice" I was able to disable the feature.  
> I set the "href" attribute on the "overridelock" to an empty string:
>
> <contextmenue name="backofficelock">
>    <contextdisabled name="button.edit" 
> href="javascript:location.href=editUrl+'?idedit='+kontextparam;"/>
>    <contextdisabled name="explorer.context.delete" 
> href="javascript:location.href=deleteUrl+'?iddelete='+kontextparam;"/>
>    <contextspacer/>
>    <contextentry name="explorer.context.overridelock" href=""/>
> </contextmenue>
>
> this causes the steal lock function to do nothing.  Unfortunately the 
> context menu entry still shows up.  I will keep digging...
>
> Bart
>
> ------------
>
> Jorg Heymans wrote:
>
>> For some reason my posts to opencms-dev are not forwarded on to the 
>> newsgroup anymore. The last 5 msg's i sent or so never got there, 
>> hence this forward to your private adress.
>>
>>
>> ======================
>> My first idea would be to control this in the getLockState() and 
>> setLockstate() methods of your ContentDefinitionclass. Ultimately 
>> these methods get called when the locking state of a resource changes 
>> so you could put some code in there to prevent it I guess.
>>
>> Regards
>> Jorg Heymans
>>
>> On Wednesday 23 October 2002 18:55, Bart Elberg wrote:
>>
>>> Is there an easy way to disable lock stealing?  Template and code
>>> changes are fine if someone can provide some hints.
>>>
>>> I am using version 4.6.1
>>>
>>> Thanks
>>>
>>
>>
>>
>

-- 
Bart Elberg
Manager of Software Development
__________________________________________________
I.D.E.A.L. Technology Corporation - Orlando Office
http://www.idealcorp.com - 407.999.9870 x15