Release notes for Episerver updates

Steps to reproduce:
1. Create CultureSpecific LinkItemCollection property on a page and have English and Swedish enabled.
2. Add link in LinkItemCollection property for English version of page.
3. Create draft of Swedish version of page.
4. In projects "Overview" export language file and copy paste the information from the English "LinkItemCollection" property so it looks similar in the Swedish version with a LinkItemCollection property.
5. Import the file.
6. Run Scheduled job "Import Translation Packages " and take a look at the Swedish draft.

Expected:
Should translate LinkItemCollection links.

Actual:
LinkItemCollection property is empty.

Make Auto translate function work with new Text Translator API from Microsoft.

Versions that are being used?

EPiServer.CMS 11.14.2
EPiServer.CMS.UI 11.23.6
EPiServer.Labs.LanguageManager 3.3.1
EPiServer.Marketing.Testing 2.5.12

1. Install Alloy sample site with the versions and add-ons listed above.
2. Add Language Gadget on the Edit mode.
3. Start A/B Testing on a page.
4. Click View Test on the notification bar on the page.
5. Open console in developers tool, and refresh the page.
Result: there are errors on console "Unable to load /EPiServer/EPiServer.Labs.LanguageM…tails&dojo.preventCache=1588072078383 status: 500"

Steps to reproduce:
1) Create an Alloy project.
2) Install the EPiServer.Labs.LanguageManager plugin.
3) Add the code in the attached EventInitialization.cs.txt file.
4) Run the site.
5) Add the LanguageManager gadget.
6) Select any page and create a version in another language so it has at least 2 languages.
7) Use the LanguageManager gadget to delete the newly created language branch.

Expected result:
A dialog displaying a cancelation reason.

Actual result:
The ui fades to gray, a spinner spins forever, and you see this get error "Error: Unable to load /EPiServer/EPiServer.Labs.LanguageManager/Stores/language/ status: 500"

Steps to reproduce:

1. Create a page called Page 1.
2. Create a Swedish version of Page 1 called Page 1 - SV.
3. Add Page 1 - SV to a translation project called Translation.
4. Switch to Translation project view.
5. Select Options > Download Translation Package to download the translation package.

Expected:
The Name in URL field is in the translation file.

Actual:
The Name in URL field is not added to the translation file.

Steps to reproduce:
1. Set up the translation provider "Cognitive Service Translator" with SubscriptionKey = "30a7926f11be4395ab920b0a7329ce5d" in Admin Mode.
2. Create catalog content in SV.
3. Input a long text to the Description field in All Properties mode/SEO tab:
"Bangladeshs cricketteam drog bara upp på en av de två riktade moskéerna när attacken började, berättade lagets tränare CNN.

En video som publicerades på Twitter visade att de bangladeshiska idrottsmännen gick bort från moskén som en polisbilhuvud i motsatt riktning, sirener grälde.

Teamet skulle spela mot Nya Zeeland laget den närmaste veckan."
4. Publish it.
5. Replace content by auto-translating from SV in FR language.

Expected:
The text is translated correctly.

Actual:
The page loads forever.

Steps to reproduce

1. Add a property to a Standard Page.

   [Display(

   GroupName = SystemTabNames.Content,

   Order = 400)]

   [CultureSpecific]

   public virtual ContentReference MyContentFolder { get; set; }

2. Create a Standard Page.
3. Select a folder as value of the property.
4. From LM, add to a translation project, check "Add children" and "Add related contents".

Expected:
You can add a page to a translation project

Actual:
Error on console. The page cannot be added to the translation project.

Steps to reproduce:

1. In Edit Mode, compare 2 languages so that the context is compareediting
2. Create a project
Expected: Successfully created a new project

Actual: Edit Mode is spinning, error in console:

(I tested in feature/LM-275 branch)

The MS translation API will be obsoleted on 30 April (https://docs.microsoft.com/en-us/azure/cognitive-services/translator/migrate-to-v3). We updated LM to use new API version. After 30 April, previous versions of LM might not work.

Steps to reproduce:

1.Create an English version of content (page, block).
2.Create a project.
3.Drag and drop the content to the project overview.
4.Select the content.
5.Add the content to the Translation Project via the Language Manager gadget.
6.Open the project overview.

Expected: The content displays normally

Actual: The content doesn't display at that time. It only displays after a long time (more than 15 seconds).
Tested on Firefox 60.0.1