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 16, 2010
  6859
(0 votes)

Mark page as changed checked as default

If you check the EPiServer SDK they way to do it is by attaching to the EditPanel loadedpage event i Global.asax.

What if you would like to to it for different pagetypes then? It would be no big thing to add a paget ype check and maybe make it configurable through a section i web.config.

Since I don’t like neither sections in web.config or having lot’s of code in global.asax i decided to try to accomplish this with a custom property.

It turned out to be very straight forward. Just create a custom property with a control class inheriting from PropertyStringControl, and add the below code to CreateEditControls.

Just add the property to the top of the Information tab and you should be good to go.

Note: After having so colleagues trying it out it seems that neither of the two approaches work i CMS5 R2, but both do in CMS5.

   1: #region CreateEditControls
   2:     /// <summary>
   3:     /// Set "PageChangedOnPublished
   4:     /// </summary>
   5:     public override void CreateEditControls()
   6:     {
   7:         PageData pd = ((PageBase)this.Page).CurrentPage;
   8:  
   9:         if (pd.Property["PageChangedOnPublish"] != null)
  10:             pd.Property["PageChangedOnPublish"].Value = "True";
  11:  
  12:     }
  13:     #endregion

 

Global.asax code:

   1: public class Global : EPiServer.Global
   2: {
   3:     protected void Application_Start(Object sender, EventArgs e)
   4:     {
   5:         EditPanel.LoadedPage += new LoadedPageEventHandler(EditPanel_LoadedPage);
   6:     }
   7:  
   8:     protected void EditPanel_LoadedPage(EditPanel sender, LoadedPageEventArgs e)
   9:     {
  10:         e.Page.PageName += "[Test]";
  11:         e.Page["PageChangedOnPublish"] = true;
  12:     }
  13: }
Jun 16, 2010

Comments

Falted
Falted Sep 21, 2010 10:33 AM

Have you tried this approach in CMS 6?

Per Nergård (MVP)
Per Nergård (MVP) Sep 21, 2010 10:33 AM

Yes I tagged it with CMS 6 so i should have done it in cms 6.

mpagi.kironde@rufusleonard.com
mpagi.kironde@rufusleonard.com Sep 11, 2012 05:58 PM

HI Per,

I tried your solution in version 5.2.375.236, but no luck. Its driving me up the wall, Any ideas how to get it workin in 5.2

thanks

Per Nergård (MVP)
Per Nergård (MVP) Apr 4, 2013 05:33 PM

Sorry that I haven't answered. There is some problem because I don't get any mails when people comment altough I have it in the settings.

I think this is a known limitation that it doesn't work in CMS5.

Marcus Andersson
Marcus Andersson Jun 18, 2013 11:02 AM

Exactly what I was looking for!
Thanks.

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 |