Release notes for Optimizely CMS and Commerce updates

Fixed an issue where the remaining URL was stripped from the CD response when the LinkItem/LinkItemCollection property refers to content.

Built-in support for list properties on content models was limited to primitive types such as string, number, and ContentReference. List properties are now supported as individual properties (such as int, string, XhtmlString and so on) including Block types. You can now define properties on content models like:

public virtual IList<string> MyStrings {get; set;}
public virtual IList<TeaserBlock> MyTeasers {get; set;} 

where TeaserBlock in example above is a defined block in CMS, like:

[ContentType]
public class TeaserBlock : BlockData
{...}

• Track usage (soft link indexing) for items that can reference content (such as IList<ContentReference>). 
• Import and export list definitions and data.
• New list properties are JSON-based (unless explicitly specified, for example, through BackingTypeAttribute).

Handle the case that a menu item of Global Menu Navigation is redirected from a Razor page endpoint, Html.CreatePlatformNavigationMenu() was not working correctly in this case.

The Range attribute on double type properties does not let you control how many decimals are being displayed in the UI.

As a workaround, you should omit the use of the Range attribute.

The current menu implementation now supports the code example in Highlight parent menu items.

Properties that use the SelectManyAttribute and get the values from a ISelectionFactory doesnt handle values that contains the character comma (,). The underlying storage uses that character to separate values from each other and therefor values including commas cannot be properly saved to the database. A fix was realesed that used JSON to handle the issue and while it worked correctly it was a breaking change, CMS-26903, that needed to be reverted. This new issue is a clone of the original CMS-23405 in order to find a different solution to the problem.

Fixed an issue where page in non-master language could not be created if has property was marked both Required and non CultureSpecific.

When handling multiple sites in Admin > Manage Websites the wrong start page might be highlighted when moving among sites.

Workaround: Reload the page by pressing Ctrl+F5 to select the appropriate start page.

Clients can create a block using endpoints.

Previously, if a block's parent was a page, then its parent would be that page, which was consistent with IContentRepository and explicit because there was no handling behind the scene. However, in UI, block's parent was ForThisPage (associated with the param parent).  

Supported endpoints

• Create 
• CreateOrUpdate (only support creating new content item)
• CreateMediaMultipart
• CreateOrUpdateMediaMultipart (only support creating new content item)
• CreateContentMediaBinary
• Move 

x-epi-parent-location-rule  – Header parameter is introduced to specify where content will be created or moved under: Content asset folder of parent or directly under parent. It has three values:

• Default
  • Create / CreateOrUpdate and Move endpoints – By default content is created directly under parent.
  • CreateMediaMultipart, CreateOrUpdateMediaMultipart, CreateContentMediaBinary endpoints
    • By default, content is created under asset folder of parent if parent is IResourceable (e.g Block or Page).
    • Otherwise, content is created directly under parent.
  • CreateContentMediaBinary endpoint
    • If parent is not provided, content is saved under global asset root folder.
    • If non-default value of parent location rule is present but no parent Id is provided, Http 400 response is returned with message Parent must be provided.
• Direct  – Content created directly under parent.
• AssetFolder
  • If parent is IResourceable (e.g Block or Page), content is created under asset folder of parent.
  • If parent is not IResourceable , 400 response is returned with message Asset folder is not supported for parent content.

Fixed an issue where Content Delivery API impacted all media URLs in CMS.