Asset lock

Squiz Matrix Support
1
  1. We have "Refresh Interval" and "Lock Length" set as default value,
  2. From the Concepts Manual 3.18, it says,

[quote]While you are editing the content of the asset, you will continue to have the lock on the asset. When you

are no longer editing the asset, by default the lock will expire after 10 minutes. This means that you will

no longer have the lock on an asset and someone else will be able to make changes to it. If you have

finished editing the asset and know that someone else needs to edit the asset, instead of waiting 10

minutes, you can click the Release Lock(s) button.[/quote]

3. I found some backend users have over 200 locks and they are there forever

4. how comes? and how to resolve?

:blink:’ />:blink:<img src=‘http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/blink.gif’ class=‘bbc_emoticon’ alt=’:blink:

2

A user can have 200 expired locks. Locks don't clean up until someone else takes them.

3

Thanks Greg. I have done the testing and confirmed that 'expired lock' doesn't effect others to acquire the locks or the same guy re-acquire the locks. But the expired lock seems misleading the system admin to see whether the user really has locks.


From the testing I found something more interesting.

I used two browsers and two accounts.

Browser A: Firefox with admin account to monitor the lock status (Admin interface)

Browser B: IE with LDAP account to act the lock (Simple edit interface)



I had Browser B access the simple editing interface of an asset's details screen, content screen and metadata screen, then had it back to the front end. In Browser A, I browsed admin interface to check the asset locking status.


  • In the first checking rotation, details screen, content screen and metadata screen were locked by the LDAP user, expiry time were all ten minutes. I left the Browser A in details screen.[*]In the second checking rotation, details screen, content screen andmetadata screen were locked by the LDAP user, expiry time were eight and half minutes. I left the Browser A in details screen.[*]In the third checking rotation, details screen, content screen andmetadata screen were locked by the LDAP user, however details screen, content screen's expiry time were reset to nine mintues, xxx seconds, but the metadata screen's expiry time went on counting to six minues, xx seconds. I left the Browser A in details screen. [This is weird!!!][*]Then in the fourth and fifth checking rotation, details screen and content screen were reset twice to ten minutes after two minutes, it seemed that Browser B had got the top frame's Refresh Interval work for it, but Browser B was not in either simple editing interface nor admin interface.

Hope the above makes sense, may I have some clue?

:huh:
Robin
4

The only time the locks will be refreshed automatically is if that top bar is reloading. It definitely sounds like it was there somewhere. Are you sure the top bar was not hidden?

5

I had the Browser B in front end (neither simple editing interface nor admin interface)