Using Session State in Custom Editor Dialogs

Article information
Article relates to	RadEditor for ASP.NET AJAX
Created by	Stoyan Stratev

Starting with version 2008.2.1001, the RadEditor control no longer requires Session State to be activated in the web application. This was done in order to allow the editor to work in all application scenarios. As a result of this change, if you have customized one of the editor dialogs and are using the Session object in the code, the dialog will stop working after you upgrade to the latest release. You might see an exception with the following text:

Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the <configuration>\<system.web>\<httpModules> section in the application configuration.

To fix this, you will need to create a new dialog handler class with enabled session for the editor popups and update your dialog handler definition in the Web.config file to point to the new class. You can put the new class in the App_Code folder of your web application:

VB.NET

C#

The class simply inherits the default dialog handler and implements the IRequiresSessionState marker interface. To enable the new dialog handler, open the application's Web.config file and update the <httpHandlers> element. The element is located in the <system.webServer> section when running in IIS 7 Integrated Mode and in the <system.web> section in all other cases.

old definition:

new definition:

The only changed part is the type attribute. It should hold the type and assembly name of your new dialog handler. In this case the type is CustomHandler.SessionStateDialogHandler and the assembly name is App_Code. If you are using a web application project, which does not have an App_Code folder, simply replace App_Code with the name of your project's output assembly.