Release notes for Episerver updates

Issue where images are not rendered on a third-party website.

Code has been modified to use the parameters for allowing the htmlcanvas JavaScript to perform cross-domain loading of images.

If the key is missing, a refresh has to be performed to get the tests and variants from the database.

AdminConfigTestSettings caches current settings and never reads again on load balanced machines. This is evident in the Current getter method. There is no need to cache this and whenever Current is read we should just get it from the DynamicDataStore

There is a BOM character created in ABT Script after customer added the AB Testing module into their project. It causes a redundant white line in the site footer, for some customer it adds a white bar on the top of the page.

See MAR-1326 for more details.

Currently we are newing up an instance of TestingContextHelper in the TestManager. We should be getting a service registration of this item.

ConfigurationMonitor resets the load balanced environments at startup causing the rest of the lb machines to toggle the state of ab which then triggers another reset from each lb node, sending another message out to the machines causing another reset message, and so on.

Additionally this configuration monitor is setup to poll every 500msec. There is no reason we need to poll so often. Change to 1 minute

Also added app setting configuration values to override defaults:
EPiServer:Marketing:Testing:TestMonitorSeconds
EPiServer:Marketing:Testing:ConfigurationMonitorSeconds

Redundant ServiceLocator.GetInstance<> calls caused high allocations to load services.

Related to MAR-1302

Problem:

When a user is not a member of one of the default roles (such as CMSAdmin or CMSEditor), the user cannot access or edit an AB Test Controllers. You can now specify a comma-separated list of one or more custom roles to provide access to the AB Test Controllers.

Solution:

1. Add a comma separated list of roles to the app keys. For example:

   <add key="EPiServer:Marketing:Testing:Roles" value="Content_Admins" />

2. Create a new mapped virtual role section. For example:

   <virtualRoles addClaims="true">

   <providers>

   ...

   <add name="LocalAdmins"

   type="EPiServer.Security.MappedRole, EPiServer.Framework"

   roles="SWE_Admins"

   mode="Any" />

   </providers>

3. Add users to those roles so they can access the UI editor again.

Steps to reproduce

1. Create an Alloy site.
2. Install ab testing.
3. Navigate to edit cms pages.
4. Select start.
5. Edit the "Alloy plan" block in the bottom left of the screen.
6. Replace the Alloy plan image with another of your choosing.
7. Click publish / Ab Test changes. The image you see in the challenger should be the image you just replaced.
8. Click cancel.
9. Replace the image with a new image.
10. Publish / Ab Test changes.

Expected:
The image in the challenger spot should be the one used in step 9.

Actual:
The image is the one shown in step 6.

Workaround:
Click revert changes and use the image you wanted to use in step 9

Currently, when AB testing is installed, we listen for LoadedContent and LoadedChildren, so we can swap views out for running tests. This hook exists even if there are no active tests. This activity affects performance.