Hi,
As the title suggests, in my fckconfig.js file I've set the following properties as such :
The CSS file is as follows:
Notice that the latter two styles were created to see if, for instance, my custom style code that is made in the WYSIWYG editor will show the styles as I choose them. They do not, probably by design (?).
More importantly, however, when I test the page containing the editor in a browser, the #FckEditor styles are not applied (the page background is white and the text is black, which is the default). Further, if I attach the CSS file to the document manually in its header, the background of the editor will be the same color as the background of the entire page, but that's the only thing that changes (the fonts continue to be black, so the background of the editor must be transparent for some reason).
This is an excellent tool (kudos to the developers). But if I may voice a minor complaint, the documentation has been inadequate for troubleshooting purposes, and, in particular, configuration of the editor has been very counterintuitive. Is there any way to see what your styles look like in the WYSIWYG editor, such as if I change "Styles" in the drop down box? OR does this only affect the source code, and the display remains the same?
Thank you in advance for your help.
-Brandon
As the title suggests, in my fckconfig.js file I've set the following properties as such :
... FCKConfig.EditorAreaCSS = FCKConfig.BasePath + '../../css/FckEditor.css'; ... FCKConfig.BodyId = 'FckEditor' ; FCKConfig.BodyClass = 'FckEditor' ; ...
The CSS file is as follows:
body { background-color: #6E5E39; } /* Body background outside of editor */ #FckEditor { background-color: #6E5E39; } /* Body background inside of editor */ #FckEditor span /* Font style and color on anything with FckEditor ID name */ { font-family: "Palatino Linotype", Palatino, Serif; color: #EAE8E2; text-decoration: none; } span.body_content /* Font style and color on anything without FckEditor ID name */ { font-family: "Palatino Linotype", Palatino, Serif; text-decoration: none; color: #EAE8E2; } span.h2 /* Font style and color on anything without FckEditor ID name */ { color: #EAE8E2; font-family: "Palatino Linotype", Palatino, Serif; font-weight: lighter; font-size: 1.3em; }
Notice that the latter two styles were created to see if, for instance, my custom style code that is made in the WYSIWYG editor will show the styles as I choose them. They do not, probably by design (?).
More importantly, however, when I test the page containing the editor in a browser, the #FckEditor styles are not applied (the page background is white and the text is black, which is the default). Further, if I attach the CSS file to the document manually in its header, the background of the editor will be the same color as the background of the entire page, but that's the only thing that changes (the fonts continue to be black, so the background of the editor must be transparent for some reason).
This is an excellent tool (kudos to the developers). But if I may voice a minor complaint, the documentation has been inadequate for troubleshooting purposes, and, in particular, configuration of the editor has been very counterintuitive. Is there any way to see what your styles look like in the WYSIWYG editor, such as if I change "Styles" in the drop down box? OR does this only affect the source code, and the display remains the same?
Thank you in advance for your help.
-Brandon
Re: EditorAreaCSS property doesn't work
I actually had a hard time when I tried to change the styles of the editor using some code but I know the new tool for 2.5, showBlockQuotes, or something like that, actually manages to do that, you may want to look at that code. I don't understand why the EditorAreaCSS isn't working but are you sure the path is right, I believe the BasePath points to the editor/ directory (not trying to insult you or anything, it's just a mistake I've made in the past). If not I have a thread on 'css in editing area' (http://www.fckeditor.net/forums/viewtopic.php?f=6&t=7195) if you want to check that out. Good luck