Optimizely - update 373

Action on product controller fails to execute if SEO URL is enabled.

Steps to reproduce:

1. On a Quicksilver sample site, change MapDefaultHierarchialRouter from false to true: CatalogRouteHelper.MapDefaultHierarchialRouter(RouteTable.Routes, true);
2. Navigate to a product from the start page and try to change the variant (shoe size for instance).

Expected:

Should hit public ActionResult SelectVariant(FashionProduct currentContent, string color, string size, bool useQuickview = false).

Actual:

SelectVariant is not hit.

Scrolling error when loading items in Order/Cart list in the Order Management (CSR) view.

Steps to reproduce:

1. Open Order Management.
2. Scroll to the bottom of the page to load more orders/carts.
3. Repeat step 2.
4. Observe that more blank spaces appear.
5. To trigger loading of more items, scroll to the bottom of the blank page.

This issue relates to cart deserialization, where Cart Properties allow for duplicate keys. The serialized cart was stored in the database as JSON, with duplicated keys for "CampaignCode" in the Properties field. This caused the the Properties HashTable deserialization to fail.

Update length for MetaField table.

Update the LENGTH column of MetaField table for 'NText', 'LongString', 'LongHtmlString'  meta data type when the LENGTH <=16.

GetReferencesToContent result is incorrectly cached.

Step to reproduce:

1. Use IContentRepository.GetReferencesToContent to get content reference to an asset.
2. Add the asset to, or remove it from some catalog content.
3. Use IContentRepository.GetReferencesToContent again.

Expected:

Result list is updated.

Actual:

Result list is not updated.

This feature lets order managers and customer service representatives track the history of a specific order for audit and analysis purposes. The feature automatically records a range of events related to order/shipment status update, payment, and promotion of an order.

In accordance with GDPR regulations, you can choose whether you want to accept cookies for Marketing Automation connectors. (Normally, the cookie is created when you submit a marketing automation form.)

Customers are responsible for presenting the cookie option dialog box to the user, obtaining the response, and then passing the response to Optimizely through the IPersonalizationEvaluator.AcceptCookies property. If the user chooses not to accept the cookies, some or all functionality of the connector will not work; the form will post successfully but personalization features will not.