World is now on Opti ID! Learn more
World is now on Opti ID! Learn more
Recently, I handled a couple of support cases that revolved around two challenges in a Search & Navigation. Rendering breadcrumbs for search results , and Searching below a specific node and including content and content assets . Neither problem w...
In Find 13, we introduced language routing on indexing to improve indexing performance for indexes setup with multiple languages. With the release of Find 13.4.9, we further introduced language routing on query time. We recommend moving up to 13.5...
Dear partners and developers, Due to issues introduced with this change/release https://world.optimizely.com/documentation/Release-Notes/ReleaseNote/?releaseNoteId=FIND-5191 which impacts both clients and the Find service we are delisting the...
Changing the timeout for Search & Navigation requests is something that has been requested over and over in forums and support cases for quite some time. The default request timeout is set to 100 seconds (HttpWebRequest.Timeout default) which coul...
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...