smithsson68@gmail.com
Optimizely
Mar 4, 2011
visibility 8546
star star star star star
(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

error Please login to comment.
Latest blogs
Unit-Level Promotion Exclusions: Updated Behaviour and Developer Guide

Introduction Since Commerce 13, Optimizely Commerce Connect has supported two modes for promotion exclusion: order-level and unit-level. Order-leve...

Viet Anh Nguyen | Oct 23, 2026

Experimentation When the Agent Makes the Decision

When an agent enters the loop, an A/B test loses its obvious unit, its obvious variant and its obvious decision-maker. WebMCP, WebKit's objection, ...

Piotr | Oct 23, 2026 |

Virtual Opticon 2026: Where AI Can Improve DXP Delivery

Consider a campaign whose first draft takes ten minutes to generate but then waits five days for review. Faster drafting has helped one task. The...

Augusto Davalos | Oct 21, 2026

The Low-Level API Is Not Automatically Fast. Part 4: Counting Round Trips

The low-level Commerce DTO API is not automatically fast: counting the database round trips per imported row, and four fixes I would apply first.

Stanisław Szołkowski | Oct 21, 2026 |