Release notes for Optimizely CMS and Customized Commerce updates

Fixed an issue where ContentEventIndexer loaded content with a default content cache expiration time of twelve hours. This caused content to remain in memory for longer than necessary.

Fixed an issue that left content in the page's For this page folder when the associated page was deleted, which led to clutter and potential data inconsistencies; the orphaned content was still searchable.

Fixed an issue where the explorer view filter did not work.

Fixed an issue where DefaultRequestHeaders were set when the request was made. This could lead to race condition during startup

Fixed the following authorization issue: The UI (dojo script) sent a header "Authorization" (Bearer token) to Bestbets, Editorial, and ServiceHealth controllers but those controllers only accepted Windows Authentication (which would send a WWW-Authenticate header).

Fixed an issue that may cause deadlock when the Optimizely Search & Navigation client API sent an HTTP request using the HttpClient library because the calling method waited for a response and the result was resumed on the context thread. 

Fixed an issue where settings were initiated in the client with incorrect values.

Fixed errors that occurred when you tried to add and save visitor group membership criterion after you upgraded to Optimizely Content Management System (CMS 12), (suspected to be related to an upgrade of the EPiServer.Find.Cms package from version 14.2.4 to 15.2.0). Additionally, unified search functionality was compromised so that only pages without visitor group configurations appeared in search results (unless the user was an administrator).

Steps to reproduce:

1. Upgrade CMS to version 12 and EPiServer.Find.Cms package to version 15.2.0.
2. Create a visitor group that has another visitor group as a member.
3. Attempt to add a new membership criterion to this nested visitor group and save.
4. Perform a unified search for pages. Only pages without visitor group configurations appear, (unless logged in as an administrator).

Fixed an issue where synonyms displayed a "not available" after a recent upgrade.

Fixed an issue in the indexing job that sometimes failed with an error such as

An exception occurred while fetching content.
Cannot create a command without an existing connection
or Invalid operation. The connection is closed.