rich text editor link does not work

The code is there, which means the module is probably installed OK.

Is it possible to get an error message after you have clicked the toggle? (Tools - Error console.)

Steve

sure, here it is:

Error: tinyMCE is not defined
Source File: http://localhost/?q=node/3/edit
Line: 65

OK - it's worth trying this.

In admin/settings/tinytinymce look at the advanced mode init script. Near the end is a line:

I think the use of the inline comment may be breaking the script in your version of Firefox. So I suggest that you remove the entire line.

If that doesn't work could you post the HTML source code for one of your pages where the editor should be (but isn't working).

Steve

Thanks for the suggestion, but no, it didn't change the error message (I took out the line and ran updates before I tried just in case)

Hi,
I am not sure if this update will help eliminate possibilities but I uploaded my site to a hosting service - from my windows xp to a linux, and also upgraded my firefox to 2.0.0.19.

Neither action however helped activating the rich text editor link and the error message remains: Error: tinyMCE is not defined
Source File: http://localhost/?q=node/15/edit
Line: 66

I do need to go live so do you recommend giving up and installing another editor? If so, which one?

thanks

I might be able to see what's happening if you post the source code of one of the offending pages:
- In your browser, view source
- save the file to your desktop
- add a post to this issue attaching the source file

sure, thanks very much. I had to zip it since the Drupal forum does not accept attachments with this kind of extension.

Here it is:

I notice that the init script still contains a comment, marked by //

I suggested in post #3 that you removed this comment as I wondered whether all browsers would accept the comment at that location. Can you try this again, removing the commented line. Afterwards, you will probably need to clear the Drupal cache.

You also say that you uploaded to a hosted service. Would it be possible for me to see the hosted pages (you would need to give me access to the editor)

Steve

Hi Steve,
Thanks very much for your help. Since getting rid of the comment did not solve the problem I put it back in, but I tried taking it out again (and flushed the cache) on the hosting service and the result was identical, (although on the host the message talks about line 45). I also tried doing it from another computer, in case the problem was in the browser setting, but no joy here either.

I would not mind allowing you to see the pages but the problem is that the account isn't mine. We are kindly hosted by another NGO and that's their account. In case the same page from the hosting service would be of any help, I am attaching it here:

Thanks very much again.

One other thing I can think of - some people have reported problems downloading tinymce from Moxiecode (ftp client needs to be in binary mode) it might be worth trying that. The reason I suggest this is that everything looks OK on the HTML you showed me but the error reports that the tinymce object does not exist.

As a last resort I have zipped up the tinytinymce directory that works on my local machine and which I have copied to several sites - you can download it from http://stevelockwood.net/files/tinytinymce.zip. If that doesn't work - I'm flummoxed!

Great!!! thanks so much, I am happy now. I am sending you the tar file I have used, just in case you will come across the problem once again in the future and will need to work out what went wrong.

thanks so much for the excellent service!!

Hi,

I have been also looking at this issue and I have stumbled over a solution.

As per the notes for the module on this website I installed the tinytinymce folder under ..\sites\all\modules

I then created a tinymce subdirectory under ..\tinytinymce folder in which I put the jscripts folder

Now this bring up the RichText panel allowing me to both format and add images as I previously had in my v5 version.

Hope this helps

Chris

Hi,

Here attached in a zipfile is the jscript file structure

Chris

Hi Steven

I found your post trying to find a resolution of my problem.
as you can see my issue on http://drupal.org/node/347025, I can't see my "Browse" btn on the editor image function. (see attached jpg). I installed your version of tiny tiny MCE and delete my tinyMCE from sites/all/module directory. I'm not sure this supposed to fix my issue but I am desperate to do whatever I come across. My site is in our development server (Debian/Linux server) and I am viewing firefox 3 with Mac, but same issue in windows (both IE and firefox). I don't think this is a browser issue. If you can help me, would be appreciated.

My issue has solved using http://drupal.org/node/347025 recommendation and installed inline module. Thanks, everyone.

Update: I withdraw this support request; my problem has been solved. For me it was a browser issue after all. (I should have tested more thoroughly and not been distracted by others saying the browser wasn't the problem!)

-------------------------------------------------------------------------------------------------------------------------------

I'm having a similar problem - rich text link doesn't bring up the WYSIWYG. I just reinstalled using your file from stevelockwood.net ... no luck. Attached is my source code from a create content interface .... maybe it'll reveal something? It's been a while, but I installed TinyTinyMCE in another site and it showed automatically in the create content form, without the link. Is that a setting that I've now forgotten, or an older version? I don't remember a special configuration.

I'm using Drupal 6.10, BTW - thanks.

Thanks Chris! The zip with the jscripts folder worked for me.

The problem is that each time one updates tinytinymce, even without realizing it (through drush, for instance), the tinymce folder is erased. Perhaps the module could give a warning in the Status Report when the tinymce folder is missing?

If you're running into this issue, and you've double-checked that you've got the directory structure installed properly, try running update.php before you do anything else. It worked for me. (I recommend that step be added to your documentation.)