I love this module. It has the opportunity to solve one of the biggest usability problems in Drupal.
When users edit a node and click "Save" to save their changes, they are taken to the node view page. Then the average user sees they made a typo. Instead of clicking "edit" the user just hits "Back" on their browser, makes a few more edits, then clicks submit.
This is a big problem. Although they may have thought they were just making a few more edits to the page, they were editing an expired version of the node edit form which causes all kinds of problems, including the unhelpful error:
This content has been modified by another user, changes cannot be saved.
Your lock has been removed due to inactivity or by an administrator. Failed to regain the lock since the document has been changed since.
First, they can't figure out who else edited the page. (Because it told them it had been modified by another user, which isn't true.)
As soon as they use the back browser to go back to the previous page, an ajax callback should check the validity of the form. If the form has expired, it should stop the user from editing the page and ask them to reload the page. (Or better yet, it should just reload the node/##/edit page for them.)
(Even simply storing this in a cookie via javascript would fix the problem for most users while still providing a graceful fallback. I'd be happy to provide some example code if that would be helpful.)
Let me know if I can help in any way.
Closed: outdated
2.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I, too, made a small module to mitigate this error.
Back Button Disable Module →
.
I won't upload it as a proper Drupal module. Drupal 7 is soon end of life and uploading modules to drupal.org is a hideous and time-consuming chore.