Follow bloggers on Optimizely World to get the latest from people who know all about the Optimizely platform! You will find blog posts from the entire Optimizely community, as well as from the Optimizely development teams.
Start blogging - create your own blog (requires log in)
Manage your blog posts on Optimizely World (requires log in)
Rules for blogging on Optimizely World
From Episerver.Find version 16.1.0, we introduced some new features that make the indexing job in CMS more flexible and efficient: Support continuous indexing job. In case the job has been crashed, you can restart and it will continue indexing...
From version 16.1.0 there are some updates on the statistics pages: Add pagination to search phrase list Allows choosing a custom date range to get statistics Allows downloading raw data in csv format I hope that with these updates we can work mor...
We're excited to unveil the latest addition to the Search & Navigation suite: a dashboard designed to proactively monitor your resource usage. It's a powerful tool that offers immediate insights, helping you prevent potential issues before they...
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...
Over the last couple of years, we have been hard at work upgrading the architecture and backend that power Search & Navigation (formerly known as FIND). The most recent development efforts have been on stabilizing the backend we refer to as “V3”,...
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...