May 3, 2010
(0 votes)

Changes to the EPiServer UI dialog system in EPiServer CMS 6

When an EPiServer CMS editor opens a dialog it is usually done by a JavaScript API called EPi.Dialog. This API is responsible for instantiating  the dialog as well as sending data to and from the dialog. In EPiServer CMS 5 and 6 dialogs are created as new windows that are styled as “pop ups”. This is nothing that the user normally is aware of although a user can close the dialog window with the normal close window function in the web browser.

Inline dialogs vs. external dialogs

An inline dialog is created as a part of the existing page and window but styled to look as a pop up dialog. This means that the dialog is technically the same page as it’s “parent” window. In Internet Explorer 8 new windows are run under a separate thread. This can cause race conditions between script running in different windows. The EPiServer Development Team have spent time addressing bugs that are caused by race conditions when closing a dialog, specially if the dialog has made a post back before closing itself.

Dialogs in the Tiny MCE implementation

In the Tiny MCE implementation in EPiServer CMS 6 external dialogs are used when opening built in Tiny MCE dialogs (for instance the insert/edit image dialog). These dialogs works a bit differently than the rest of the dialogs in the EPiServer CMS UI. For instance, it’s possible to access the underlying UI when a dialog is opened. Please note that this behavior is not intentional.

What are the changes we plan to implement?

To address the race condition problems in IE 8 (and new versions of IE and possible other browsers) as well as creating one user experience for editors when using dialogs we would like to rewrite EPi.Dialog to use inline dialogs. Since we are currently working on upgrading Tiny MCE to the latest version (3.3.4 at the moment) we would like to do these changes as the same time.

How will these changes affect my code?

The hypothesis is that these changes will not affect the public API:s for the EPi.Dialog classes. JavaScript code that is executed in a dialog might be affected if it relies on the knowledge that the dialog lives in a separate window. For instance, a call to will return a different object in an inline dialog compared to an external dialog. Resizing the current window size will also work differently with inline/external dialogs.

We are interested in your feedback

We are normally very restrictive with making breaking changes, but since we believe that very few will be affected by this change we would really like to address these issues. If you know that this will affect you, for instance if you are using EPi.Dialog in an EPiServer CMS module, then please reply to these post so that we can this into consideration before making a final decision.

May 03, 2010


Sep 21, 2010 10:33 AM

Sounds like a good plan. :-)

I also think that it is important to define clearly what is part of the public API that EPiServer developers can use safely to extend the EPiServer user interface with plug-ins.

If you as a developer in a normal project extends EPiServer user interface you will rely on EPiServer's CSS classes and JavaScript library. It is hard to know what is safe to use...

Sep 21, 2010 10:33 AM

Hi Fredrik!

You have a very valid point regarding what is public or not regarding the user interface. One cause of this is that there is currently not any SDK for the client API:s that is intended to be public. We are currently working on a more streamlined way to work with UI extensibility for the EPiServer product family with more documentation and guidelines for partner developers. We are still very early in this process but be assured that we will write more about this as soon as we have the basics in place and need feedback from the EPiServer community.

Mari Jørgensen
Mari Jørgensen Sep 21, 2010 10:33 AM

Hi Linus!

I think the change is a good idea. :-)

I now there are a lot of modules that are using EPi.Dialog to interact with EPiServer dialogs.
It would be great if the changes could be described in detail, similar to what Henrik wrote when the EPi.Dialog was introduced in EPiServer 5:

Please login to comment.
Latest blogs
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog