Release notes for Optimizely CMS and Customized Commerce updates

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 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 if you changed weights in the Search & Navigation UI (Configure > Boosting), the changes were not reflected on the site before the site was restarted because the cache for UnifiedWeightsResult in UnifiedWeightsCommand was not invalidated correctly.

Fixed an issue where the dojo language file was missing.

Episerver Find JavaScript can use hashes that align with current security practices.

Fixed an issue where you could not select target content after searching when creating/editing Best Bets.

Fixed an issue where search pages created scripts with incorrect defer values using find.js.

Expected:

Actual:

Indexing large content structures sometimes failed with a SQL timeout. This fix optimizes how the indexer compiles the list of content items to index to avoid the large SQL call that can time out.

Fixed an issue where using a Chinese, Japanese, or Korean (CJK) analyzer/language in an index resulted in an empty language dropdown in the Find user interface.