If you use the dnnwerk provider - you need to setup an editor.css file in your skin folder - with the styles you want rendered in the radeditor.

Then in the dnnwork config util set the cssfile to /editor.css - this will tell radeditor to use the editor.css file explicitly - it will also populate the stylesheet drop down properly as well.

Oh and as a tip dont just copy your skin.css file - it works better if you cull out the style elements that are not relevant - that is things like the menu styles and contentpane type layout elements.

The thing to understand about the radeditor is that it uses and IFRAME wrapper to display itself
 - which does not inherit any of the multiple .css files that can be buried on a dnn page - from default.css to portal.css to skin.css to container.css

In the default version if i recall only skin.css gets passed in - but not the default.css or portal.css or container.css or any of the combination of skinwidget type scaler .css files in some skins - though never been a 100% sure on this - it eventually all got rather messy.

We gave up on all that messing and moved to using editor.css with ALL the styles that area need for font look and fell and the dnnwerk provider - it works perfectly - showing exactly the same colors, fonts, spacings and styles used when the site renders.  Our clients love it

 Westa

Hi Roger,

One of the reasons we first moved to the dnnwerk provider was because of a site we had that was light text on a dark background.

Basically the thing you need to understand is that a finished dnn layout can be a combination of a lot of different .css files.

container.css
containername.css
skin.css
skinname.css
portal.css
default.css

So for starters what we do with all our sites is normalize the css into one single skin.css as much as possible.
This can also bring some noticeable performance boosts as well.

Note - this is not always possible for containers depending on your container design

We then take this skin.css file and remove all the elements that are not needed for content layout - these are things like the MENU and ControlPanel and contentPane style layout definitions.

This resulting stripped down style list is then copied into an editor.css file and placed in that skins folder - in the dnnwerk config we then set /editor.css as the rad editor stylesheet.

There is nothing magical about the editor.css file - to get wysiwyg however - it MUST contain all the style elements that are effecting the final look of your dnn site ... the rad editor is running inside an IFRAME and as such does NOT inherit any of the styles that exist in your dnn site ...   if  you dont use the editor.css type functionality - then rad will try and guess by referencing if I recall the skin.css file alone - but without any of the core defaults for stuff from portal and default and skinname as well.  -   oh and specifically not as a rule the background color markup for the dark background page - which is often in peoples skins NOT defined in .body but instead as a color at the container level.

In editor.css - you simply define it in the body style markup - and it becomes the backcolor for that editor layout.

Westa