TinyMCE no showing everywhere

Events happening in the community are now at Drupal community events on www.drupal.org.
Inv1sus's picture

Hello everybody!

I installed the WYSIWYG modul, then i chose the TinyMCE, because i like it. Very friendly, simple, ect.
But i have a problem with WYSIWYG module, because it doesnt work everywhere, example: Footer message at Site configuration > Site information or Contact form > Additional Information. I dunno, that just i have this problem or its normal. How can i turn it on at every textarea? Pls help me :(

Sry for my english, but on my country's drupal pages nobody answered! :(

Comments

Not a new issue, but here is my two cents

michael_lessard_micles.biz's picture

Greetings,

In my case, I had similar problems for the following reasons :

:: TEMPLATE MISSING THE CLOSURE
A common reason is a code missing at the end of page.tpl.php in your current theme.

// make sure echo $closure; exist somewhere at the end of page.tpl.php, before the BODY tag.
<?php
echo $closure;
?>


</BODY>

:: JQUERY and javascript failures :
In Drupal 5.x, my jquery .js was not in the proper folder (Drupal 6.x automatically puts the updated .js for jquery in the right place).

:: LANGUAGE
In any Drupal and WYSIWYG version : if you select a non-English language, the TinyMCE will not appear unless you install the languages files in the libraries/tinymce/jscripts/tiny_mce/... (all the translation files have to be in the proper folder - You can download the language package from the TinyMCE official site). You can easily check this theory by making sure the language is English and see if it becomes visible.

nb: deactivate Drupal javascript compression of course and jquery compression also (i.e. just for these test; you can turn them all after normally).

Editor not displaying

shimshun's picture

Many thanks Michael for this; i would never have found this out on my own without many hours of head scratching and some luck
I was missing the closure at the end of my page template as i had a custom template
The need for it seems a bit odd: any ideas why?

This is normal

twod's picture

Wysiwyg module ties each editor profile to an input format (text format in D7) to make sure that you always get the right editor configuration when switching between formats.
This means the editor will automatically be available wherever there is an input format selector (it doesn't need to be visible, like when there is only one format active).

Drupal does not use input/text formats when rendering all fields, for example those you mentioned above. This is often the case when a field can use nearly all HTML tags, but still needs XSS protection etc. The contents of those fields are not rendered using check_markup(). Instead, they use something like admin_filter_xss() which doesn't run the filters associated with an input format so you could not use modules like Image Assist or Wysiwyg Image upload anyway, the "filtertags" they use would not be turned to HTML.
So on these fields, which are mostly admins-eyes-only, there is no format selector and no WYSWYG editor.

Thanx

Inv1sus's picture

Thanks the answers. Finally i decided some days ago, that i try out fckeditor and i uninstalled the WYSIWYG modul. Fckeditor now works everywhere and i can set, what i want to convert.
BTW, u are right TwoD. I am new in drupal things, but now i could make better solution with WSYIWYG in safe. I learned some things. There are so many way to do extra things with this great cms ^^ without break the standard drupal code. Just i need time.

Sry for my english, i hope u understand what i wanted to tell. :)

Wysiwyg

Group organizers

Group categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: