Optimizely - update 439

CMS Core 12.12.1 had a high-priority patch, so CMS released a patched version of CMS UI with an updated dependency.

CMS Core 12.12.1 had a high-priority patch, so CMS released a patched version of CMS UI with an updated dependency.

Fixed an issue on a site where Episerver.Marketing.Automation.Forms package was installed: if you tried to fetch the form field values for auto-fill when a custom data source was used to map form fields, an error occurred.

Prefix wildcards are an anti-pattern, which can cause issues on production clusters, so now prefix-wildcard queries are rejected if you are using Optimizely Search & Navigation version 16.0 or later.

This is a breaking change. See Breaking changes for Optimizely Search & Navigation 15 for alternate solutions.

Fixed an issue where the Create new element button was removed from ContentArea of a Form.

Fixed an issue that lost the recorded data of a submission when other data was submitted. For example, assume you created a form with elements in English, and translated the form to Swedish. If the English form was submitted, the data was recorded, but if you then submitted the Swedish form, the Swedish data was recorded but the previous form submission data (from the English form) was then lost.

Fixed an issue where the export tool could not export data from installations that contained references to assets in the Optimizely Content Marketing Platform (CMP) DAM.

Fixed an issue that did not update the changes to a version string of element views.

Fixed an issue in the Quick Editor where you could not see a placeholder of RichText element.

Fixed an issue with Forms created with the Norsk (no) language that caused data to not be recorded from the form.

Fixed an issue where you could not create an element because the New Form element screen was behind the Quick Edit popup so you could not input data.

Fixed an issue that caused System.Data.DataException for netPageDynamicBlockDelete when you upgraded the database to 12.10.10. The reason was the baseline of the CMS database script missed qualifying the dbo behind netPageDynamicBlockDelete.

Fixed an issue that caused an ArgumentOutOfRangeException during lazy loading of properties. If the length of property value exceeded contentOptions::PropertyLazyLoadThreshold then it caused a ArgumentOutOfRangeException.