Manoj Kumawat
Mar 8, 2022
  1732
(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.

Please login to comment.
Latest blogs
Custom form element view in Optimizely CMS 12

Do you want full control over the form element markup? Create your own views!

Tomas Hensrud Gulla | Dec 11, 2024 | Syndicated blog

How to Elevate Your Experimentation - Opticon workshop experience

As a non-expert in the field of experimentation, Iā€™d like to share my feedback on the recent Opticon San Antonio workshop session titled "How to...

David Ortiz | Dec 11, 2024

Persisting a Strawberry Shake GraphQL Client for Optimizely's Content Graph

A recent CMS project used Strawberry Shake to generate an up-to-date C# GraphQL client at each build. But what happens to the build if the GraphQL...

Nicholas Sideras | Dec 11, 2024 | Syndicated blog

Opti ID with Secure Cookies And Third Party AddOns

Opti ID has revolutionised access to the Optimizely One suite and is now the preferred authentication method on all PAAS CMS websites that I build....

Mark Stott | Dec 9, 2024