Magnus Rahl
Oct 19, 2016
  4070
(4 votes)

Planned Breaking Changes in Commerce 2016

As previously announced, new major versions of CMS and CMS UI are coming. Compatible versions of Commerce, Find for Commerce and Service Api will be available from day one. In order to create a compatible version of Commerce, we have to do a small number of low-impact breaking changes in Commerce, which means Commerce too will have a new major version.

The breaking change consists of removing some types that support the Commerce UI (not intended to be used directly) from the EPiServer.Commerce.Core package. The removed types are:

  • EPiServer.Business.Commerce.Providers.ProductSearchProviderBase
  • EPiServer.Business.Commerce.Providers.ProtectedProductSearchProvider
  • EPiServer.Business.Commerce.Providers.ProductSearchProvider
  • EPiServer.Commerce.Catalog.CatalogMetadataExtender
  • EPiServer.Commerce.Marketing.PromotionDataMetadataExtender
  • EPiServer.Commerce.SpecializedProperties.DictionarySelectionFactory
Oct 19, 2016

Comments

Please login to comment.
Latest blogs
Integrating Searchspring with Optimizely – Part 1: Architecture & Setup

Integrating Searchspring with Optimizely – Part 1: Architecture & Setup

Wiselin Jaya Jos | Mar 20, 2026 |

CMS 13 Preview 4 — Upgrading from Preview 3

This is the third post in a series where I use the Alloy template as a reference to walk through each CMS 13 preview. The first post covered...

Robert Svallin | Mar 20, 2026

The move to CMS 13: Upgrade Notes for Technical Teams

A technical walkthrough of CMS 13 preview3 and headless work: what is changing, where the risks are, and how an upgrade and what to expect

Hristo Bakalov | Mar 20, 2026 |

Customizing Product Data Sent to Optimizely Product Recommendations in Optimizely Commerce

A practical guide to customizing IEntryAttributeService in Optimizely Commerce so you can override product titles, add custom feed attributes, and...

Wojciech Seweryn | Mar 20, 2026 |