Issue with Saving Changes in Umbraco Back Office After Switching Browser Tabs

umbraco / Umbraco-CMS

Umbraco is a free and open source .NET content management system helping you deliver delightful digital experiences.

MIT License

4.42k stars 2.67k forks source link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

10.8.6

Bug summary

Hello, I've been having issues with bugs in the Umbraco back end, my site is hosted on Umbraco cloud.

I'm getting bugs with not being able to save changes in the back office after I browse any other tab on my browser, whether changing content, document types, scripts, stylesheets or changes to a template. When I make a change to anything for the first time it works all fine, it seems to be an issue when I click on any other tabs on my browser to view the content on the front end, then go back to the tab I'm editing, make a change and try to save it either comes up with validation errors or the save button just never saves and spinning icon never saves. This isn't ideal as it means I can only work with one tab or have to reload the page everytime.

Here is a video example of the problem: https://www.loom.com/share/ce32db37b10242ae9f235e4b12b6da24?sid=7ad6c2a9-1b79-4d39-94e9-0a74cdc5d866

I've updated to the latest version of Umbraco CMS. Current versions: CMS 10.8.6 - Forms 10.5.7 - Deploy 10.2.7

Specifics

No response

Steps to reproduce

https://www.loom.com/share/ce32db37b10242ae9f235e4b12b6da24?sid=7ad6c2a9-1b79-4d39-94e9-0a74cdc5d866

Expected result / actual result

No response

Hi there @110percentdev!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
We'll replicate the issue to ensure that the problem is as described.
We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:

umbraco / Umbraco-CMS