Hi Everyone,

First off - big thanks Lee for updating the CSS layout tutorial and the Red Leaf Skin. I spent a number of hours recently going through some pain in getting DNN 4.4.1, House menu, Doc switching, IE 7 and Red leaf working nicely.

I have some questions regarding the best use of the FckEditor and how to make it WYSIWYG - I'm currently using the FckEditor provider from the dnn site.

1) Editor area css. Setting this to dynamic goes some of the way in making things look WYSIWYG however by default it uses any styling in the body tag/class (which may not have the rules you necessarily want to apply). There are 2 config items FCKConfig.BodyId and FCKConfig.BodyClass that could set which styles come into effect in the editor. Has anyone got this to work?

http://wiki.fckeditor.net/Developer...ngs#BodyId

I seem to remember in the FckEditor tutorial there was the small issue of the (dark) page background colour coming through in the editor box.  Maybe setting the BodyClass item to point to another element/class would stop this from happening.


2) What styles do people populate the style drop down with? I usually put the image on left/right and clear as described in one of the skinning tutorials on this site. I've also tried setting the FckEditor List of available styles option to dynamic. This results in populating the style drop down with every single style in the cascade of style sheets to appear - which is too much for an end user to deal with. . .

3) How do you describe to users how to format content in the editor? It seems pretty easy to get to a point where formatting rules are overlapping eachother with the only way out being to switch to source mode and clean up the tags. The clear formatting button doesn't seem to help much . . .

regards,

Adam.

Hi Adam,

2) I just use a few styles, mainly the image left, right, quotes and code.

If you follow the FCK editor video tutorial it walks you through how to create a styles.XML file -   This is what you need to create.

You add the CSS that you have detailed above into your skin.CSS file and in the styles.XML file you detail the HTML code that is added to the text HTML module when a user selects a style.

In the latest version of the FCK editor you can upload the style.XML file to a folder within your file manager.

Then in the actual FCK editor settings / List of available styles for the editor

Style list generation mode: select URL
Custom XML file: navigate to the styles.xml file that you have previously uploaded
and then apply this to the instance / module / portal whatever you require


3) Yes this can be a problem, so it is best to limit the styles that are available for basic content administrators

Hope this helps, thanks,