Frontend Editors Releasing Locks

Squiz Matrix Support
1

Hi all,


I am having some trouble with frontend editors not releasing locks when they either exit edit mode or click on our special logout link which just appends ?SQ_ACTION=logout& to the url.



The locks are not being released straight away when either of the above functions occur. even after the lock length time is reached, it either just refreshes the lock or the page goes a level of access that not even an admin can acquire a lock on.



I have also tried completely closing the frontend editors browser, but seems to make no difference.



We found that when the refresh interval was, for example, 2 mins and the lock length was, for example, 5 mins, the lock timeout would get to 3 mins and then refresh to 5 mins again!



Could someone please suggest the best way to setup the lock length/refresh time and the best way for a frontend user to logout.



Cheers, dhugg.

2

Locks are not automatically released by the Simple Edit system. The locks should release at a maximum of Logout+Lock Timeout. So, if your lock timeout is 5 minutes, then the locks should release no later than 5 minutes after the user logs out of simple edit mode.


If this is not happening, please let us know. Currently, there is no way to force an unlock via the Simple Edit interface.



However, System Administrator users (and root) can forcibly acquire locks on any page by clicking the "Acquire Lock" button and typing in the security code. This will force the asset to unlock and relock, so any changes the user may have made will be lost.

3

F.Y.I:
The same issue was mentioned in this thread.

A thread has been lodged for what i believe is also the same issue.

4

[quote]F.Y.I:
The same issue was mentioned in this thread.

A thread has been lodged for what i believe is also the same issue.

[right][post=“8094”]<{POST_SNAPBACK}>[/post][/right][/quote]





Hi I checked the bug fix, but this seams a silly way of solving this issue by introducing a %release_locks_button% for the editors to click on after changing the page status for approval.



could instead the logic to be applied to when you applying for approval, so that it automatically release the lock when you hit the commit button.



This way the editor could edit more pages, rather logging out the user from the system and for the user to log them self back in into the system to edit another page?

5

[quote]could instead the logic to be applied to when you applying for approval, so that it automatically release the lock when you hit the commit button.
[right][post=“13313”]<{POST_SNAPBACK}>[/post][/right][/quote]



From v3.12 you will be able to do this with triggers. :slight_smile:

6

You are able to setup a trigger to release lock on the simple edit screen in v3.12.



New trigger condition: URL matches

  • Trigger action will be executed when link contains the specified query string
  • You can specify a query string such as 'release_lock=1', example link in Layout content: 
        Exit Edit
    
Exit Edit and Release Lock


    New trigger action: Release lock
  • Release all currently held locks on the asset that the action is executing on



    Please do note that when you commit, you stay in the simple edit interface (not frontend view), hence lock will be re-acquired.
7

What is the event for this trigger? I have put the following link in my Details layout:

    <a href="./?release_lock=1" target="_top>Exit Edit and Release Lock</a></pre><br />
<br />
and created a trigger with a URL match on release_lock=1 to release the lock but it isn't working.<br />
<br />
Sarah
8

Use the "Asset Accessed" event. :slight_smile: