London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

dada
Oct 13, 2020
  7268
(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
Routing to a page in SaaS CMS

More early findings from using a SaaS CMS instance; setting up Graph queries that works for both visitor pageviews and editor previews.

Johan Kronberg | Apr 14, 2025 |

Developer Meetup - London, 24th April 2025

Next Thursday, 24th April will be Candyspace 's first Optimizely Developer Meetup, and the first one held in London this year! We've have some...

Gavin_M | Apr 14, 2025

Successful Digitalization for SMEs: How Optimizely One can Revolutionize Your Business Processes

"Achieve digital excellence with Optimizely One: Boost efficiency, delight customers, secure growth." In today's digital world, it's crucial for...

Frank Hohmeyer | Apr 11, 2025

Personalized Optimizely CMS Website Search Experiences Azure AI Search & Personalizer

In the last blog, we discussed Integrating the Optimizely CMS website with Azure AI search. Now let’s take a bit more advanced topic to serve...

Naveed Ul-Haq | Apr 10, 2025 |