smithsson68@gmail.com
Mar 4, 2011
  8292
(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
Four database surprises when upgrading from CMS 11 to CMS 13

We're in the middle of migrating a fairly large site from CMS 11 / .NET Framework to CMS 13 / .NET 10. The code migration is one thing, but the...

Per Nergård (MVP) | Jun 12, 2026

Designing ODP Real-Time Audiences for CMS Personalization and Experimentation

A practical look at when to use ODP Real-Time Audiences, how to build them, and how they fit into CMS personalization and Feature Experimentation.

Wojciech Seweryn | Jun 11, 2026 |

Unlock Experimentation with Content Variations in CMS 13

Part 1 argued that Content Variations is the CMS 13 feature that didn't get the keynote but should have. This is the follow-up: wiring those...

Piotr | Jun 11, 2026

umage.ai is now an Optimizely Silver Solution Partner

umage.ai is officially an Optimizely Silver Solution Partner. The badge formalises an alignment that was already there — agent-driven Optimizely wo...

Allan Thraen | Jun 10, 2026 |

Why Optimizely's MCP Servers Offering Matters

MCP (Model Context Protocol) is what enables, connecting AI agents directly to enterprise tools. With Optimizely OPAL and Optimizely MCP servers,...

K Khan | Jun 9, 2026

A day in the life of an Optimizely OMVP: Managing Graph search: the native portal and the community plugin

Optimizely Graph has quietly become the search engine sitting underneath most new Optimizely builds. It ships with CMS 13, it's the answer to "what...

Graham Carr | Jun 9, 2026