Manoj Kumawat
+4
Mar 8, 2022
visibility 2685
star star star star star star
(1 votes)

Prevent content events from the loop

I'm writing a simpler solution to the problem that most of us keep getting while working with ContentEvents. There might be solution to this already but at least I couldn't find it easily. 

I was working on content events where on PublishedContent I had to refer products under the category. Now this needs ContentEvents

_contentEvents.PublishedContent += ContentEvents_PublishedContent;

private static void ContentEvents_PublishedContent(object sender, ContentEventArgs e)
{
    SaveDynamicCategory(e.Content);
}

The method above SaveDynamicCategory has a save method as below - 

ContentRepository.Save(content, SaveAction.Publish, AccessLevel.NoAccess);

This works perfectly but the problem that comes with it that it keeps on calling PublishedContent deligate. Therfore the solution is to use piped SaveAction along with SkipValidation as below - 

ContentRepository.Save(content, SaveAction.Publish | SaveAction.SkipValidation, AccessLevel.NoAccess);

And if publish method check this enum containing SkipValidation - if true then stop the loop and return it - 

private static void ContentEvents_PublishedContent(object sender, ContentEventArgs e)
{
   if (e is SaveContentEventArgs saveContentEventArgs && saveContentEventArgs.Action.HasFlag(SaveAction.SkipValidation))
    {
        return;
    }
    SaveDynamicCategory(e.Content);
}

Hope it helps. Thank you for your time.

Mar 08, 2022

Comments

Jake Jones
Jake Jones Mar 8, 2022 11:05 AM

Hi Manoj,

Thanks for sharing.

Why not just use PublishingContent? It occurs when content is requested to be published, so before the actual publish event, meaning you could modify the content before publishing and wouldn't need to re-publish it yourself.

If you do need to publish twice, would you be better off just checking the dynamic category value you're setting? The risk with your approach is that the SkipValidation flag now has a potentially unexpected consequence, which may be an issue if you end up using in elsewhere in the solution.

Anyway, just my thoughts 😉

Manoj Kumawat
Manoj Kumawat Mar 8, 2022 11:12 AM

Hello Jake, I expected that coming 😉 and thank you for pointing that out.

I had the bad example to share but this is not about publishing/published events. It is just about how you can use SaveContentEventArgs while you are stuck in loop at any event. I would like to correct that in blog too.

error Please login to comment.
Latest blogs
From SDK to Core: Modernizing Optimizely Configured Commerce for .NET 8 and .NET 10

The .NET Framework 4.8 clock is running out for Configured Commerce customizations. Handled well, this deadline is not a chore it is the cleanest...

Vaibhav | Jul 29, 2026

Parallel Development in Optimizely CMS SaaS: Shifting to a Schema Migration Mindset

  Part 3 of the Parallel Development series. The branch-scoped push script from Part 1 works. Run it on a feature branch where you've touched a...

Vipin Banka | Jul 25, 2026

From AI Agents to AI Workflow with Opal

Introduction In the first article in this series , we talked about AI agents in Optimizely Opal and walked through the process of creating a...

Igor Safonov | Jul 23, 2026

Building Your First Optimizely Opal AI Agent: a Hands-On Walkthrough

Introduction There's a common assumption that building an AI agent is something only engineers or developers can do. It isn't. At the Optimizely AN...

Igor Safonov | Jul 23, 2026