I am one of those strange people that wants the editor in the signature box in the edit account pages :)

After getting everything set up and running (easily, though it took a little bit of looking to find where everything was as it wasn't where I was used to it being, so nice work on that front ;) everything seemed to just work and I am reasonably certain I had the editor in the signature field to begin with. Then I went and attempted to get IMCE happening and it stopped appearing (assuming it was ever there to begin with and I'm not just remembering incorrectly).

Complete uninstall of both modules and reinstall of WYSIWYG API with TinyMCE did nothing. I thought to try the dev version (was using the stable 6-0.5 previously), which also hasn't helped. I used some code from my D5 template.php which is how I got it to show up in there in the days before WYSIWYG API, no go.

So is there anything specific I need to do to get the editor to stick into the signature field or is there just something ridiculously obvious that I've managed to overlook?

Using Drupal 6.9 and looking with FF3.0.5 and Safari 3.2.1 if that helps.

Thanks :)


ryivhnn’s picture

Okay so it's an input filter thing. So I guess I change it to can someone tell me how to enable the editor on the fields that don't have input filters available? My users get freaked out when they have to edit their signatures in html/bbcode and of course they all want tickers and photos and stuff in their sigs, and while the site admin have html skills they'd much prefer the wysiwyg when editing the mission statements and other front page associated things :)


sun’s picture

Title: Editor for signature box? » Add module to fix missing input formats in Drupal core
Version: 6.x-1.x-dev » 6.x-2.x-dev
Component: Editor - TinyMCE » Code
Category: support » feature

Wysiwyg API depends on an input format selector for each form element to work. To solve this issue, we need to add a separate module to the package, which extends most of the forms in Drupal core with an input format selector, stores those values, and uses them to render the content on output (using template preprocess functions).

On a second thought, I'd like to know from dragonwize whether this would better suit into the Better Formats module. (I'd guess so)

sun’s picture

Gábor compiled a list for that already: http://groups.drupal.org/node/9072

dragonwize’s picture

The feature would definately fit under the better formats scope. I would probably make it a sub-module though so it would be an option because as Gabor notes, there is some funny stuff going on under the hood with some of the fields.

sun’s picture

Project: Wysiwyg » Better Formats
Version: 6.x-2.x-dev » 6.x-1.0-beta6

Great! Moving over to Better Formats. I'd be very interested in this functionality - in particular, because we could probably use most of the gained knowledge for a patch for D7.

btw, also applying as co-maintainer for Better Formats :) If you want me, could we agree on http://drupal.org/node/363367 ?

ryivhnn’s picture

Obviously I'd be interested in the functionality too :) Sorry I lack the brains to acquisition the coding skills to offer more practical help :( But people like you guys make me terribly, terribly happy :)

And I have Better Formats as well so am quite happy to attempt to break things when you have time to work on it :)


dragonwize’s picture

Status: Active » Postponed

Marking as postponed until work actually begins on this feature.

jimmb’s picture


A big selling point of Drupal is allowing clients to have rich-text editor/WSYIWYG capability as much as possible. Hopefully this will happen in the not-too-distant future!


Liam McDermott’s picture

Hope no-one minds me spamming my own module here, but I stumbled across this issue when adding support for WYSIWYG signature editing to Signatures for Forums. If you need this functionality and don't mind helping test out some dev code, go and grab the latest 6.x-1.x-dev version and try it out! Note: it doesn't just work with forums.

*** EDIT ***
If you do find any bugs, please report them here, not in this topic. ;)

igorik’s picture


Is there any progress with this topic?
I really would like to use wysiwyg editor but I can't, because I lost wysiwyg options for private message textarea, guestbook textarea, can't set simplyfied wysiwyg for comments etc. Everything this works for me using fckeditor module, but I would like to use WYSIWYG editor.


ryivhnn’s picture

#10 - the module linked in #9 gets it back. Not sure when the module devs for Better Formats will hve time to work on it or if it matters if Signature for Forums can do it.

igorik’s picture

maybe this could be marked as a duplicate of http://drupal.org/node/350696 ?

dragonwize’s picture


No, this is a seperate issue from that. This issue deals with Drupal core fields like mission statement, footer message, etc (more listed here: http://groups.drupal.org/node/9072). These fields do not have the ability to choose an input format at all they are just processed with filter_xss_admin instead. This issue is to give these fields the power of input formats.

Yas375’s picture


BayerMeister’s picture


Danny Englander’s picture


liquidcms’s picture

would like to start using wysiwyg module as i have converted modules like Autosave to D6 specifically for use with W - but.. on most of my sites i still end up using FCK module as i don't know how else to have control on which fields get editor applied.

will need to try out BF a bit more to see how much effort to get it control this (FCK's approach of listing field ids seems so much more straightforward right now).

since many fields also don't have input formats... fck winning there as well.. but subscribing here hoping to see a solution.

i agree W approach to providing generic module wrapper makes complete sense.. just hope it catches up to the modules it hopes to replace.

dragonwize’s picture

Issue summary: View changes
Status: Postponed » Closed (won't fix)

6.x is now unsupported.