Optimizely - update 436

Fixed issues introduced with bugfix https://world.optimizely.com/support/bug-list/bug/FIND-5191

This change was intended to address an issue with child content not being updated when the URL segment of the parent content was changed. However, it did not achieve the desired result and can sometimes be very resource-intensive.

To address this, the following changes were implemented:

• Child content is now only indexed when the URL segment changes, rather than on all updates.
• Child content is added to the indexing queue to prevent freezing of the queue processing.

Fixed an issue where EPiServer.Find.Cms 14.2.x should have depended on 6.0.1 and not 6.0.0.

Fixed an issue where find.js hurt the Google pagespeed score because it blocked page loading. A defer attribute was added to the script tag so it can be downloaded in parallel to the HTML. 

Note – This was done only for Find API v14.x because the ability to add attributes in the ClientResource class was added in CMS 12.1. (See CMS-18710)

Fixed an issue where Personalized Find did not work when session was disabled.

Fixed an issue where a 404 error occurred when you clicked the On-page Editing option in a form.

Fixed an issue where the session state did not save the GUID identity because the track event of VisitorGroup was running.

Fixed an issue that failed to add a Google Analytics tracking account when you configured OIDC with Azure AD.

Fixed an issue that should have informed you to sign in if your Google account was signed out or unauthorized.

Updated the company name to Optimizely.

Fixed an issue where the Form Submission option did not display to switch to Form Submission mode.

Fixed an issue with Google analytics on the Configure Analytics Gadget tab that did not show the Everyone group among the list of user groups.

Fixed an issue where properties were not copied over when creating SerialzblePayment from custom payment class.

Improved error logging in the case where the response uses the "failure" status code without providing any detailed server-side error(s). 

Fixed an issue that caused an error if you tried to import a duplicate catalog; you could not insert duplicate node entry relations.

Fixed an issue where the Drag/Drop function would not work in Catalog\Asset when the Commerce site is integrated with the latest CMS (Core 12.8.0, UI 12.9.0).

Fixed an issue where a warning message would not display when removing a block being used on a page.

As part of a bugfix, version 14.6.0 introduced a change to the payment creation logic. This change has been shown to have side effects. 14.9.0 reverts the payment creation logic to its pre 14.6.0 state and fixes the original bug in a different way. 

Fixed an issue where customer organizations would only display on the first page when adding child organizations.

Fixed an issue where not all customer organizations would display when editing a Parent organization.

Added the Bolt payment provider integration.

Fixed an issue where video content could overflow content areas in On-Page Edit view.

Fixed an issue where two icons could be displayed at the same time in context menu for content selectors.