A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Mari Jørgensen
May 24, 2011
  4281
(0 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.

ContentPlaceHolderName2

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.

Translations

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. 

viewMode

May 24, 2011

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026

How to run Optimizely CMS on VS Code Dev Containers

VS Code Dev Containers is an extension that allows you to use a Docker container as a full-featured development environment. Instead of installing...

Daniel Halse | Jan 30, 2026

A day in the life of an Optimizely OMVP: Introducing Optimizely Graph Learning Centre Beta: Master GraphQL for Content Delivery

GraphQL is transforming how developers query and deliver content from Optimizely CMS. But let's be honest—there's a learning curve. Between...

Graham Carr | Jan 30, 2026