G'day … we're using Matrix 4.6.1, and on this and previous versions we've had problems with staff 'losing the lock' on standard pages that they're editing in the Matrix admin interface - so that when they finally press "Commit" Matrix throws away all their changes.
This is definitely a problem in Internet Explorer, though Firefox seems to work ok. It doesn't affect people all the time: yesterday a colleague lost work twice, but this morning the same staff member with exactly the same browser/computer, etc is having the locks on the page renewed correctly.
We've got the refresh interval and lock length still on their default settings of 120 and 600 seconds respectively. People who lose locks seem to do so after about 10 minutes of not pressing Commit, so I guess the 600 seconds length is working but the 120 second refresh is not.
Does anyone else have problems 'losing' locks? What have you done about it?
I'm tempted to extend the lock length to 1800 seconds or something like that, even though it shouldn't be necessary. Has anyone else tried this?
I wonder if it'd be worth the system having a built-in JavaScript-powered countdown clock that appears when the system has been unable to renew the locks and you've only got a couple of minutes left to press Commit before you lose your work.
Cheers,
Warwick
[quote]
G'day … we're using Matrix 4.6.1, and on this and previous versions we've had problems with staff 'losing the lock' on standard pages that they're editing in the Matrix admin interface - so that when they finally press "Commit" Matrix throws away all their changes.
This is definitely a problem in Internet Explorer, though Firefox seems to work ok. It doesn't affect people all the time: yesterday a colleague lost work twice, but this morning the same staff member with exactly the same browser/computer, etc is having the locks on the page renewed correctly.
We've got the refresh interval and lock length still on their default settings of 120 and 600 seconds respectively. People who lose locks seem to do so after about 10 minutes of not pressing Commit, so I guess the 600 seconds length is working but the 120 second refresh is not.
Does anyone else have problems 'losing' locks? What have you done about it?
I'm tempted to extend the lock length to 1800 seconds or something like that, even though it shouldn't be necessary. Has anyone else tried this?
I wonder if it'd be worth the system having a built-in JavaScript-powered countdown clock that appears when the system has been unable to renew the locks and you've only got a couple of minutes left to press Commit before you lose your work.
Cheers,
Warwick
[/quote]
Hi Warwick,
The top bar in the admin interface (the one with quick search) has a javascript which refreshed the locks on the main frame according to what is configured for refresh interval.
If the locks are not refreshing thats the first place to check. Is the top frame appearing broken?
What I have seen is when the top frame refreshes, if the request goes wrong there is a 404 returned. This prevents the locks from being refreshed. If the user see a broken top frame they can try reloading just that frame and it should all work alright.
Hope this helps.
Ash
Thanks for your reply Ash. I don't think the top frame was failing to refresh but I'll keep an eye on it for next time if we have this problem.