Per Nergård (MVP)
+2
Jun 26, 2013
visibility 6457
star star star star star
(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

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |