Try our conversational search powered by Generative AI!

Episerver - update 296

New release of Episerver Content Delivery API (support for retrieving Commerce catalog content and local blocks, and four new options).

The update applies to Episerver projects version 7.5 and higher, and contains finalized work items included in the latest iteration of services and related client-side NuGet packages. Continuous release updates are cumulative to include previous updates. Episerver supports all platform updates and strongly recommends that you keep ongoing projects up-to-date. You can install the update packages from the Episerver NuGet feed.

Note: A product release may contain multiple NuGet packages with inter-dependencies. This release information lists updated main package versions. When a release is built, other dependent packages may also be bumped to new versions, although they contain no publicly visible changes. This is done to avoid dependency errors. When you upgrade, NuGet alerts you to upgrade related packages to the required versions. For Commerce, it is important to ensure that you are running the same version of CMS and Commerce, both in the front-end and back-end applications.

Updated services and main packages

Click an item in the list to see work item details.

APIs_32.svgEpiserver Content Delivery API

New features:

    • HAPI-10: Support for retrieving Commerce catalog content
      The ContentDeliveryApi.Commerce – CD.Commerce supports rendering Episerver Commerce content in SPA site with Vue or React. Basically, client can use the default endpoints provided in ContentDeliveryApi.Cms package to retrieve Catalog content through CD.Commerce in the JSON format. See the developer guide topic Content Delivery API and Commerce for more information.
    • HAPI-534: Support for local blocks and new options for Content Delivery API has been added
      The following options have been added:
      • ValidateTemplateForContentUrl: Enable/Disable the validation of content URL. For example, this option should be set to false if you want to get the URL of a content folder.
      • FlattenPropertyModel: If this option is set to true, the response JSON will be flattened.
      • IncludeNullValues: If this option is set to false, the JSON serializer will ignore all null values in the response.
      • IncludeMasterLanguage: If this option is set to false, the response model of content will not contain the MasterLanguage property.

Important notifications

Related topics

Last updated: Dec 30, 2019