We're trying to find a way to increase the autosave period when editing content within a TinyMCE editor. We've tried ajusting the AutoSaveInterval value but this is apparently obsolete in 7.5.
Has anyone been able to configure this as the default setting is really intrusive and causing people to have to re-edit text that gets reverted during the autosave process.
I have the same problem. Did you find a soultion?
Hi Sara, no we've not found a solution yet. We're currently working with EPiServer to try and resolve it. They're unable to replicate it and we have another simpler EPiServer site that we don't experiecne the issue with.
The site we have the issue with is version 7.10 but the site with no issues is 7.5. What version are you running?
We can't replicate it in our dev environment. Only in customers test environment (ie10). We currently run version 7.13.
Update: We just deployed CMS.UI 7.14 to customers test enviroment. Now they cant replicate the issue. So maybe 7.14 solved it!
We tried upgrading to 7.14 but unfortunately that didn't help.
However we believe we’ve found the root cause of our problem. Before we upgraded our EPiServer from 7.5 to 7.10 we were having lots of content caching issues. People would change a property value in the “All properties” view and when they previewed the page the change they just made wouldn’t be visible. To get around this we added Html.FullRefreshPropertiesMetaData() to our base view. We passed a list of all the page’s properties to this method and that fixed the caching issue. It seems however that every time an auto save happens the Html.FullRefreshPropertiesMetaData() method was being called.
We also noticed that the CreateLayoutModel method in Alloy’s PageViewContextFactory was also called on every auto save. In this method we’d added code that looked up page properties on our start page and added them to the layoutmodel. Removing this lookup of the start page from CreateLayoutModel greatly improved the auto save but didn’t totally fix the issue. It wasn’t until we removed Html.FullRefreshPropertiesMetaData() from our root view that the auto save issue was truly resolved.
It also looks like the caching issues we were experiencing in 7.5 don’t seem to be present in 7.10 so removing Html.FullRefreshPropertiesMetaData() only seems to have has a positive impact.