dada
Oct 13, 2020
  7992
(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
Searchable settings page

In my current project which has been actively developed for quite some time we have a big classig settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |

Stott Robots Handler v7 for Optimizely CMS 13

Stott Robots Handler version 7 is now available for  Optimizely PaaS CMS 13 . This is includes updates to support the switch from a Site based...

Mark Stott | Apr 2, 2026

Automating Block Translations in Optimizely

Stop manual block-by-block translations. Learn how to use the TranslateOrCopyContentAreaChildrenBlockForTypes config to automate Optimizely CMS...

Stuart | Apr 1, 2026 |