dada
Optimizely
Oct 13, 2020
visibility 8332
star star star star star
(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.

error Please login to comment.
Latest blogs
Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026

Opal Workflow Agents And The Graph Webhook Trap

What we did? We built a compliance review workflow agent in Opal. The job was simple: when an editor submits a page for review in Optimizely CMS 13...

Ritu Madan | Oct 14, 2026