Take the community feedback survey now.

Magnus Rahl
Oct 19, 2016
  3920
(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
Running Optimizely CMS 12 on .NET 10 in Azure

Upgrade your Optimizely CMS website to .NET 10!

Tomas Hensrud Gulla | Nov 21, 2025 |

Experimentation Evolution with AI (Masterclass Recap)

If you think you are not using AI in your experimentation program you are probably wrong. Ever asked an AI to rephrase a hypothesis or brainstorm a...

Polly Walton | Nov 21, 2025

Effortlessly Configurable Custom Fields for Scheduled Jobs in Optimizely with PlugInProperty

Optimizely CMS lets developers add job parameters—such as textboxes and checkboxes—directly to the scheduled job admin UI using PlugInProperty. Wit...

Ravindra S. Rathore | Nov 21, 2025 |

Optimizely Package Explorer: Now With Extra Superpowers

If you’ve ever opened a .episerverdata file and asked “What is in here?” (guilty as charged) — then this is your moment. We’ve given our open-sourc...

Allan Thraen | Nov 20, 2025 |