This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project; see Installing Optimizely updates.
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.
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 processes updates in parallel to the save/publish thread. It also sends updates in batches.
The impact is slow save and publishing in the edit UI. It would also affect import jobs that trigger content updates. You will likely see more bulk/index requests to Find than you usually would.
Find V1 and V2 clusters 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
Contract resolver was not reused in some places, which caused performance issues.
Best bets title and description was not auto-populated for Commerce content.
Cache in BestBetRepository is not working. This is caused by the CacheEvictionPolicy using the overload for cacheKeys, which is not correct. Instead, the masterKeys should be used.
This is an issue where during an indexing job, the number of documents increases as expected on the Overview page. But when the job finishes, the number of indexed documents are significally reduced again.
Issue where exceptions 'Can't find variable: FindApi at global code' and 'FindApi is not defined at <no_method>' are displayed.
The FindApi() function should not be executed from find.js, if it could not be loaded in the browser.
See this forum post for more details and solution.
Issue where Delete By Query is not working as expected when using service queue.
Steps to reproduce:
All content gets indexed.
Some content is not indexed.
With this fix, the message 'IAttachmentHelper can not be initiated' is logged as INFO instead of ERROR.
IAttachmentHelper is an optional module and is not required, so the message type in logs if the module does not load should not be ERROR.
This is an issue where a deadlock occurs in tblFindIndexQueue which can occur while running any import job that would trigger save/publish events