Release notes for Optimizely updates

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:

1. Add attribute disableServiceQueue="false" on episerver.find element in web.config (<episerver.find
   serviceUrl="..."
   defaultIndex="..." disableServiceQueue="false"/>
2. Run the indexing job.

Expected result:

All content gets indexed.

Actual result:

Some content is not indexed.

This is an issue where a deadlock occurs in tblFindIndexQueue while running an import job with the Episerver Service API.

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.

When there is a long message for a Job on the page EPiServer Find Content Indexing Job, then the page will fail to load with an error "The page was not displayed because the request entity is too large.".

Fixes an error in Personalized Search & Navigation (formerly Personalized Find) where tracking is not working due to a mix-match in models.

Opt-in functionality to use the new Asynchronous Queues providing higher indexing and tracking throughput.

This fix solves the issue with FileLoadException exceptions and warnings in Visual Studio when upgrading to find 13.3.0.

Problem Description

Upgrading to Find .NET API v. 13.3.0 results in FileLoadException for four different assemblies.

The following warnings can be seen in Visual studio:

Found conflicts between different versions of "System.Web.Http" that could not be resolved.
Found conflicts between different versions of "System.Web.Mvc" that could not be resolved.
Found conflicts between different versions of "System.Web.Http.WebHost" that could not be resolved.
Found conflicts between different versions of "System.Net.Http.Formatting" that could not be resolved.

Steps to reproduce

1. Install the Alloy sample site with the Episerver tools in Visual Studio.
2. Verify that Alloy runs.
3. Update Find to 13.3.0.
4. Note that the site will not run.