Mark Everard

Hello, I'm Mark – a PhD physicist turned technologist / architect.

Missing Personalization Containers

with 2 comments

Combining Composer with Visitor groups on your EPiServer CMS6 R2 site gives your editors a powerful new way of working with ‘personalized’ content, via the built-in Personalization Container Composer element.

This function allows an editor to create a Composer area that will display a unique list of other Composer functions; depending on which visitor group a user is matched to in your site. This means that editors can personalise more than just page content, and can also adjust the page layout and functionality offered to each visitor, by dragging different Composer functions into each Personalized ‘slide’ within the Personalization Container function.

Upgrading a site to 6 R2

After upgrading a few sites from CMS6 to CMS6R2, if you don’t check the option to import PageTypes during the upgrade process (which if you’re using PageTypeBuilder you might think you can skip) then  the Personalization container isn’t created, and you’ll be missing this piece of functionality.

personalization container

The easiest way to re-create this function is to export the composer PageType information from a ‘fresh’ install of the Composer / R2 Alloy Tech site, and then import this into your site.

To save you the hassle of setting up a fresh demo site. I’ve included an exported Composer Personalization function as a download below (.xml format). – Import using EPiServer Composer Import / Export page.

You just need to import this using the Composer import feature in EPiServer Admin mode, and hey presto!

Written by mark

January 6th, 2012 at 7:00 pm

Posted in EPiServer