Unless I'm missing something obvious, setting custom classes in settings/wysiwyg/profile/edit doesn't seem to have any effect on the FCKeditor style dropdown (the styles from the default fckstyles.xml are shown instead). As I understand it, even "FCKeditor - WYSIWYG HTML editor" module doesn't allow web configuration of the style dropdown, so it may be that there isn't a practical solution.

I understand that WYSIWYG API support for FCKeditor is a work in progress. However, until CSS class web settings can be made to work, it may be best to remove this field from the profile/edit form and replace it with a link to a handbook page detailing how to override the styles by creating a custom fckstyles.xml file and pointing to it with the FCKConfig.StylesXmlPath property in fckeditor.config.js. This ties in with this patch: #399466: Check theme directory for fckeditor.config.js

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Closed (duplicate)

Marking as duplicate of #331089: Enhance FCKeditor support, Patch for multiline support and #313497: Allow configuration of advanced editor settings

BenK’s picture

BenK commented
Version: 6.x-1.1 » 6.x-2.0
Status: Closed (duplicate) » Active

Hi everyone,

I wanted to re-open this issue because setting custom CSS classes still doesn't work when using FCKEditor with the latest stable version of the WYSIWYG module. Instead, the default classes are still being shown.

I'd love to see this feature working! :-) Anyone else?

BenK’s picture

BenK commented

I've changed the status from "duplicate" to "active" because I believe the threads referenced above don't deal with this custom CSS issue specifically. If I'm wrong about that, feel free to change it back.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Closed (duplicate)

Allowing the CSS classes to be changed will most likely be a part of the other issue. The whole profile edit page needs to change to allow the editor implementations to put any settings there. It's a big change that will be made to 3.x first.

ianski’s picture

ianski commented

Bump – I would also love to see custom CSS classes working with FCKEditor when configured on the settings/wysiwyg/profile/edit page.

sheathe’s picture

sheathe commented

subscribe

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

There's no point in subscribing to this issue. It's marked as a duplicate of #313497: Allow configuration of advanced editor settings which is where discussions on improving support for most editor settings takes place.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Version: 6.x-2.0 » 6.x-2.x-dev

#331089: Enhance FCKeditor support, Patch for multiline support did not resolve this and it remains an issue in current dev.

danielnolde’s picture

danielnolde commented
Title: CSS classes from WYSIWYG Profile form have no effect on FCKeditor » CSS classes from WYSIWYG Profile form have no effect on FCKeditor / CKeditor ...
Status: Closed (duplicate) » Active

hm, after way over a year this BUG is still not even tackled...
And this bug not only happens with FCKeditor but also with CKeditor.

What the others said is true:

This is *no* 'duplicate' issue of some feature-adding-issue (which both issues you mentioned are!), but a clear bug of existing functionality! Mixing up features with bugs doesn't lead nowhere, so please help us to solve this bug.

TwoD or sun, can you point us to where we could start fixing this bug?
I'd love to make a patch, i just need some hint where to start and what to look for...

cheers,

daniel

danielnolde’s picture

danielnolde commented

This bug/issue is more some "sibling" of this CKeditor-related issue describing the same misbehvaiour - and therein, TwoD provided a non-hacking workaround for the problem, tailored for CKeditor but probably translatable to FCKeditor, too:

http://drupal.org/node/746524#comment-3304858

Thanks TwoD for the workaround!

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

danielnolde is correct.

Using the workaround in #746524-20: No Font Styles for CKeditor, replace the setting key with StylesXmlPath and the whole value with a string path pointing to an XML file with your style definitions, instead of the JavaScript file CKEditor uses.

http://docs.cksource.com/FCKeditor_2.x/Developers_Guide/Configuration/St...

The complexity of these definitions are part of what have kept us from using the simple textarea on the profile page. When #313497: Allow configuration of advanced editor settings gets in, I'd like to replace it with a simple textfield and connect that to the option mentioned above so one can set the pah using the GUI. That's why I originally marked this as a duplicate of that issue. Then maybe we could talk about creating the XML file itslef from within Drupal as well.

aaronbauman’s picture

aaronbauman
he/him
commented
Version: 6.x-2.x-dev » 7.x-2.x-dev

Issue persists to 7.x
updating version since other issues are getting closed as dupes on this one.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Postponed (maintainer needs more info)

#746524: No Font Styles for CKeditor has been resolved. I'm not sure what's left for this issue.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

I'm changing this back to 'duplicate' to get it out of the queue, and since it depends on the other issues mentioned above. There have also been changes made related to these settings since this issue was last updated. I'm currently working on removing settings widgets which don not have any effect for some editors and that should also help with the confusion over these settings.