Breaking changes
Breaking changes for Optimizely Search & Navigation 17
Optimizely Search & Navigation 17 changes the names of indexed fields and the signatures of several interfaces you can implement or extend. Review these breaking changes before you upgrade so that your code compiles and your queries return the results you expect.
Breaking changes for Optimizely Search & Navigation 16
Optimizely Search & Navigation 16 uses the HttpClient library instead of the obsolete HttpWebRequest to send requests to the search service. As a result, Optimizely Search & Navigation extends the public constructors in the client class with a parameter of type IHttpClientFactory .
Breaking changes for Optimizely Search & Navigation 15
Before Optimizely Search & Navigation Client API version 15, you could search for documents with terms beginning with an unknown string, but this is no longer supported. Depending on the use case, you might achieve the same results using different solutions.
Breaking changes for Optimizely Search & Navigation 13
EPiServer. Find.
Breaking changes for Optimizely Search & Navigation 12
EPiServer. Find.
Personalized Search & Navigation 2 breaking changes
Version 2. 0 of Optimizely Personalized Search & Navigation adds support for EPiServer.