Hi guys,

I was wondering if you could possibly accept to add the '#wysiwyg' entry to your textareas so that way I don't have to do it each time I upgrade. Plus, that way, it would make sure that people don't get tags in places where they should not have them.

For example, the description should never include HTML (although I've seen people doing so, it is wrong!)

      $form['dc.description']['value'] = array(
        '#type' => 'textarea',
        '#title' => t('Description'),
        '#description' => t('Enter a description. Limit your description to about 20 words, with a maximum of %count characters. It should not contain any HTML tags or other formatting.', array('%count' => variable_get('nodewords_max_size', 350))),
        '#default_value' => empty($content['value']) ? (!empty($options['default']['dc.description']['value']) ? $options['default']['dc.description']['value'] : '') : $content['value'],
        '#cols' => 60,
        '#rows' => 6,
        '#wysiwyg' => FALSE,            // Add this one entry to all textarea that should never get HTML
      );

If you would like to have a patch, let me know.

Thank you!
Alexis

Comments

avpaderno’s picture

Title: Add '#wysiwyg' => FALSE to textarea... » Add '#wysiwyg' => FALSE to textareas
Status: Active » Fixed

HTML tags are stripped from the meta tags content; avoiding that the textarea form fields used by the module are replaced by a WYSIWYG editor should make more evident to users that HTML tags should not be put into meta tags content.

I added the attribute to all the textareas of the modules, including the one that should contain the content of label.rdf sent by ICRA.

AlexisWilke’s picture

kiamlaluno,

Thank you! Some editors may not support the option (yet), but FCKeditor does. This is great! 8-)

Alexis

Status: Fixed » Closed (fixed)

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