World is now on Opti ID! Learn more

Jonas Bergqvist
Oct 6, 2014
  6573
(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
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |