Hmmm - just had a chance to look at this on one of our sites - it seems there may be a bug in the radeditor that is not properly pointing to the editor.css file - sure it was working when I looked at this last.

It may be worth flagging this as a possible bug.

 Westa

FYI I've traced this down to an issue with the pop-ups introduced in DotNetNuke 6.0. For some reason when the module is popped up it does not inject the cssFiles variable that the telerik editor uses to control stylesheets (I'm speculating that it doesn't because it's not a full page but rather a popup). I've logged an issue for this in our bugtracker so we can fix it for a future release (http://support.dotnetnuke.com/issue/V...) . Note: i also associated that with an issue related to module.css which seems a related issue i.e. pop-ups loading skins differently from discrete pages.

For now, you can work around this by disabling popups for the html editor. To do so, log in as host and go to host->extensions, click the edit icon beside the html module, expand out the "module definitions" section, click the edit icon beside the "edit" control and then uncheck "supports popups". This will revert it to the pre dnn 6.0 behaviour where an edit goes to a new page and the editor.css will load correctly. Please note, the correct path is the root of the active skin i.e. in my install using the DarkKnight skin it's Portals\_default\Skins\DarkKnight\editor.css

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US