Episerver - update 352

Fix for making default values for Commerce content work for selected languages.

Steps to reproduce:

1. On the Commerce Quicksilver sample site, make sure there are multiple languages enabled for catalog content (en, sv - where en is master and selected language).
2. Create some content which inherits from NodeContent like:

public class TestContent : NodeContent 
{
     [CultureSpecific] 
     public virtual string Text {get;set;}

     public override voide SetDefaultValues(ContentType contentType)
     {   
        Text = "Some text";
        base.SetDefaultValues(contentType);   
     }
}

          3. Create TestContent in catalog.

Expected:

Should set default value for all language versions (en, sv).

Actual:

Only sets it for the selected language (en) when creating the content (not for sv).

This is a fix for an issue where the API allows for addition of duplicate assets to products.

Scenario: When adding multiple media items with the same key/ID to a product, it causes an exception (duplicate key) when saving the next time.

Cause: 

AssetServiceDatabase.CommitAssets does not check duplication for the updatingRows list.

In this case, an exception should be thrown.

This fix makes the media pane available also in the Commerce Marketing user interface.

Scenario:

For the Catalog user interface, the Media pane is enabled by default:

In the Marketing user interface, the Media pane is anot available:

This feature implements TokenEx for processing Authorize.net payments in Order Management. 

When a customer service representative selects Authorize.net as payment method, TokenEx will protect sensitive payment information when processing the payment.

The AuthorizeTokenEx payment provider is installed through a separate package.

Fixed an issue where calling 

ContentRepository.GetReferencesToContent(contentReference, false)

would throw exception after upgrading to CMS 11.30.1

Steps to reproduce:

1. Create a form with a Datetime or Datetime range element, and a Submit element.
2. Add the form to a page, and then publish the page.
3. View the form.
4. Click on the date picker.

Expected:

The date picker is displayed.

Actual:

The date picker is displayed but there is an 404 error in the console.

ReCaptcha has been upgraded from v2 to v3.