Mari Jørgensen
May 24, 2011
(10 votes)

EPiServer Commerce and Composer R2 – a Love Story!

With the release of EPiServer Composer 4 R2 we now got a great tool for building and optimizing personalized start pages and landing pages. What better way to combine a flexible layout with personalized content, than for an ecommerce site.

New and improved Composer

thumbsup_iconThe Composer R2 release has several new/improved  features:

  1. Personalization blocks
  2. New preview mode
  3. Editing block trough double-click
  4. Improved drag and drop
  5. New and improved functions
  6. Toggle visibility of block borders and headers


Easier to install

Page and function type definitions are now automatically registered as part of the Sample package installation - no longer need for manual import in Admin mode.

No more CSS and JQuery conflicts

In Composer 4 R2 the Composer CSS and JavaScript have now been encapsulated to make sure it does not interfere with your custom files. This is great news for us developers!

To learn more about news in EPiServer Composer R2, read Peter Sunnas article.

Installing Composer on a Commerce site

As the title of the blog post indicated, getting Composer to play nice with the demo Commerce site is pretty straight forward. You need to make minor adjustments to the Composer templates, this is because the Composer sample package is built for the Alloy Technologies sample site. The necessary changes are described below. 

Path to MasterPage file

Change the MasterPageFile attribute for the Composer template files (aspx files located in <siteroot>/Composer/Pages/) to use the Commerce master page.

Name of Content Placeholder

In the same aspx files as mentioned above, we also need to change the name of the content placeholder to use.


Also, since the Commerce demo site is using “en-US” as the default UI language, you might notice some missing translations in the Composer dialogs.


A quick fix for this is to

  1. Locate Dropit.Extension_EN.xml inside the lang folder
  2. Copy file and name it Dropit.Extension_ENUS.xml
  3. Open file and change
    <language name="English" id="en"> to
    <language name="English United States" id="en-US">

That’s it – your new commerce pages are just a few drag and drops away. 


May 24, 2011


May 24, 2011 03:00 PM

Excellent work.

May 24, 2011 03:22 PM

If you experience installation issues, have a look at this forum thread:

Aug 22, 2011 06:02 PM

Great blog Mari! Straightforward and accurate.

Please login to comment.
Latest blogs
Caching & Rendering of metadata from the DAM

For the EPiServer.Cms.WelcomeIntegration.UI 1.2.0 release, we have facilitated the ability to cache and render metadata from assets within the DAM....

Matthew Slim | Jun 2, 2023

Conversion Rate Optimization: Maximizing ROI through Data-Driven Decisions

In today's digital landscape, businesses are constantly looking for ways to improve their online presence and drive more conversions. One effective...

JessWade | Jun 1, 2023

Enhance Your Writing with Suggestions

Are you tired of staring at a blank screen, struggling to find the right words? The Epicweb.Optimizely.AIAssistant Addon is here to revolutionize...

Luc Gosso (MVP) | May 31, 2023 | Syndicated blog

Content Graph - Letting GraphQL do all the hard work for you

Background As we have seen before, setting up Content Graph on the CMS side is pretty easy. However, when it comes to the “head” part of the setup,...

Kunal Shetye | May 26, 2023 | Syndicated blog