When saving contents on an asset / screen that has its locks released automatically, the Seamless save plugin displays a message of "Error, your locks have been released".
This behaviour is incorrect since the changes have actually been saved.
Some workarounds:
Hardcoded list of assets / screens that are known to have their locks released automatically and alter the way messages are displayed based on this logic (not ideal) or;
Look for something on the asset submit form that will hint at the fact that this screen has its locks released automatically.
When saving contents on an asset / screen that has its locks released automatically, the Seamless save plugin displays a message of "Error, your locks have been released".
This behaviour is incorrect since the changes have actually been saved.
Some workarounds: