HELP -- lost in the maze of WYSIWYG-API chaos

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

I'm getting close to ripping my hair out. I am trying to install some of the WYSIWYG-API-compatible Drupal modules. I got nicEdit running a while ago, and it works mostly except I've been having problems & want to try one of the others. It is nearly impossible to find the web pages for how to install other editors with WYSIWYG.

What would really help is:

  1. if this community could PLEASE come up with a search term that can be used to search for Drupal modules that are compatible with the WYSIWYG-API. "WYSIWYG" does NOT work. If you search for "tinymce wysiwyg drupal" you get the TinyMCE WYSIWYG Editor module http://drupal.org/project/tinymce which has been superceded by the WYSIWYG API. In addition I can't find anything on moxiecode's website about installing TinyMCE in Drupal.

  2. Please tell makers of WYSIWYG-API compatible modules they shouldn't advertise they're compatible with the WYSIWYG API until they explain how to install their module in Drupal. I need to know what directory to upload into (usually the modules/wysiwyg directory I guess) and what items need to be placed within that directory and which are optional: online storage fees for some site hosting services are not free, and I want to make sure that I know which of the files are instruction and example files that I don't really need to run the module in question.

  3. Please come up with a page on the Drupal website, that is a list of WYSIWYG-API compatible modules so their authors can post information there. If there is such a page, I can't find it.

Until then, I'm just going around in circles...
--Jason

Comments

I think you may be a little

dragonwize's picture

I think you may be a little confused. Those modules are not compatible with the WYSIWYG API module the libraries are compatible. In other words the TinyMCE editor NOT the module works with WYSIWYG API module. To install the editors, download the library of code for the editor's website NOT from Drupal.org modules. Then uncompress the library file into your modules/wysiwyg folder.

Those modules are the old way of implementing an editor in Drupal. WYSIWYG API module is the new way.

Built-in

sun's picture

What dragonwize said.

Just go to admin/settings/wysiwyg/profile in your Drupal site, open the "Installation instructions" fieldset and follow the displayed instructions.

Further documentation about installing and configuring editors is available by following the links below "Further documentation" on the Wysiwyg API project page.

Daniel F. Kudwien
unleashed mind

Daniel F. Kudwien
netzstrategen

Yes, like dragonwize

svendecabooter's picture

Yes, like dragonwize says...

  • You install the WYSIWYG API module in your /sites/all/modules folder.
  • Then you download the editor of your choice from the 3rd party website hosting it (e.g. TinyMCE from http://tinymce.moxiecode.com).
  • You extract the downloaded package for the editor of your choice in the /sites/all/modules/wysiwyg/ folder.
  • Then you go in the Drupal WYSIWYG API module admin to configure everything properly.

That should do the trick :)

--
http://www.svendecabooter.be

I think you may be a little

arghman's picture

I think you may be a little confused.

That was my point! 8( 8( 8( I'm not confused at all.
I understood exactly from the TinyMCE WYSIWYG module home page that it doesn't work with the WYSIWYG API. But if you search for TinyMCE and WYSIWYG and Drupal, that's what you get!

There should be some way to search for modules that are compatible with the WYSIWYG API, and unfortunately a google search for "WYSIWYG" doesn't work because unfortunately a lot of the other Drupal modules that are not compatible with the WYSIWYG API are still WYSIWYG editors.

I still can't figure out where to look for editors that are compatible with the Drupal WYSIWYG API. OK, so nicEdit and TinyMCE are in, what else is out there?

===

re: installing tinyMCE, I'll give it a shot. The .zip file for TinyMCE 3.2.2.3 is confusing; unlike the usual Drupal modules which have a root dir named after the module itself, the TinyMCE zip file has an "examples" and a "jscripts" directory. My guess would be that it's the jscripts/tiny_mce directory that should be copied into /sites/all/modules, but I'm not sure.

Not to be that guy…

choster's picture

…but did you look at the WYSIWYG API module page itself?

Supported editors/plugins

  • Editors: FCKeditor 2.6, jWYSIWYG 0.5, markItUp 1.1.5, NicEdit 0.9.0, TinyMCE 3, TinyMCE 2, Whizzywig 55
    Support for other editors is in the workings. Patches can be found in the issue queue.
  • Plugins: Teaser break, Image Assist

I don't care much for Drupal's native search engine, but that's an issue to bring up with the search developers, not here.

===
For installing TinyMCE, again, the instructions read

Extract the archive and copy its contents into a new folder in the following location:
sites/all/modules/wysiwyg/tinymce."

Not sites/all/modules, but sites/all/modules/wysiwyg/tinymce. The jscripts directory would thus be sites/all/modules/wysiwyg/tinymce/jscripts .

===
You continue to refer to the various third-party wysiwyg packages as "modules"; they are not Drupal modules, and you shouldn't expect them to have anything in common with Drupal modules. They're just files that you load onto your server.

Installation instructions

sun's picture

Again, you should follow the built-in installation instructions:

Daniel F. Kudwien
netzstrategen

DOHWWWW again!

arghman's picture

@sun: I never noticed the installation instructions! (in http://{my site}/admin/settings/wysiwyg/profile ) I am just not used to drupal with its subtle collapsed menus. :( lots of hidden goodies.

thanks!

The WYSIWYG API module page

dragonwize's picture

The WYSIWYG API module page (http://drupal.org/project/wysiwyg) lists all the editors it is currently compatible with:

Supported editors/plugins

* Editors: FCKeditor 2.6, jWYSIWYG 0.5, markItUp 1.1.5, NicEdit 0.9.0, TinyMCE 3, TinyMCE 2, Whizzywig 55

Support for other editors is in the workings. Patches can be found in the issue queue.

DOHWWWW!

arghman's picture

For some reason my attempts to search missed that page.
:embarrassed:

Sorry. :( Thanks for the clarifications.

arghman - I'm with you

tmptye's picture

Guys you all sound soooo smug - wysiwyg api and in particular tinymce are ball breakers, we just can't get em working here, one minute we can see a few editing tools, then they vanish. We've tried all the path options, all the "simple" installation instructions, all the search possibilities - jeez you guys this worked beautifully in previous incarnations, it wasn't broke and they've tried to fix it! And it's rubbish.

er spleen vented, at easy!

If Wysiwyg API does not work

sun's picture

If Wysiwyg API does not work as expected, please

1) Remove all buttons/plugins from your Wysiwyg profile except bold+italic buttons
2) Test whether the editor appears
3) If not, temporarily disable (all) other contrib modules
4) Test again
5) If the editor appears, re-enable other contrib modules step-by-step to see who's guilty.

Daniel F. Kudwien
unleashed mind

Daniel F. Kudwien
netzstrategen

Are you using dev?

choster's picture

The dev version of the module changed the location where WysiwygAPI looks for the scripts; instead of say, /sites/all/modules/wysiwyg/tinymce , it now goes to /sites/all/libraries/tinymce . This change caught me off guard as well, but the instructions at /admin/settings/wysiwyg/profile do reflect the update.

I apologize if my previous post sounded smug, as that was not at all my intent. I do find this module SOOO much more reliable, stable, and easy to configure than the old fckeditor and tinymce standalone modules, though, that I honestly have a hard time understanding situations that lead people to come to the inverse conclusion.

I don't detect any smugness

mt3ch's picture

I don't detect any smugness at all in their replies and I think you are being very unfair. I found the responses the developers gave very clear, helpful and to the point. This brevity may have given the impression of smugness but brevity is useful in such circumstances because it makes it easier to find and grasp the answer (besides the busy schedules of these developers providing a service for free, in addition, to daytime jobs and helping out the many other support requests in this project and other open source they are probably involved in). Please do not be so hasty to judge through your own highly charged emotional filters, or "vent your spleen" before giving consideration to these matters. (Note even the original poster thanked them for their help and apologised to them for not noticing the instructions clearly given on the module homepage and the module settings page which the developers each pointed to several times).

Although experiences may differ, personally, I would like to thank the developers of this module, as a humble Drupal user/admin since some time ago I know that this module was desperately needed by many in past times, myself included, and it has thus far done the job for me perfectly each time. The instructions were easy for me to locate in the most obvious places (not Drupal search which is out of the scope of this project), and the installation process could not have been simpler and clearer to me. Thank you guys, and please do not be discouraged by the negative comments—you may not hear so much from those that are happy with the work you have done, but be assured we exist and are applauding you all the way! :-)

wywinwyg

tmptye's picture

what you want is not what you get... OK joking aside thanks Choster and Sun for pitching it, I've looked at both your suggestions, neither help I'm afraid; I've moved the folders around somewhat experimentally, had unpredictable results with a number of browsers, updated everything, disabled modules, created library folders, switched on just the "bold", even invited a Voodoo priest to shout at it. We just can't make any sense of the install process. References seems to be scattered across drupal.org, with no cohesion... I'm sure I saw somewhere "Just install it as normal" when we all know (now) WYSIWYG API gets to live in sites/all/modules then the editors get to live in sites/all/modules/wysiwyg/ so anything but "normal"

Anyway if this works, and by thunder I shall make it work by the beards of my forefathers, it will be like, so like, better!

Thanks again all.

Holy Beards of the Forefathers

tmptye's picture

God must have switched on the "make WYSIWYG API work" button... don't know what I did:

drupal 6.12 (recently upgraded during this nightmare)
WYSIWYG API 6x 2.0 Alpha
TinyMCE 3.2.4.1

using a mac, Firefox 3, no wait it doesn't work in Safari (no matter)

............

all make sure that it all goes together like this

sites/all/modules/wysiwyg/tinymce

............

best of luck

Working no problem

plebe's picture

but I can't get 3rd party commercial plug-ins to work with wysiwyg module. I can't add the buttons to the toolbar. I found I could edit the fckeditor.inc file in the wysiwyg module, and it seems to accept the settings, but the editor balks: "unknown toolbar item "xxx" "

Any ideas how I can get my plug-ins working with wysiwyg module?

[edit]

...discovered that if you do NOT check any of the buttons/plugins checkboxes under each input filter, wysiwyg module seems to be taking from fckconfig.js, which is great, since now my custom plug-ins work! However, now I can't restrict use to a (different) toolbar per role. If I use the default wysiwyg checkboxes, it seems fckconfig.js is ignored, and so I lose my custom plugins.

Hmm. Anyone know how to restrict a ToolBar set in fckconfig.js to a particular role?

Wysiwyg

Group organizers

Group categories

Group notifications

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