Per Nergård (MVP)
+1
Jun 26, 2013
visibility 6278
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
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |