Optimizely - update 384

Fixed an issue where the Linux container setup introduced a kind of proxy or firewall that Windows hosting did not have. This caused the local container IP (::ffff:169.254.129.1) to be sent to the Peerius APIs. This issue was addressed by adding Episerver.Tracking and Episerver.Personalization to our sites. 

Migration step: GroupName on property was not updated. It was created under the NewGroupName tab, and the old property was moved to the Content tab.

In a multi-site scenario, locally (with localhost and separate port numbers), content language was not determined correctly because the code in EPiServer.Globalization.Internal.HostLanguageResolver was only comparing the host name, and not the port number.

Steps to reproduce: 

1. Install Alloy.
2. Update EPiServer.CMS package to 11.15.1.
3. Compile and build.
4. On start page, add a Button block in a content area.
5. Enter required text.
6. In link, click external and paste the JavaScript:
   javascript:void(location.href='mailto:' + String.fromCharCode(106,111,104,97,110,46,97,110,116,105,108,97,64,111,112,116,105,109,105,122,101,108,121,46,99,111,109))
7. Save and publish block and page.
8. Go to admin.
9. Run Link Validator job.

An exception caused the job to fail and stop executing, instead of marking it as an invalid link and ignoring it going forward, to complete with a summary of scanned links and failed links.

If you saved DisplayName with only spaces, it did not show correctly in UI Admin. It should have a fallback to ContentType.Name.

When connection string was configured with MultipleActiveResultSets (MARS) set to true the application generated SQL timeout exceptions when running on Linux due to thread starvation.

The logging compatibility API was made obsolete. It was added to simplify the transition fro log4net but is no longer needed.

When accessing the URL of language content that was expired, the AlternateLinks handler wrote out the expired version that then became a 404 error, instead of using the fallback language.

When the job failed to delete a content asset folder, the job was stopped and marked as failed instead of logging the issue and continuing with other candidates.

Logging of errors was enhanced to be more informative.

When a culture was set in web.config, the indexing job should have updated the SearchTypeName. For example, setting the culture to Swedish (sv-SE), SearchTypeName should have updated to Sida but was listed incorrectly as Page.

Added support for attributes on static client resources.

The class EPiServer.Framework.Web.Resources.ClientResource.cs should have a dictionary of attributes that are added to the html element.

One example where it can be used:

Add SRI - Sub Resource integrity, on injected scripts. ClientResource should provide a way to add the integrity attribute on the generated html element.

Example:
 
{{<script src="https://example.com/example-framework.js"integrity="sha384-oqVuAfXRKap7fdgcCY5uykM6+R9

Added the Edit command to the selected item in ContentReference selector so that users can easily go to that item. If the selected item is a block, it also has the Quick Edit command.

The command is available even if the ContentReference property is readonly.

Re-introduced the divider for the context menu.

An incorrect error message was displayed when you entered an invalid password of more than 6 characters.

Displayed restriction information for properties of types ContentReference and ContentArea similar to ContentReferenceList.

Changed the button text in ContentReference selector from [...] to Select [Type] to indicate the type of contents can be selected.

Added an (arrow-up-right-from-square) icon to some global navigation menus to indicate that the menu link opens in a new tab or new window.