Opticon Stockholm is on Tuesday September 10th, hope to see you there!

smithsson68@gmail.com
Mar 4, 2011
  7465
(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..?

Atul Kumar
Atul Kumar 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
Handling Nynorsk and Bokmål in Optimizely CMS

Warning: Blog post about Norwegian language handling (but might be applicable to other languages and/or use cases). Optimizely have flexible and...

Haakon Peder Haugsten | Sep 5, 2024

Remove Unwanted properties for Headless Implementation using Content Delivery API

While working with Headless, whenever we want to send data to the front end, many properties are also shown in JSON that we don't wish to, which...

PuneetGarg | Sep 4, 2024

Optimizely Headless Form Setup

1. Create empty CMS applications First, let’s setup an empty CMS application. Install the NuGet packages in your solution using the NuGet Package...

Linh Hoang | Sep 4, 2024

Default caching on search request on Search & Navigation

For the better performance, Search & Navigation .Net client has provided StaticallyCacheFor method for caching your search result in a specific of...

Manh Nguyen | Sep 4, 2024