Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
editor css
#4
It is preferable to have a seperate file, more than likely your stylesheet will have wrappers and classes that are not present in the ckeditor frame.

editor.css is really contentsCss, I have no idea why it was named editor.css
editor.css is what cke loads for its own styles.

regardless

You can just set your own
contentsCss in ckeditor config or GSEDITOROPTIONS

PHP Code:
define('GSEDITOROPTIONS'"contentsCss:'/theme/editor.css'"); 

supposedly you can also pass an array of multiples
eg. ['/1.css', '/2.css']

in 3.3.x contentCss is looked for here
theme/TEMPLATE/editor.css
ckeditor will also look for its own in its folder for contents.css if not set

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.

to summarize

As of now if a theme wants to include a stylesheet to style the wysiwyg editor, then editor.css in your main theme folder needs to exist. (styles/editor.css would probably have been better, its too late now to change that though )

If a user wants to add their own and override this, then they can specify using contentsCss as i mentioned above.
NEW: SA Admin Toolbar Plugin | View All My Plugins
- Shawn A aka Tablatronix
Reply


Messages In This Thread
editor css - by datiswous - 2014-12-17, 20:34:31
RE: editor css - by hameau - 2014-12-17, 21:42:19
RE: editor css - by datiswous - 2014-12-17, 23:07:53
RE: editor css - by shawn_a - 2014-12-18, 00:35:52
RE: editor css - by hameau - 2014-12-18, 02:50:51
RE: editor css - by shawn_a - 2014-12-18, 03:15:35
RE: editor css - by datiswous - 2014-12-18, 07:49:31



Users browsing this thread: 1 Guest(s)