Replace SEO URL generation in EPiServer Commerce 7.5
EPiServer Commerce 7.5 offers two different approaches for routing to catalog content: The hierarchical route using the Name in URL property of the ancestor contents, and the SEO URL which has been fused with the Simple address system you know from EPiServer CMS. So the former will be on the format /catalog/category/subcategory/product and the latter a single URL segment. Which one is used when rendering links depends on how you register the catalog routes, see the routing article in the Commerce SDK / Developer Guide for more information.
By default the SEO URL is generated from the name of the content, with the “file extension” .aspx appended. To make the URLs unique per language branch, the language name may also be appended, to generate something like Red-Striped-Shirt-en.aspx.
Generating your own SEO URLs
The SEO URL generation is handled by the Mediachase.Commerce.Catalog.Data.UniqueValueGenerator class. You can override the generating bit in your own class:
1: using System;
2: using Mediachase.Commerce.Catalog;
3: using Mediachase.Commerce.Catalog.Data;
4: using Mediachase.Commerce.Shared;
5: using System.Globalization;
6:
7: namespace EPiServer.Commerce.SampleMvc.Business
8: {
9: public class ExtensionlessUniqueValueGenerator : UniqueValueGenerator
10: {
11: public ExtensionlessUniqueValueGenerator(ICatalogSystem catalogContext)
12: : base(catalogContext)
13: {
14: }
15:
16: protected override string SuggestSeoUri(string name, string languageCode, int index, string duplicateUrl)
17: {
18: var slug = CommerceHelper.CleanUrlField(name);
19: if (String.IsNullOrEmpty(duplicateUrl))
20: {
21: return slug;
22: }
23: return slug + "-" + index.ToString(CultureInfo.InvariantCulture);
24: }
25: }
26: }
The overridden SuggestSeoUri method will be called repeatedly until it generates a unique value. The index parameter is incremented by one for each call, and the duplicateUri parameter is set to the value which was checked in the previous pass (it will be null in the first call). As you can see I completely ignore the languageCode parameter, which means two language versions may vary only by a number in the URLs (product-name-1 and product-name-2).
To make use of your implementation you need an initialization module to replace the configuration in the container:
1: using EPiServer.Framework;
2: using EPiServer.Framework.Initialization;
3: using EPiServer.ServiceLocation;
4: using EPiServer.Commerce.SampleMvc.Business;
5: using Mediachase.Commerce.Catalog.Data;
6:
7: namespace EPiServer.Commerce.SampleMvc
8: {
9: [ModuleDependency(typeof(EPiServer.Commerce.Initialization.InitializationModule))]
10: public class Initialization : IConfigurableModule
11: {
12: public void Initialize(InitializationEngine context)
13: {
14: }
15:
16: public void Preload(string[] parameters)
17: {
18: }
19:
20: public void Uninitialize(InitializationEngine context)
21: {
22: }
23:
24: public void ConfigureContainer(ServiceConfigurationContext context)
25: {
26: context.Container.Configure(c => c.For<UniqueValueGenerator>().Use<ExtensionlessUniqueValueGenerator>());
27: }
28: }
29: }
Comments