Ephox EditLive! can be integrated seamlessly into ASP.Net applications with the use of the ASP.Net server control. This control was designed for use with ASP.Net 1.0 and 1.1, and with the release of version 6.1 of EditLive! this control supports ASP.Net 2.0. This has now been thoroughly tested, with some constraints identified. The constraints are listed below. 

As EditLive! is an HTML editor, it will need to be able to edit HTML, and send HTML text back to the server. This means that the .net request validation functionality will need to be disabled through setting the property validateRequest="false" in the page (through the Page directive: <%@ Page validateRequest="false" …%>). 

The server side code behind view exposes the EditLive! content through properties on the control. It is possible to access content at any stage in the life cycle through these attributes. Updates to content will only be visible in the control when they are made before rendering the applet. This means that content updated in the Page_Load event will be correctly reflected, but changes made in the event handlers for form events will not be reflected in the client control. In order to update content on a form event, the JavaScript APIs for EditLive! will need to be used. 

In order to use multiple instances of EditLive! the "AppletName" of each control will need to be initialised in the Page_Load event. Each applet name should be set to a unique value, which can then be used to access content in the postbacks. A useful value for the applet name is the name of the control.

This entry is filed under Integrating EditLive!. You can follow any responses to this entry through the Atom feed. You can leave a response, or trackback from your own site.