Skinning the Rad Editor and Dealing with Dialogs.

[Chad]

We are using the rad controls inside of sharepoint.  We've done a lot of skinning of individual RadControls.  We've created our own non embedded skins for each of the controls.

With our custom LV skins, we've set this key in the web.config, and it has worked with all the other controls.

<

add key="Telerik.Skin" value="LV" />

The rad editor has presented some problems.  It is skinned and working,but if we click on the table editor and then the table wizard, it pops open a rad window that throws an exception about the SpinBoxColumns being unable to find the embedded skin LV.

Looking at the TableDesign.ascx, it seems that control is loading other Telerik controls that don't have EnableEmbeddedSkins set to false.  I set about trying to change the dialogs so I could set the Enable EmbeddedSkins to false so it stop throwing the exception.

I've tried using code behind or declaratively setting the ExternalDialogsPath and it never seems to use the modified dialog ascx files.

In the OnLoad event we set the properties of the Rad Editor.

// Code Snippet
this.EnableEmbeddedSkins = false;
this.CssFiles.Add("/_layouts/LearningVillage/Styles/RadControls/EditorContentArea.css");
this.DialogHandlerUrl = SPContext.Current.Site.Url + ((SPContext.Current.Site.Url.EndsWith("/", StringComparison.InvariantCulture)) ? "" : "/") + "_layouts/LearningVillage/Telerik.Web.UI.DialogHandler.aspx";
this.ExternalDialogsPath = SPContext.Current.Site.Url + ((SPContext.Current.Site.Url.EndsWith("/", StringComparison.InvariantCulture)) ? "" : "/") + "_layouts/LearningVillage/EditorDialogs/";
this.Tools.Clear();

//End Code Snippet, below this we set which EditorTools are added to the toolbar.

It seems that setting the ExternalDialogsPath has no effect with the Rad Editor does not effect where the dialogs are being loaded from.

Any suggestions?

[Chad]

On a side note, we are using version 2008.1.515.35

[Lini]

Hi Chad,

What you stumbled upon is a limitation with the current dialog skinning mechanism for the RadEditor and RadSpell controls. When you are using a custom skin for the editor, the editor dialogs will try to render with the Default skin, since they are different documents and thus cannot use the CSS files for the editor skin you have added in the main page.

We have recently fixed this problem by allowing the editor dialogs to have custom skins. You will need to set an editor property with the location of the custom skin CSS file you wish to use in the dialogs. The fix will be available in the official Q2 2008 release of RadControls for ASP.NET AJAX. If you wish to test your SharePoint application now, then please open a formal support ticket and we will send you a hotfix build with instructions.

Kind regards,
Lini
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center