This project is read-only.
Working with the provider is fairly easy. First install the package as you would do with any other module. Then place the RadEditor Config module on a tab that only you have access to (the config module will only work for host users) and start configuring. That easy!

Enable the editor provider

On the top of the module view you will see a dropdownlist that shows all providers that are already installed plus the dnnWerk.RadEditorProvider. select the dnnWerk.RadEditorProvider from the dropdown list and click on Enable this Editor. This will update your web.config (make sure you have a backup!) and enable the editor. As soon as the dnnWerk.RadEditorProvider is enabled, the config form will become visible to enable you to manage your configuration.


Working with configurations

If you want to create a new configuration, select an existing configuration as the base for your new configuration first. Then click on Copy Selected, select for who / what portal / what page the configuration is supposed to be and click on Create at the bottom of the form. The new configuration will appear in the tree on the left hand side and can be now be edited from there.


XML? What's that?

While the basic configuration is done through a regular form the toolbars are configured by editing the xml file directly. If anyone is interested in building a UI for editing the toolsfile xml file, let me know :-)

And what to put in the configform?

All fields in the config form are simple textboxes. Currently no checks are done if you put in invalid value in one of the form fields. If you put in something invalid, let's say "/Images" in the ImagesPath textbox and there is no "images" folder in portal directory, the editor file dialog will not load. While this is a very lazy approach (I know) the good thing about it is that will have to go to the filemanager first and setup a directory with the approriat permissions.

t.b.c. ...

Last edited Aug 25, 2010 at 6:01 PM by proeder, version 3


No comments yet.