Hi there,

Whenever you create a textarea that is not to receive HTML code, you should mark it as not wysiwyg. That way, I don't have to do a special setup again and again for each website I install.

  ...
  '#type' => 'textarea',
  '#wysiwyg' => FALSE,
  ...

Thank you.
Alexis

CommentFileSizeAuthor
#1 addthis-wysiwyg-6.x.patch1.26 KBAlexisWilke
addthis-wysiwyg-6.x.patch1.26 KBAlexisWilke

Comments

AlexisWilke’s picture

AlexisWilke commented
StatusFileSize
new addthis-wysiwyg-6.x.patch1.26 KB

Sorry, wrong boolean value in the previous patch! 8-}

vesapalmu’s picture

vesapalmu commented
Status: Needs review » Postponed (maintainer needs more info)

This patch has to do with sites that have all textareas defined as WYSIWYG? Is this a real problem in many sites? I have only seen WYSIWYG used in very well specified textareas so far.

AlexisWilke’s picture

AlexisWilke commented

It may only be specific to the FCKeditor and CKEditor. It's not for the WYSIWYG module.

By default, the FCKeditor will transform all textareas except for those marked as not a good choice in the FCKeditor settings. The problem is that the FCKeditor only knows the Core textareas and a few major 3rd party modules. For the rest, they don't define any default. This can be "fixed" by adding the '#wysiwyg' flag to FALSE to prevent FCKeditor on that box.

I do that in all the 3rd party modules I use, and when the author accept to check it in, that's great because that way I don't have to do it again and again at each upgrade.

FYI, there's only ~92,000 users of the FCKeditor and CKEditor... so maybe you can ignore my patch.

Thank you.
Alexis Wilke

vesapalmu’s picture

vesapalmu commented
Status: Postponed (maintainer needs more info) » Fixed

Oh, so it was a (F)CKeditor issue. Thanks for letting me know. The patch is now included in D6 2.x dev.

Please test the latest version. It includes many small patches and shoud be released soon.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.