[Solved] RadEditor - Custom skinning problems (with problems in LinkManager)

[gerco Koks]

Hello,

I have a problem using custom skinning in RadEditor.
I have tried the solution mentioned in the installation manual delivered with our version (2008.3 1314)
Appearance > Create New Skin
Appearance > DialogsCssFile Property

The editor itself takes the custom skin but the context menu en the <Hyperlink manager> control(s) doesn't.

When I don't use custom skinning the controls are beeing loaded by the Telerik.Web.UI.DialogHandler.aspx but then i have the problem that the resources are not beeing loaded, so i do have the controls but no text.
All the proper .resx files are in the App_globalResources folder.

I have attached 2 screens. The first is an example of the directory structure and the second attachement shows how the linkManager is beeing loaded.

thx.

Gerco

 

[gerco Koks]

We are still working on a solution of the problem described in the opening post. We have decided not to use custom skinning so we are focusing on the problem of the missing text ( resources can not be found??? ) in the hyperlinkManager (and all other dialogs).
We have created a test project with the radeditor out of the box and are able to reproduce this problem by using the following settings:

        <telerik:RadEditor ID="RadEditor1" runat="server"
            Width="875px" Height="200px"
            ShowSubmitCancelButtons="false"
            EnableDocking="false"
            EnableClientSerialize="false"
            CacheLocalization="true"
            ToolbarMode="Default"
            Skin="Office2007"
            Editable="true"
            RadControlsDir="~/RadEditor"
           LocalizationPath="~/<our custom resource folder for the radeditor>"
            ExternalDialogsPath="~/EditorDialogs">
        </telerik:RadEditor>

Notice the LocalizationPath property.
When this property is set the HyperlinkManager (and all other dialogs) has no text (see screenshot).

Setting the property LocalizationPath to App_GlobalResources is not an option because we use a DBResourceFactory in our application for all our other resources.

I hope you can help.

[Rumen]

Hi Gerco,

Straight to the questions:
1) Skin problem: Please skin the editor and its dialogs by following the instructions in these articles:

Registering an external skin of RadEditor
and
RadEditor Q3 2008 Skins Available for Download.

To style the dialog you should set the DialogsCssFile property to point to a css file containing reference to the following classes:
@import url('../ToolBar.css');
@import url('../FormDecorator.css');
@import url('../TabStrip.css');
@import url('../Editor.css');
@import url('../TreeView.css');
@import url('../Splitter.css');
@import url('../Slider.css');
@import url('../Upload.css');
@import url('../Window.css');
@import url('../Grid.css');
@import url('../Widgets.css');
@import url('../FileExplorer.css');
@import url('../Menu.css');

@import url("Ajax.Vista.css");
@import url("ColorPicker.Vista.css");
@import url("ComboBox.Vista.css");
@import url("Dock.Vista.css");
@import url("FormDecorator.Vista.css");
@import url("Grid.Vista.css");
@import url("Input.Vista.css");
@import url("Menu.Vista.css");
@import url("PanelBar.Vista.css");
@import url("Rotator.Vista.css");
@import url("Slider.Vista.css");
@import url("Spell.Vista.css");
@import url("Splitter.Vista.css");
@import url("TabStrip.Vista.css");
@import url("ToolBar.Vista.css");
@import url("TreeView.Vista.css");
@import url("Upload.Vista.css");
@import url("Window.Vista.css");
@import url("Widgets.Vista.css");

2) If you use only the English localization then it is not needed to set the LocalizationPath property and copy the resx files in the web project. The English localization files are embedded in the Telerik.Web.UI.dll and the editor will automatically load them if the App_GlobalResources is not set.

If you use non English localization then make sure that the English resx files are also copied to the localization folder to which the LocalizationPath property points.
Please, also see the following live example: Localization.

If you experience any problems, open a support ticket and send a fully working project that demonstrates them.

Best regards,
Rumen
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.