Download
2014-12-18, 02:50:51
Thanks for the explanation, Shawn. I never got any further than my quick-fix. Generally, CKE just ignores anything it doesn't understand, so I left it at that. At least it avoids the need to maintain two files.
What's wrong with 'editor.css'? At least the name says what it styles. 'content.css' is less specific, imo.
It's like a link in Windows (in this case), so it appears as a file to the system, but it references another file. The link goes in the same folder as template.php, but it points to the real file in, e.g., the styles folder. You can certainly make the symlink if you have shell access to the server and may be able to do it from the hosting control panel.
However, see Shawn's explanation for more robust ways of styling the editor window.
(2014-12-18, 00:35:52)shawn_a Wrote: In 3.4 I might add an additional theme override in themes/editor.css
and probably change it to contents.css, so its not so confusing in the future.
What's wrong with 'editor.css'? At least the name says what it styles. 'content.css' is less specific, imo.
(2014-12-17, 23:07:53)datiswous Wrote:(2014-12-17, 21:42:19)hameau Wrote: It isn't necessary to have a separate file: you can use a symlink to the theme's css file.Sorry, how do you do that? This is new for me.
It's like a link in Windows (in this case), so it appears as a file to the system, but it references another file. The link goes in the same folder as template.php, but it points to the real file in, e.g., the styles folder. You can certainly make the symlink if you have shell access to the server and may be able to do it from the hosting control panel.
However, see Shawn's explanation for more robust ways of styling the editor window.
--
Nick.
Nick.
