KennyG
Dec 18, 2017
  2846
(1 votes)

Comparing draft content to published content

We had a situation arise the other day where we needed to compare some values in a draft page against the currently published version. Based on some fields changing we knew we needed to reindex a list of related pages.

This all takes place in the IContentEvents PublishingContent event handler which has been wired up in an InitializationModule.

The trick here is to cast e.Content to get the current draft and to use e.ContentLink.ToReferenceWithoutVersion to get the published version so that you can compare.

Here is a code sample that checks for a change to the Name and logs it.


using System;
using System.Linq;
using EPiServer;
using EPiServer.Core;
using EPiServer.Framework;
using EPiServer.Framework.Initialization;
using EPiServer.ServiceLocation;
using EPiServer.Logging;


[InitializableModule]
[ModuleDependency(typeof(EPiServer.Web.InitializationModule))]
public class PageDataUpdatedInitialization : IInitializableModule
{
    private static readonly ILogger Logger = LogManager.GetLogger();
    private Injected contentLoader;


    public void Initialize(InitializationEngine context)
    {
        var events = context.Locate.ContentEvents();
        events.PublishingContent += this.PublishingContent;
    }

    private void PublishingContent(object sender, ContentEventArgs e)
    {
        var newPageData = e.Content as PageData;
        if (newPageData == null)
            return;

        var oldPageData = contentLoader.Service?.Get(e.ContentLink.ToReferenceWithoutVersion());
        if (oldPageData == null)
            return;

        // check to see whether any updates were made to the specific value
        if (!ValueChanged(oldPageData, newPageData))
            return;

        // if so, do something
        Logger.Debug("Value has changed from {0} to {1}", oldPageData.Name, newPageData.Name);
    }

    private static bool ValueChanged(PageData oldPageData, PageData newPageData)
    {
        var oldName = oldPageData.Name;
        var newName = newPageData.Name;

        if (newName != oldName)
        {
            return true;
        }

        return false;
    }

    public void Uninitialize(InitializationEngine context)
    {
        //Add uninitialization logic
    }
}

Dec 18, 2017

Comments

valdis
valdis Dec 18, 2017 06:32 PM

just a couple of my humble cents here:

  • I would not do all the logic in initialization module. these are meant to just initialize things. rest of the logic I would move to separate service
  • there I would require IContentLoader from constructor (btw, you are missing T part of the Injected field data type) - therefore I would be required to pass it in from init module somehow
  • and also in the same way - I could require IContentEvents implementation to be supplied.
  • not a big deal - but avoids you to use anti-patterns, such as ServiceLocator.

Also I would encourage you to take a look at brilliant way to handle Episerver events differently - http://marisks.net/2017/02/12/better-event-handling-in-episerver/

KennyG
KennyG Dec 18, 2017 08:24 PM

Thanks for the feedback Valdis! 

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