Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

Autosave sometimes does not work and gives different "Could not save property" error popups.

Vote:
 
Sometimes the autosave does not work and gives one of the below errors in a small popups:

"Could not save property. The page may have been changed by another user. Please reload the page"
"Could not save property, Please reload the page"


Reloading, as the error message suggests sometimes works. But, other times it leaves all fields locked for editing, and you need to click on to another page and then back to re-enable editing - and start over.

Has anyone experienced this and eventually have some tips for debugging and solving it?

It's CMS v12.22.1

Thanks in advance and best regards.
#310153
Edited, Oct 06, 2023 8:22
Vote:
 

Anyone has anything to this one?

#311491
Oct 26, 2023 8:58
Manoj Kumawat - Oct 26, 2023 9:46
Did you have any console errors or check in network tab if there is any fail request. This could potentially lead you to the root cause. I had this kind of issue when I had to update an existing property with a different datatype. Somehow property sync was not working. So I had to create another property. Check if you have the same scenario.
Vote:
 

You can probably see more information from log files. Without a full stacktrace it's almost impossible to understand what is wrong 

#311496
Oct 26, 2023 9:55
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.