smithsson68@gmail.com
Mar 4, 2011
  8109
(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
Bypassing WAF Blocking in Optimizely CMS 11 with Custom Base64 Properties

Introduction As Optimizely developers, we frequently encounter requirements to allow editors to inject third-party scripts into the head or body of...

Amit Mittal | Mar 2, 2026

Inspect SaaS CMS Packages Without Losing Your Sanity (Package Explorer Update)

Optimizely export packages have quietly become more complex. Inline (nested) blocks in CMS 12 and PaaS solutions weren’t always displayed clearly,...

Allan Thraen | Mar 1, 2026 |

Unstoppable: Insights from Optimizely’s 2026 UK Partner day

Over 150 Optimizely partners met in Shoreditch for the 2026 London Partner Kick Off. The theme was very much Opal with a side order of Optimizely's...

Mark Welland | Feb 27, 2026

What you need to run better experiments today

A practical, end-to-end playbook for higher quality A/B tests: conditional activation, targeting, metrics, power, SRM, and decision discipline.

Hristo Bakalov | Feb 27, 2026 |

Catalog Traversal in Action. Part 2: Real-World Scheduled Job Patterns

In my previous post, I showed how to build a memory-efficient catalog traversal service for Optimizely Commerce. The service uses streaming to...

Stanisław Szołkowski | Feb 24, 2026 |

Resource Editor - A localization management tool for Optimizely CMS

If you have worked with Optimizely CMS for any amount of time you know that managing localization through XML files can be tedious. Content type...

Per Nergård (MVP) | Feb 23, 2026