Take the community feedback survey now.

Jonas Bergqvist
Oct 6, 2014
  6592
(0 votes)

Comments and Ratings in Commerce 8.0

In Commerce 8.0, we have dropped the dependency to EPiServer Common Framework. When dropping the dependency, we had to remove all classes in EPiServer.Business.Commerce which had dependencies to EPiServer Common Framework. With the dropped classes, we dropped some functionality. This blog post will show how to recreate the missing functionality.

Dropped functionality

When we dropped the dependency to EPiServer Common Framework, we lost comments and ratings, which has been a part of Commerce in earlier versions. This will cause problems when upgrading to Commerce 8, if the site uses comments or rating.

Dropped classes

The following classes have been dropped from EPiServer.Business.Commerce:

  • Comment
  • CommentExtensions
  • DynamicEntry
  • DynamicEntryHandler
  • DynamicEntryProvider
  • IMessage
  • IProductComment
  • IProductRating
  • ProductComment
  • ProductCommentResult
  • ProductEntry
  • ProductEntryHandler
  • ProductRating
  • RatingMessage
  • UserExtensions

Make logging work

In “EPiServer CommonFramework”, there is functionality for logging, which will help developers to find problems in the code. This code will not be available anymore as long as the “EPiServer CommonFramework” nuget package isn’t explicitly installed on the site. Projects that has used EPiServer Common logging should change to work directly against “log4net”. By changing the using statement to “log4net”, log4net will start handling the logging.

Recreate functionality

To add back comments and ratings after upgraded to Commerce 8, the following steps are needed:

  1. Add the package “EPiServer Common” to your project.
  2. Download the zip-package below.
  3. Add the classes to your project after you have unzipped the package.

After you have the classes in to your project, you have to add a couple of lines to an initialization module:

// register entity provider with supported types
EntityProviderHandler.Instance.RegisterEntityProvider<DynamicEntityProvider, DynamicEntity>();
EntityProviderHandler.Instance.RegisterEntityProvider<DynamicEntityProvider, ProductEntity>();

Download

Zip file containting comments and ratings: CommentsAndRatings.zip

Oct 06, 2014

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Opticon London 2025

This installment of a day in the life of an Optimizely OMVP gives an in-depth coverage of my trip down to London to attend Opticon London 2025 held...

Graham Carr | Oct 2, 2025

Optimizely Web Experimentation Using Real-Time Segments: A Step-by-Step Guide

  Introduction Personalization has become de facto standard for any digital channel to improve the user's engagement KPI’s.  Personalization uses...

Ratish | Oct 1, 2025 |

Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP : 🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites What I didn...

dada | Sep 29, 2025

Creating Opal Tools for Stott Robots Handler

This summer, the Netcel Development team and I took part in Optimizely’s Opal Hackathon. The challenge from Optimizely was to extend Opal’s abiliti...

Mark Stott | Sep 28, 2025

Integrating Commerce Search v3 (Vertex AI) with Optimizely Configured Commerce

Introduction This blog provides a technical guide for integrating Commerce Search v3, which leverages Google Cloud's Vertex AI Search, into an...

Vaibhav | Sep 27, 2025

A day in the life of an Optimizely MVP - Opti Graph Extensions add-on v1.0.0 released

I am pleased to announce that the official v1.0.0 of the Opti Graph Extensions add-on has now been released and is generally available. Refer to my...

Graham Carr | Sep 25, 2025