Optimizely - update 443

Fixed an issue that caused a failure to upgrade to 12.3.0 because SPs netSoftLinksGetBroken and SoftLinksGetBrokenCount was missing due to missing dbo schema in update script.

Fixed a cache memory leak.

When an item is inserted with a cache dependency, an entry is added to the cache dependency map, but it does not check if the same entry is already there, which opens the possibility of having duplicates added and uses memory unnecessarily.

Multiple duplicates were observed in a memory dump from a customer site. It might have been triggered because the Optimizely Search & Navigation indexer loaded the same blocks over and over again in steps of the indexing.

Fixed a cache memory leak.

The cache stores a mapping of cache dependencies separate from the cache itself. Cache dependencies are cleaned up when items are removed or expired, but left behind when the cache is compacted due to memory pressure. In sites that have much more content than can fit in the cache, over time orphaned dependencies can come to dominate the cache itself, effectively causing a memory leak.

Fixed EPiServer.Commerce.FindSearchProvider to support Find 15.

Updated package dependency range to Episerver.Find 15.

Fixed an issue that transformed a placeholder character (#) from a paragraph to a heading1 when you inserted a RichText placeholder, then pressed Enter.

Introduced an app setting called HidePartialSubmissions that filters partial submissions from any external interface such as UI, exports, and actors. Combined with retention policies, this addresses the potential problem where multi-step forms may contain personally identifiable information (PII) but typically don't have customer consent since that's usually given at the end.

Fixed an issue where the Create new element button did not display when you edited a form by Quick Edit.

Fixed an issue that overwrote a previous submission if you enabled HidePartialSubmissions, when new data should be added to the data table.

When you enabled DisableFormCookies and disallowed anonymous submission, a visitor could not submit the form, but you were not notified about this. The issue was addressed by notifying the form editor when these conditions exist where a visitor cannot submit a form.

Fixed an issue where the Drop Content Here option was missing - when you clicked Add Link in the Display page after submission section - if your personal language was set to Swedish, Danish, or German.

When addressing the issue in CMS-23405, a breaking change was introduced in how the values for string properties using SelectManyAttribute and ISelectionFactory are stored in the database. A change was made to serialize the selected options as JSON instead of comma separated strings. This change was reverted back to the original format. Make sure to verify that any values stored for properties using SelectManyAttribute are correct. Rechecking them in the UI and saving will save in the correct comma-separated format. Items saved in the JSON format introduced by 12.17.0 will not be selected correctly in the UI, so any updated properties needs to be verified.