Follow-up to 🐛 Add rudimentary conflict prevention to the Config Auto-save end-point Active
Steps to reproduce
The content has either been modified by another user, or you have already submitted modifications. As a result, your changes cannot be saved.
Why it works after making change is that then the auto-save is re-created from the current input which goes through form submission process again.
If immediately after node is updated outside XB, the user instead tries to make an edit in the XB version then the user will get the error that ends with
Please refresh your browser to receive the latest changes and continue.
This is because the browsers xb auto-save has a autoSaveStartingPoint that is made with the prevision revision. See \Drupal\experience_builder\Controller\AutoSaveValidateTrait::getClientAutoSaveData
If then refreshed their browser they will be able publish. since this is same experience as if another user was editing the same node inside XB there would be no way for a user to tell the difference. When the user published they would erase any changes made outside XB, if they access to the fields changed
Before deciding on the technical solution we should decide that desired user experience is for when a content entity is edited outside of XB when there is current auto-saved version of the same
Possible solutions
Active
1.0
Auto-save
I chatted with @wimleers about this before making the issue we agreed that probably
The user should get a message that the entity was saved outside of XB and everything except the XB canvas has been reset to the saved version
Is the best solution for the time being
We should verify this works after reverting a revision too.