CiviCRM Community Forums (archive)

It would be helpful for the styles presented in the HTML editor to be WYSIWYG.

Cases include ...

• CMS front-end screens: When event info, event registration, and contribution pages are presented to the end-user, the CSS used from a number of sources: firstly the CMS template CSS, then CiviCRM's CMS frontend CSS, then civicrm.css (or custom CSS if specified) and finally the CiviCRM theme CSS. It would be useful to specify key styles to be applied to editor content and to be used in the drop-down style selections.
• CiviMail: an organisation is likely to set the mail header for CiviMail to include CSS to style the HTML. It would be useful to specify key styles to be applied to editor content and to be used in the drop-down style selections.

I suggest that 2 new parameters are added which act very much like customCSSURL on civicrm/admin/setting/url:

• editorFrontEndCSSURL: URL of the CSS used when editing front-end content
• editorCiviMailCSSURL: URL of the CSS used when editing CiviMail content

Of course, organisations will often want their email and web appearance to match, so perhaps a single parameter will suffice.

(Note 1: The TinyMCE editor is bundled with CiviCRM and used for editing text fields. TinyMCE takes a parameter content_css which is a comma-separated list of CSS files applied to the editor content. The FCKeditor parameter is FCKConfig.EditorAreaCSS.)

(Note 2: The code in packages/HTML/Quickform/tinymce.php and packages/HTML/Quickform/fckeditor.php looks like it might be difficult to parameterise to behave differently for front-end pages versus CiviMail. Perhaps a single parameter editorCSSURL will suffice.)

Ken