Per Nergård
Jun 26, 2013
  5426
(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
Opti ID overview

Opti ID allows you to log in once and switch between Optimizely products using Okta, Entra ID, or a local account. You can also manage all your use...

K Khan | Jul 26, 2024

Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024