Overwriting the default LifecycleDecorator for a Content manager

Title

URL Name

Overwriting-the-default-LifecycleDecorator-for-a-Content-manager

Article Number

000186599

Environment

Product: Sitefinity Version: 4.x, 5.x, 6.x, 7.x, 8.x OS: All supported OS versions Database: Microsoft SQL Server 2012 SP2

Question/Problem Description

How to execute a custom logic when a new Content item (like NewsItem or DynamicContent) is published.

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Need to execute additional logic on content item publishing. Need to extend the publishing logic.

Resolution

This can be accomplished by changing the default LifecycleDecorator for the appropriate Content manager.

The lifecycle of Content items and Pages is handled by a LifecycleDecorator. It handles all lifecycle operations like CheckIn, CheckOut, Publish, etc.

The example bellow, shows how to override a LifecycleDecorator and use to modify the publishing for NewsItem.

using System;

using Telerik.Sitefinity.GenericContent.Model;

using Telerik.Sitefinity.Lifecycle;

using Telerik.Sitefinity.News.Model;

namespace SitefinityWebApp.LifecycleDecorators

{

public class NewsItemLifecycleDecorator : LifecycleDecorator

{

public NewsItemLifecycleDecorator(ILifecycleManager manager,

LifecycleItemCopyDelegate copyDelegate, params Type[] itemTypes)

: base(manager, copyDelegate, itemTypes)

{

}

// Use to support the ContentManagerBase<Provider>, IContentLifecycleManager<ILifecycleDataItem> implementation.

public NewsItemLifecycleDecorator(ILifecycleManager manager, Action<Content, Content> copyDelegate, params Type[] itemTypes)

: base(manager, copyDelegate, itemTypes)

{

}

protected override

ILifecycleDataItemGeneric ExecuteOnPublish(ILifecycleDataItemGeneric masterItem, ILifecycleDataItemGeneric liveItem, System.Globalization.CultureInfo culture =

null, DateTime? publicationDate = null)

{

// The master item to be published. It contains the changes for publication.

NewsItem newsItem = masterItem as NewsItem;

// The live item - the last published item. It does not contain the changes to be published.

NewsItem liveNewsItem = liveItem as NewsItem;

// The published item. The returned item has status Live.

ILifecycleDataItemGeneric baseResult = base.ExecuteOnPublish(masterItem, liveItem, culture, publicationDate);

return baseResult;

}

In order to register the LifecycleDecorator to be used for NewsItems publishing, register it using the Object factory, specifying the item's manager - in this case the NewsManager:

public class Global : System.Web.HttpApplication

{

protected void Application_Start(object sender, EventArgs e)

{

Bootstrapper.Initialized += new EventHandler<ExecutedEventArgs>(Bootstrapper_Initialized);

}

protected void Bootstrapper_Initialized(object sender, ExecutedEventArgs e)

{

if (e.CommandName == "Bootstrapped")

{

ObjectFactory.Container.RegisterType<ILifecycleDecorator, LifecycleDecorators.NewsItemLifecycleDecorator>

(typeof(NewsManager).FullName,

new InjectionConstructor(

new InjectionParameter<ILifecycleManager>(null),

new InjectionParameter<Action<Content, Content>>(null),

new InjectionParameter<Type[]>(null))

);

}

Change the manager type if the LifecycleDecorator has to be replaced for different content type, for instance, Events.

Replacing the LifecycleDecorator is also possible for DynamicContent items. However, replacing the decorator, overrides the one used for all DynamicContent items - disregarding module type.

The different additional logic depending on the item type can be done as in the bellow example:

using System;

using Telerik.Sitefinity.DynamicModules.Model;

using Telerik.Sitefinity.Lifecycle;

namespace SitefinityWebApp.LifecycleDecorators

{

public class DynamicContentLifecycleDecorator : LifecycleDecorator

{

public DynamicContentLifecycleDecorator(ILifecycleManager manager, LifecycleItemCopyDelegate copyDelegate, params Type[] itemTypes)

: base(manager, copyDelegate, itemTypes)

{

}

protected override

ILifecycleDataItemGeneric ExecuteOnPublish(ILifecycleDataItemGeneric masterItem, ILifecycleDataItemGeneric liveItem, System.Globalization.CultureInfo culture =

null, DateTime? publicationDate = null)

{

if (masterItem.GetType().ToString() == DynamicContentLifecycleDecorator.pressReleasesTypeName)

{

// The master item to be published. It contains the changes for publication.

DynamicContent item = masterItem as DynamicContent;

// Add logic for on publish of Press releases

}

// The published item. The returned item has status Live.

ILifecycleDataItemGeneric baseResult = base.ExecuteOnPublish(masterItem, liveItem, culture, publicationDate);

return baseResult;

}

protected static readonly string pressReleasesTypeName = "Telerik.Sitefinity.DynamicTypes.Model.Pressreleases.PressRelease";

}

Registration:

ObjectFactory.Container.RegisterType<ILifecycleDecorator, LifecycleDecorators.DynamicContentLifecycleDecorator>

(typeof(DynamicModuleManager).FullName,

new InjectionConstructor(

new InjectionParameter<ILifecycleManager>(null),

new InjectionParameter<LifecycleItemCopyDelegate>(null),

new InjectionParameter<Type[]>(null)

)

);

The above examples are also attached to the article.

Workaround

Notes

Keyword Phrase

Last Modified Date

7/20/2016 2:15 PM

Overwriting the default LifecycleDecorator for a Content manager

Files(1)

Was this article helpful?

Was this article helpful?

Overwriting the default LifecycleDecorator for a Content manager

Information

Related Articles