Try our conversational search powered by Generative AI!

dada
Oct 13, 2020
  6896
(3 votes)

How to make Find 13.x play nice with Find on-premise

If you are using Find (Search & Navigation) 13.x or later with an index located on a Find on-premise instance you need to do the following to achieve full compatibility. 
This is not applicable to any solution where you're using an index hosted by EPiServer.

1. If you are on 13.0.5 or later you need to make sure you upgrade to at least 13.2.4 and add useLegacySorting=true to your episerver.find config element to be
    able to use the Elastic Search sorting functionality to it's full extent.

<episerver.find serviceurl="..." useLegacySorting="true" ... >

2. With Find 13 language routing was introduced. This is not available on Find on-premise therefor you should disable it.
    Disable Language Routing support via LanguageRoutingFactory. 

   [InitializableModule]
   [ModuleDependency(typeof(IndexingModule))]
   public class MyFindInitializationModule : IConfigurableModule
   {
       public void Initialize(InitializationEngine context)
       {
       }
       public void Uninitialize(InitializationEngine context)
       {
       }
       public void ConfigureContainer(ServiceConfigurationContext context)
       {
           context.Services.AddSingleton<LanguageRoutingFactory, MyLanguageRoutingFactory>();
       }
       }

   public class MyLanguageRoutingFactory : LanguageRoutingFactory
   {
       public override LanguageRouting CreateLanguageRouting(ILocale locale)
       {
           return null;
       }
   }
   }

Oct 13, 2020

Comments

Tomas Hensrud Gulla
Tomas Hensrud Gulla Oct 13, 2020 12:22 PM

Nice update, but this should be added to the documentation, if not already in place. I can see it mentioned in the release notes (added after the release): 
https://world.episerver.com/documentation/Release-Notes/ReleaseNote/?releaseNoteId=FIND-5988

I had to figure it out the hard way...
https://www.gulla.net/no/blog/undocumented-breaking-change-in-episerver.find-13.2.0-affecting-on-premise-find-installations/

dada
dada Oct 13, 2020 12:41 PM

Hi @Tomas, You are correct and I have relayed this information to the documentation team at the same time as I wrote the blog post.

Please login to comment.
Latest blogs
Why C# Developers Should Embrace Node.js

Explore why C# developers should embrace Node.js especially with Optimizely's SaaS CMS on the horizon. Understand the shift towards agile web...

Andy Blyth | May 2, 2024 | Syndicated blog

Is Optimizely CMS PaaS the Preferred Choice?

As always, it depends. With it's comprehensive and proven support for complex business needs across various deployment scenarios, it fits very well...

Andy Blyth | May 2, 2024 | Syndicated blog

Adding market segment for Customized Commerce 14

Since v.14 of commerce, the old solution  for adding market segment to the url is not working anymore due to techinal changes of .NET Core. There i...

Oskar Zetterberg | May 2, 2024

Blazor components in Optimizely CMS admin/edit interface

Lab: Integrating Blazor Components into Various Aspects of Optimizely CMS admin/edit interface

Ove Lartelius | May 2, 2024 | Syndicated blog