Optimizely - update 396

Fixed an issue where a block name did not show in the Show notification dialog box.

Fixed an issue where, after changing the required ContentReference image property for content, the content was auto-saved but did not publish, and an error displayed.

Fixed an issue that defaulted to No when the default enter key should be Yes when you cut and paste a page, block, or media from one folder to another folder.

Fixed an issue where the wrong name displayed in compare mode for a multi-language block on a multi-language page.

Up until now, on-page editing required sharing the domain between the delivery site and the management site; developers had to ensure that the two sites set the same document.domain.

The new On-Page Edit feature does not require access to the document in the delivery site because the communicationInjector.js script (included in the delivery site) inspects the rendered page and uses postMessage to report back rendered properties and their positions to the management site. This lets the management site show overlays and add editors to the properties.

This release primarily supports server-side-rendered content and the next version will improve upon the support for Single Page Applications where content is rendered on the client.

Fixed an issue where the username was not properly URL-encoded.

Fixed an issue where naming a page property "Constructor" generated an error on the console and the page was not created.

Added support for .NET 6 to CMS UI packages of Optimizely Content Cloud (CMS).

There will be no changes to the .NET 5 support, and the packages will include assemblies built for both .NET 5 and .NET 6.

Sever-side pagination is used in Set Access Rights when searching for users and groups.

Also, the UI was updated for the Add Users/Groups component to support infinite scrolling.

Fixed an issue where the tooltip did not show.

Fixed an issue where after a role was deleted, the selected role was changed but not blank.

The communicationInjector.js and deliveryPropertyRenderer.js scripts are available anonymously to provide an on-page editing experience in a cross-domain scenario, such as a public website located in one place and the management UI located in another. The scripts communicate authentication and authorization between the public and management websites prior to accessing content.

Fixed an issue where a site could not start on environment other than DXP if EPiServer.CloudPlatform.Commerce is installed.

Fixed an issue where Customer menu item highlighting was lost on page refresh.

Fixed an issue where Commerce CSR UI did not correctly display anonymous customer's information.

Fixed an issue where results of entries with no price were not cached.

Fixed an issue where nothing was logged when the tracking configuration was invalid when tracking to Peerius.

Fixed an issue where saving catalog resulted in unnecessary version updates.

Fixed an issue where the ChangeBy field did not update correctly.

Fixed an issue where some product variations showed "0" in the Stock column when browsing catalogs, but displayed positive numbers when in All-Properties View.

Fixed an issue in the Order Management module where data in date and time fields in Subscription details were incorrectly displayed.

Fixed an issue where free gifts were not correctly added to the cart after conditions for promotion were fulfilled.

Ported EPiServer.SwaggerDocs project to .NET Core.

Fixed an issue where metadata did not publish.

When you uploaded an image from file explorer to the page, it was stored as a local asset and inherited the publishing cycle of the page. If you changed the image metadata (such as title or alt text) and published the image, the metadata did not publish

Fixed an issue where the on-page preview of the block was not updated, if you edited a contentArea with blocks where the page/block was already pending a publish (Publish button was available),