Magnus Rahl
Oct 19, 2016
  4031
(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
Using Scalar with Optimizely CMS

OpenAPI, Content Delivery API, and Modern API Documentation Modern Optimizely CMS solutions are increasingly API-first. Whether you are building a...

Andreas Ylivainio | Feb 6, 2026

Optimizely PaaS + Figma + AI: Auto‑Generate Blocks with Cursor

What if your design handoff wrote itself? In this end‑to‑end demo, I use an AI Agent (inside Cursor) to translate a Figma design into an... The pos...

Naveed Ul-Haq | Feb 5, 2026 |

Graph access with only JS and Fetch

Postman is a popular tool for testing APIs. However, when testing an API like Optimizely Graph that I will be consuming in the front-end I prefer t...

Daniel Halse | Feb 4, 2026

Best Practices for Implementing Optimizely SaaS CMS: A Collective Wisdom Guide

This guide compiles collective insights and recommendations from Optimizely experts for implementing Optimizely SaaS CMS, focusing on achieving...

David Knipe | Feb 4, 2026 |