Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more

smithsson68@gmail.com
Mar 4, 2011
  7641
(3 votes)

Configuring the new page auto-save function in CMS 6 R2

CMS 6 R2 comes with a handy new page auto-save function which as the name suggests automatically saves draft copies of a page when it is being edited. If the browser should then crash before you have a chance to save your changes in the normal way, next time you log-in, you will be presented with a small pop-up to say that you have a draft copy of a page which can be recovered.

By default a page draft will be automatically saved after 1 minute and then updated every 1 minute after that. The draft will be kept for 3 days and then automatically deleted.

These two values can be changed by adding settings to the episerver site settings section in the episerver.config file. Both should be in the format that can be parsed to a System.TimeSpan.

The following example changes the auto save interval to 10 seconds and the draft retain period to 20 days

<episerver xmlns="http://EPiServer.Configuration.EPiServerSection">
    <site>
        <siteSettings autoSaveInterval="0:0:10" draftRetainPeriod="20.0:0:0" />
    </site>
</episerver>
Mar 04, 2011

Comments

Eric
Eric Mar 4, 2011 11:21 PM

hopefully this stuff will be in the documantation or sdk as well? :)

Eric
Eric Mar 4, 2011 11:22 PM

hmm i dont think the commentsystem is working alright..?

May 26, 2011 02:15 PM

HI Paul

I entered these two tags in Webconfig file in SiteSettings.But i cannot able to see this feature.
I have to do something else in configuration.I tried this after killing an browser instance but next time not able to see any popup.

Thanks in Advance!

smithsson68@gmail.com
smithsson68@gmail.com Feb 14, 2014 11:12 AM

This feature is obselete from CMS 7.5
http://world.episerver.com/Documentation/Class-library/?documentId=cms/7.5/7418b2cf-4d31-f751-1643-d47e2d1ae358

Please login to comment.
Latest blogs
Removing a Segment from the URL in Optimizely CMS 12 using Partial Routing

Problem Statement In Optimizely CMS 12, dynamically generated pages inherit URL segments from their container pages. However, in certain cases, som...

Adnan Zameer | Mar 14, 2025 |

Optimizely Configured Commerce and Spire CMS - Figuring out Handlers

I recently entered the world of Optimizely Configured Commerce and Spire CMS. Intriguing, interesting and challenging at the same time, especially...

Ritu Madan | Mar 12, 2025

Another console app for calling the Optimizely CMS REST API

Introducing a Spectre.Console.Cli app for exploring an Optimizely SaaS CMS instance and to source code control definitions.

Johan Kronberg | Mar 11, 2025 |

Extending UrlResolver to Generate Lowercase Links in Optimizely CMS 12

When working with Optimizely CMS 12, URL consistency is crucial for SEO and usability. By default, Optimizely does not enforce lowercase URLs, whic...

Santiago Morla | Mar 7, 2025 |