Glad things are beginning to work out for you.
NOTES (No kfm tables):
I don't bother with pre-sets, as I always use the Advanced Manager Enabled as above (making further adjustments, if I have to, in ther .js file), I don't tend have an occasion to reuse any preset I make, that doesn't need the same amount of tweaking in a new site as if I had started from scratch. If you save a preset, it will look for the same stylesheet, and each of my sites uses different style rules.
The Styles don't show up in your Editor area because you have not included the style select list in the toolbar set when you chose your buttons (the group is ['Style','FontFormat','FontName','FontSize'] ). You can select the 'Style' list seperately, without the others in the group. It would be simpler to add it directly into your 'index_messageArea1.js' than go through the wizard, who isn't very.
FCKConfig.ToolbarSets["Custom"] = [ ['Source','Save','Preview'], ['Cut','Copy','Paste','PasteText','PasteWord'], ['Undo','Redo'], ['Bold','Italic','Underline'], ['OrderedList','UnorderedList','Outdent','Indent'], ['JustifyLeft','JustifyCenter','JustifyRight','JustifyFull'], ['Link','Unlink','Anchor'], ['Image','Flash','Table','Rule','SpecialChar'], ['Style', 'FontFormat'], ['TextColor','BGColor'], ['FitWindow']]; /* Toolbar end */
Note the added 'Style', just before 'FontFormat'.
Stylesheet: - Create a new class (i.e. '.mystylesBody'):
font-family: Arial, Helvetica, sans-serif;
(Apply your own attributes).
The XML: - add a node to your xml file:
<Style name="mystylesBody" element="span" >
<Attribute name="class" value="mystylesBody" />
FCKConfig.BodyClass = 'mystylesBody';
The only purpose of this is to ensure that your client will see in the Editor area a true reflection of your body style, and the other styles as applied on top of body styles.
I use an external FTP client to upload all my files, as Dreamweaver is less than useless. I haven't tried uploading the zipped folder, It seems fine to me as it is. I don't think there would be any point in uploading one preset for all your sites, you would have to download it and configure it for each site anyway.
I don't know if any of this will be useful to you, but I have done quite a few iRite then HTMLEditor pages, and this method works best for me! Each time you run the Editor UI, you get new problems. So I don't. Quick and easy!
Editor GUI at all.
Special Bonus Track:
FCKConfig.FormatOutput = false; /* Change to true */
FCKConfig.FormatSource = false; /* Change to true */
This tidies up the html code in the editor area's 'source' view in to more meaningful well-format code (you see what's what). Well worth doing if you are likely to be making changes (adding a class to a div?) in source view.