Per Hemmingson
Jan 28, 2010
(2 votes)

EPiServer World News

A week ago we upgraded EPiServer World to the release candidate for EPiServer CMS 6 with the motto “Drinking our own champagne” and put it to the real test.

I have previously written about upgrade experiences for EPiServer CMS 5 R2 and its breaking changes. The great thing about CMS 6 is that there are no breaking changes, and the upgrade process is actually a lot easier than before* (for our website). The Development team has done a superb job of creating a stable release as well as a smooth upgrade script. The actual upgrade took 5 minutes with EPiServer Deployment Center, then you just sit and wait while it migrates all XForms data to the new Dynamic data store. 

There are of course other changes that Per Bjurström has already blogged about that you should read up on.

The site worked without recompiling the code, but there is some obsolete code functionality in XForms (pageAfterPost) and the FriendlyUrlRewriteProvider, to name a few that you should update.

We also have updated EPiServer World with new functionality and corrected some bugs, especially with WebEx/online sessions.

Most notably we have added a new forum feature, Mark as Answered:


When you select to Mark as answer, the answered post will look like this:


This has been implemented so that it is quicker to find answers to your problems as well as to answer unanswered questions. We are also working on a Community recognition program so you will get points for contributing to our EPiServer Community, and forum posts marked as answered will of course receive more points.

The second new feature added is a feedback form so you can send us comments, suggestions and errors you find on the site:


You can still use the mailbox  Note that we use Email Obfuscator to protect all e-mail addresses on our sites.

A lot more new requested functionality is in the pipeline and we are continually updating the site to ensure that there is one World to rule them all. :-)

Jan 28, 2010


Per Hemmingson
Per Hemmingson Sep 21, 2010 10:33 AM

To clarify the XForms PageAfterPost property, our solution to it was simply using PageGuidAfterPost instead, e.g:

PageReference pageReference =

if (PageReference.IsNullOrEmpty(pageReference))

PageData pd = GetPage(pageReference);

if (pd == null)


Please login to comment.
Latest blogs
Zombie Properties want to Eat Your Brains

It’s a story as old as time. You work hard to build a great site. You have all the right properties – with descriptive names – that the content...

Joe Mayberry | Mar 29, 2023 | Syndicated blog

Optimizely finally releases new and improved list properties!

For years, the Generic PropertyList has been widely used, despite it being unsupported. Today a better option is released!

Tomas Hensrud Gulla | Mar 28, 2023 | Syndicated blog

Official List property support

Introduction Until now users were able to store list properties in three ways: Store simple types (int, string, DateTime, double) as native...

Bartosz Sekula | Mar 28, 2023

New dashboard implemented in CMS UI 12.18.0

As part of the CMS UI 12.18.0 release , a new dashboard has been added as a ‘one stop shop’ to enable editors to access all of their content items,...

Matthew Slim | Mar 28, 2023