Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Definining a custom style sheet for CKEditor doesn't work; inspecting the output the standard "kama" skins in the site-wide library are still used regardless of "CSS Path" value in the profile.
Comments
Comment #1
TwoD"CSS Path" setting has nothing to do with which skin is used. It is just a comma separated list of stylesheets which will be split into an array and set to CKEditor's contentsCss option, which is used to inject stylesheets into the editing area. (This is when "Define CSS" is selected, otherwise Wysiwyg sets the option to the output of wysiwyg_get_css() or nothing at all.)
The editors may still inject its own stylesheets before the ones defined under "CSS Path" when the "Define CSS" option is selected.
Could you please elaborate on the issue you are having?
Comment #2
jmbarlow CreditAttribution: jmbarlow commentedIn that case it's a either a chair-keyboard interface problem or a documentation problem.
Looking at the profile configuration page, in the CSS section there is a drop-down "Editor CSS" which is described as "Defines the CSS to be used in the editor area" which, if set to "Define CSS", applies a comma separated list of stylesheets.
My goal was to insert breaks into the toolbar so it displayed over multiple lines and in less than 600px, which is easy enough to do by changing the CSS on combo-box elements from inline to block display. I can do it by editing the stylesheet in the library (Line 10 if anyone's interested), but I thought this UI settings was designed to override the supplied stylesheet
Comment #3
TwoDYes, they are designed to allow you to inject your Drupal theme's stylesheets into the editing area of the editors - as in where the edited contents lives - for a better WYSIWYG experience.
However, your theme styles will need some modifications to work the same in the editor as on your rendered pages, as the editor can obviously not know about all the elements wrapping a rendered node/comment and just wraps edited content in a body tag. For these reasons, the other options in that list have been added as well.
The option to only use the editor's default stylesheets could be useful when in-editor looks aren't that important, and the custom files option is for getting more flexibility and/or not expose in-editor styles with your rendered contents.
CKEditor's toolbar styling can be overridden in your theme's stylesheets using styles rule more specific than the ones used by the editor.
Comment #4
jmbarlow CreditAttribution: jmbarlow commented