Release notes for Optimizely CMS and Customized Commerce updates

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 error that returned a 400 with message Sort order must be an integer when specified or Enabled must be a boolean when specified when you called PATCH languagebranches with sortOrder enabled.

Fixed an issue that duplicated the language property when you sent a request to the CD endpoint with select=language.

Fixed an issue that caused a 400 Bad request error to be returned for content that had a link item pointing to a content with no template.

Fixed an issue that caused the {{IPageRouteHelper.ContentLink}} to return the Start page when you requested a CD endpoint and the host was language-mapped.

Content Delivery API and Content Management API supports querying and updating SimpleAddress and VisibleInMenu metadata of content.

You can get rich text stored in XhtmlString in a different structured delivery format than just an HTML string. 

Optimizely Content Cloud added support for list properties (including for blocks). You can define list properties through ContentDefinitions API also.

To define a list property then dataType should be set to PropertyCollection and itemType to the type of items within the list. 

Example of a property definition to create of a list of blocks. Here the blockType given as itemType must be an existing blockType (or part of same manifest) within CMS.

{                
   "name": "BlockList",                
   "dataType": "PropertyCollection",                
   "itemType": "InlineBlock"            
}

Or for example to define a list of Urls

{                
  "name": "UrlList",                
  "dataType": "PropertyCollection",                
  "itemType": "PropertyUrl"            
} 

Fixed an issue that returned a 400 error when you called CD GET on a content type that had a list of XhtmlString.

Updated package dependency range of CD.Search to let ContentDeliveryAPI work with newer versions of Episerver.Find, including Episerver.Find 16 and above.