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

crli
Dec 28, 2009
  6733
(0 votes)

Breaking changes between EPIServer 6 CTP2 and Release Candidate

Rather than enumerating every change between preview 2 and the release candidate we downloaded a few of the winning gadgets and made the required changes to make them work on the RC version.

This is the list of changes. Please feel invited to share any other breaking change that isn't listed here.

1. On the client, the gadget instance is passed directly instead of gadgetContext which has been removed

// from
function fcsm_initialize(e, gadgetContext) {
    fcsm_gadgetInstance = gadgetContext.instance;
// to
function fcsm_initialize(e, gadget) {
    fcsm_gadgetInstance = gadget;

2. The extensions in Shell Extensions now lives somewhere else

// from
<%@ Import Namespace="EPiServer.Shell.Extensions" %>
// to
<%@ Import Namespace="EPiServer.Shell.Web.Mvc.Html" %>

3. The dynamic data store has gained a factory

// from
DynamicDataStore<ReportSettings> store =
    DynamicDataStore<ReportSettings>.CreateStore("AnalyticsGadgetStore", false);
// to
DynamicDataStore store =
    DynamicDataStoreFactory.Instance.GetStore("AnalyticsGadgetStore")
    ?? DynamicDataStoreFactory.Instance.CreateStore("AnalyticsGadgetStore",
                                                    typeof(ReportSettings));

4. The dynamic data store “Find” has changed

// from
store.Find("GadgetId", gadgetId).FirstOrDefault<ReportSettings>();
// to
store.Find<ReportSettings>("GadgetId", gadgetId).FirstOrDefault();

5. The dynamic data store LINQ has changed

// from
from alertCollection in store
     where …
     select alertCollection;
// to
from alertCollection in store.Items<AlertMethodCollection>()
     where …
     select alertCollection

6. The gadget contracts namespace has moved

// from
using EPiServer.Shell.Gadgets.Contracts;
// to
using EPiServer.Shell.Gadgets;

7. Some resource texts have been moved

// from
[GadgetAction(ActionType.Menu, TextResourceKey = "Edit",
    ResourceType = typeof(EPiServer.Shell.UI.Views.Shared.SharedResources))]
// to
[GadgetAction(TextResourceKey = "Edit",
    ResourceType = typeof(EPiServer.Shell.Resources.Texts))] 

8. The configuration has changed to reflect that we now split modules by protected and public (added december 30)

// from
<episerver.shell>
  <siteSettings rootPath="~/U/" />
  <modules autoDiscovery="Minimal">
    <add name="DdsExplorer">
      <assemblies>
        <add assembly="DdsExplorer" />
      </assemblies>
    </add>
  </modules>
  <frameworkModules>
    <add name="Shell">...</add>
    <add name="CMS">...</add>
  </frameworkModules>
</episerver.shell>
// to
<episerver.shell>
  <protectedModules rootPath="~/U/">
    <add name="Shell" />
    <add name="CMS" />
  </protectedModules>
  <publicModules rootPath="~/public/" autoDiscovery="Minimal">
    <add name="DdsExplorer">
      <assemblies>
        <add assembly="DdsExplorer" />
      </assemblies>
    </add>
  </publicModules>
</episerver.shell>

9. Some style classes have a different name (added december 30)

//from
<div class="epi-defaultPadding">
<div class="epi-smallPadding">
//to
<div class="epi-padding">
<div class="epi-padding-small">

 

I also took the liberty of uploading the changes to codeplex. I take no responsibility for the quality of any gadget or any introduced errors. All credits goes to the original author. These are the gadgets that were updated:

Let me know right away if a gadget needs to be removed or if you need access to change a release.

Dec 28, 2009

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025

Optimizely CMS - Learning by Doing: EP09 - Create Hero, Breadcrumb's and Integrate SEO : Demo

  Episode 9  is Live!! The latest installment of my  Learning by Doing: Build Series  on  Optimizely Episode 9 CMS 12  is now available on YouTube!...

Ratish | Dec 15, 2025 |

Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025