Okay - same old story here. Have latest module, have latest Moxie code.
I've installed it twice, based on two different installation instructions that I found - I still have no editor.
Everything on the Drupal.org site points back to Moxie for install instructions, but that site just links back here - endless loop. No help.
Will anyone who has this working PLEASE post the steps you took to get it installed? I've seen some mention of the mysterious "two lines of code" - but I have no idea what they are or where to put them.
No one should have to reference 3 different sources to get install instructions.
Comments
Comment #1
kreynen commentedThere should only be 2 places to look for documentation. The TinyMCE module at Drupal.org and the TinyMCE toolbar at Moxiecode.
What are the URLs of pages pointing to Moxie? I'd like to get those changed back. If you have a URL for this "two lines of code" I'd like to take a look at that as well?
I can't really help with the install since I'm following the instructions included with the module. The basics are download the module. Download the TinyMCE toolbar. Put the toolbar into the module folder so it looks like /modules/tinymce/tinymce/. Give a role access to the tinymce. Create a profile in the TinyMCE admin utilities.
If that is what you are doing and it is not working, you are going to have to be more specific about your problem. Does the TinyMCE show up in you browser on the TinyMCE demo site? Do you get a Javascript error when pages are loaded?
Comment #2
koda commentedI agree with this comment
the instruction specify a "TWO STEP PROCESS"
but after fighting with installation, I can underline that:
the give only the second step.
The best way was to provide the tinymce folder ready to run.
So if you follow this instructions it will work:
1 first step (wich is not given in previous instructions)
-dowload the tinymce compressed module from drupal site
-exctract it
-copy it in /module
-after operation you should hae that : "/module/tinymce"
2 second step (witch was given as first step by previous instructions)
-dowload the compressed tinymce folder
-extract it in the previous tinymce folder
-after operation you have that :"/module/tinymce/tinymce"
precision the two folder are different the first you have downloaded contain the module interface for drupal
the second one contain the js code from maxiecode
Drupal is a hight quality cms, because huge effort have been done for hight quality documentation, code and support.
Please, for users, and drupal communauty, follow the drupal philosophy and change the instruction set to install tinymce.o give
The best way where to give tinymce .gz and .zip ready to be installed, and to give a link to imce.
best regard damien
Comment #3
ADMarshall commentedI cannot agree or disagree with the last comment. It is so poorly written and used such imprecise and ambiguous choices for wording that I would guess it it virtually incomprehensible for all but those with long experience in communicating with victims of autism.
I'm amazed at how difficult it has been to get clear, simple instructions for installing the TinyMCE module from Drupal. In fact, i've worked with Drupal for three years already and now absolutely dread having to get help from this site.
Comment #4
bacchus101 commentedI totally agree. The "instructions" in the post above are so ridiculously nonsensical, I just started laughing when I attemtped to read them!
I have to install tinyMCE every few months for one reason or another another and it is by far the most cryptic module in the Drupal universe. I usually spend 3-4 hours surfing around the net to find the "secret" to installing the latest version.
It reminds me of linux in the early days when getting something to work involved a treasure hunt.......
Comment #5
kreynen commentedI really don't understand what is so complicated about downloading the module. Downloading the TinyMCE from Moxiecode. Expanding both, putting the Moxiecode TinyMCE into the TinyMCE module folder, and putting the whole thing into your modules directory?
I'm probably getting close to having installed this a hundred times and I've never had an issue. If you think you can write clearer instructions, PLEASE DO! If not, save the snipes for your personal blog.
Comment #6
AdrianB commentedI agree with kreynen. I'm still new to Drupal and so far I've launced two sites with TinyMCE running just fine. There was some trouble in the "dark ages" of the module after the switch from 4.7 to 5.x, but when things got sorted out it really wasn't that difficult.
That being said it's a little more complicated than the usual module installation. First there is this downloading of external code from Moxiecode (and the langauge files from Moxiecode if you're not using English). And then there is this whole thing with giving the right user role access and creating a compatible input filter. There's a lot of steps and from what I've read in the issues here a lot of people screw it up somewhere on the way.
When I was using one of my WordPress installations the other day it struck me that from a user perspective they really outshines Drupal on the wysiwyg editor issue. It basically works like this:
1) Install WordPress (which is a breeze).
2) Start posting using the built in and activated version of TinyMCE that Just Works™.
WordPress has adopted TinyMCE as their wysiwyg editor of choice and made it a core part, a very good move IMO. I doubt that will happen with Drupal. Especially since some core Drupal developers feel like this about wysiwyg editors:
Comment #7
kreynen commentedDries cited better file management as one of the goals of the Drupal community at OSCMS. I honestly believe that TinyMCE/IMCE is a much better workflow than having to add images before you can use them with the Image module.
As far as including the Moxicode releases with the module, this is a licensing issue. Moxiecode releases everything under LGPL. Everything uploaded to Drupal's CVS automagically gets a GPL (version 2?) license attached.
I do not have permission to change the licensing of Moxiecode's work. Jeff Eaton has a pretty good summary of Drupal and GPL where he uses TinyMCE as an example of a module that connects GPL code to non GPL code.
Now what I think I could do is host versions of the module that include TinyMCE on a different site as long as the module code itself is available.
Comment #8
AdrianB commentedOk, so it is a license issue. I first thought it was (but I never searched to find the answer) but then I thought about WP using it and get away with it. I must admitt I'm only vaguely aware of the differences in licensing. (I understand the discussion about Drupal-id's TinyMCE Plus adding the Moxiecode code better now.)
I totally agree about the pros of using the TinyMCE/IMCE way of adding images, it seems natural, altough it would be even better if it was possible to reduce the number of steps and popups even further.