This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project; see Installing Optimizely updates (CMS 11 and Commerce 13).
To upgrade to Content Cloud (CMS 12), see Upgrading to Content Cloud.
Select a product, package, or service in the left menu, and then select one of the following filters from Item type and click Filter.
Note: NuGet packages listed here may not be immediately available in the Optimizely NuGet feed.
Fixed an issue that caused a 500 error on an _msearch call while attempting to view search statistics for a specific query. Track ID was supposed to contain [content_type]/[id].
Fixed an issue where adding best bets sent one config request for every existing best bet.
If you have many bests bets it can make adding/editing best bets in the Find UI result in a timeout.
Fixed an issue where the content indexer had a collection of exceptions (called _indexingExceptions), which could cause a memory leak.
Fixed an issue where adding ServiceApi to the project caused the unified search to stop working. (If you removed the ServiceApi nugget, it would work again because of a lack of user and roles in the first request.)
Fixed an issue where sometimes visitors got duplicate hits when paginating, which happened only for non-ordered constant score queries because different shards were answering the same query.
[Netcore] A NullReferenceException exception occurred when adding MapControllerRoute, when the search result should have been returned.
Logging of errors was enhanced to be more informative.
When a culture was set in web.config, the indexing job should have updated the SearchTypeName. For example, setting the culture to Swedish (sv-SE), SearchTypeName should have updated to Sida but was listed incorrectly as Page.
Find clients on version 13.4.0 - 13.4.4 configured to use an index hosted on a Find v1 or v2 cluster incorrectly disables Invisible Mode. This disables the indexing queue which is responsible for
1. Processing updates in parallel to the save/publish thread
2. Push updates in batches
The impact is slow save/publishing in the edit UI as updates to Find are sent in the same thread and not in batches.
It would also affect import jobs that trigger content updates.
You will likely see more bulk requests to Find than you usual.
Only Find indexes on Find V1 and V2 clusters are affected. They have a service url that starts with
https://us-, https://ap- , https://se-, https://eu- , htttps://az- or https://es-
It will not affect the Find indexing job as it doesn't use the queue.
If you're not able to upgrade right away explicitly setting Invisible to True in an init module works as well
ContentIndexer.Instance.Invisible = true;
TrackQueryCommand.Execute caused unnecessary LOH Heap Allocations