When editing a table, if a previous lock was not released you will get an oops:
Try Again to see if user has finished editing yet.
Edit Anyway to edit the topic anyway.
This is even if the lock is held by one self. The nescessesary post parameters doesn't survive the oops screen, so clicking "Edit Anyway" is no good (will show regular edit screen, not EditTablePlugin
Step to reproduce:
- Be in a topic using EditTablePlugin
- Edit the topic regularly, press "back" in browser instead of saving
- Try clicking the "Edit button" of a table set to use EditTablePlugin
If possible I think simply breaking the lock quietly under all circumstances could be a way to proceed. EditTablePlugin
doesn't work in forms, so the risk of content loss would be minimal as the merge feature works reliable for topic content.
This one is highly annoying for users and many don't know what to do when they click edit anyway and end up in normal edit mode. The only actual way out is to save the topic and then try edit table again.
Changing to urgent and putting it on my hotfix candidate list
Isn't this a bug of the core TWiki? Any topic locked by onself should not produce a locked message. (That was BTW the spec of Cairo.)
I think the core is ok, in this case it is just the plugin that is (too) careful on the lock checking.
I have de-activated the check for locks and released a new version to twiki.org.
This fix introduced a bug for TWiki releases prior to Dakar: Topic lock check is no longer done. Fixed in Item2829
Closed in 4.0.5 KJL