A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Per Nergård (MVP)
Jun 26, 2013
  5957
(0 votes)

Small change in CMS 7 archiving functionality

At least since EPiServer 4 the page archiving functionality have been the same. You setup the archiving scheduled job and after that it’s up to the editors to set a date for when the page should stop being published and where the page should be archived to.

A nice feature in CMS 4 – 6 was that if you specified the archive page link on a top node i.e. a news container page, all news pages created below that container node would automatically get the containers archiving page set.

Last week I was setting up the example above in CMS7 but realized that the automatic inheritance of the archive page doesn’t exist in CMS 7.1.

In order for the editors to set the stop publish date and archive page they need to go to the forms view, choose tools and select the appropriate menu option just to get to the dialog! I really can’t make any sense of that design decision. It was much easier in the previous versions if you ask me.

Ok so how do we simplify this for the editors. In CMS7 we have the possibility to override a method (SetupDefaultValues) for setting up default values for a page type.

So it’s real easy to set up both the “StopPublish” date and the “ArchiveLink” link.

Jun 26, 2013

Comments

Please login to comment.
Latest blogs
ScheduledJob for getting overview of site content usage

In one of my current project which we are going to upgrade from Optimizely 11 I needed to get an overview of the content and which content types we...

Per Nergård (MVP) | Jan 27, 2026

A day in the life of an Optimizely OMVP: Migrating an Optimizely CMS Extension from CMS 12 to CMS 13: A Developer's Guide

With Optimizely CMS 13 now available in preview, extension developers need to understand what changes are required to make their packages compatibl...

Graham Carr | Jan 26, 2026

An “empty” Optimizely CMS 13 (preview) site on .NET 10

Optimizely CMS 13 is currently available as a preview. If you want a clean sandbox on .NET 10, the fastest path today is to scaffold a CMS 12 “empt...

Pär Wissmark | Jan 26, 2026 |

Building AI-Powered Tools with Optimizely Opal - A Step-by-Step Guide

Learn how to build and integrate custom tools with Optimizely Opal using the Opal Tools SDK. This tutorial walks through creating tools, handling...

Michał Mitas | Jan 26, 2026 |