You said Save method fails, what is the error?

oww yes sorry...  So no error, but i keep getting looped into this EntryUpdating event, which continues and then just breaks the application due to too many loops. 

Reading your code more carefully I think I understand why. EntryUpdating works in a lower level (i.e. when a CatalogEntryDto is saved), and if you call Save, it will internally save the DTO, which again triggers EntryUpdating, resulting in an endless loop.

Instead of CatalogEventListenerBase, you can try using IContentEvents - if you only updates entries via content APIs (for example, by using Catalog UI), and try to use PublishedContent instead of PublisingContent event. The *ed one happens after the data is committed, while *ing happens before. I did not test that so you might want to try it first. 

If I don't take totaly wrong, then something like this should work. This is not tested code and can't guarantee that it works :)

[InitializableModule]
    [ModuleDependency(typeof(EPiServer.Web.InitializationModule))]
    public class ContentEventHandlersInitialization : IInitializableModule
    {
        public void Initialize(InitializationEngine context)
        {
            var events = ServiceLocator.Current.GetInstance<IContentEvents>();
            events.PublishingContent += PublishingContent;
        }

        private void PublishingContent(object sender, ContentEventArgs e)
        {
            TileVariant tileVariant = e.Content as TileVariant;
            if (tileVariant != null)
            {
                if (!tileVariant.ShowCommercialName && !tileVariant.RouteSegment.Equals(tileVariant.ShowroomCode.Slugify(), StringComparison.InvariantCultureIgnoreCase))
                {
                    // we don't need to create a writeableclone as this is the object getting saved 
                    tileVariant.RouteSegment = tileVariant.ShowroomCode.Slugify();
                    // for the same reason, we don't need to call the save method on ContentRepository
                }
            }
        }

        public void Uninitialize(InitializationEngine context)
        {
            var events = ServiceLocator.Current.GetInstance<IContentEvents>();
            events.PublishingContent -= PublishingContent;
        }

        public void Preload(string[] parameters)
        {
        }
    }

Hi Sebastian,

i didnt know that these events were also working for commerce section of episerver. I thought only for CMS. 

So the following problem. WHen i add this initialization module. And i try to publish a normal contentpage i never get into this module. I set my break point in the Initialize method, but never comes there.. 

What am i missing?

I also tried to add 

[ModuleDependency(typeof(InitializableModule))]

instead of your

[ModuleDependency(typeof(EPiServer.Web.InitializationModule))]

I saw someone else use that. I dont know what the difference is but i saw someone else use that, but it doesnt hit my breakpoint either.

If you are using content APIs to update your catalog items, or if you are using the Catalog UI to update them manually, then yes, you can listen to certain events in IContentEvents. If you are using CatalogEntryDto/ICatalogSystem for example, then those are in lower level and will not fire events in IContentEvents.

In Sebastian's code he added a check for TileVariant, make sure your break point is place before that. Also:

• It's recommended to have ModuleDependency on EPiServer.Commerce.Initialization.InitializationModule
• Inside Initializate, use context.Locate.Advanced.GetInstance<T> instead

thanks both of you... the content API works perfectly now...