Click publish shortly after making a change can lead to error

Needs review for the general idea. Then we could clean it up or just scrap it

This screams "race conditions", and it's definitely in the Auto-save realm, so asking @larowlan to review the general idea :)

I think this is a good idea, we can update the cached version in the store

Given @larowlan's +1, let's clarify the plan/intent here. I'd like the issue title to reflect what this MR aims to do, not describe the symptom 🙏

left one minor comment

Added a related issue 🐛 Publishing the currently edit page causes 'another user has changed this content' error Active which is in the same ballpark

Merge this on the client side with the existing list of auto-saves

Does that client-side issue already exist?

Can we get the title updated to reflect what the scope is?

NW per @larowlan's https://git.drupalcode.org/project/experience_builder/-/merge_requests/9...

I am investigating whether this should be postponed on 📌 [PP-1] Enforce conflict enforcement outside of tests and e2e tests Postponed

Bump 😇

re #13, yes I think we should postpone as that one will change how the client handles auto-saves

And then we can re-open this issue and see if the problem remains in the same way

We should have an explanation in the summary of the back-end/front-end interaction that leads to this problem

Added #17 to the issue summary — is that what you were looking for, @tedbow?

@wim leers thanks. Sorry I wasn't clear. I updated summary

I don't think we can solve this on the back-end allow and depending on how the front-end whats to handle this we might not need any back-end changes

I proposed what I consider the "safest" solution but I am not sure that will offer the UX we want

I think we can release without fixing this bug. We should still prioritize this as soon as possible but it doesn't seem like a must have for the releases.