On my Drupal driven site I have installed the tinyMCE module (and its companion imce). Once it worked beautifully but all of a sudden it seems to have disappeared!
When I try to enter new content (let's say a 'page') the only thing I see below the 'body' textarea is "disable rich text" which when clicked throws a Javascript error: "mceToggle is not defined". What is happening here???
FYI:
- everything (Drupal. tinyMCE, tinyMCE module etc) is latest version
- I've tried:
- disableing and re-enabling the module
- deleting the module and re-installing it
Nothing helps!!

Comments

vm’s picture

are the buttons enabled ?
have the default settings been changed ?

inspect adminster -> settings -> TinyMCE

petervm’s picture

Yep, I knew it but checked anyway. Most buttons and some of the plugins are enabled. I also have users with TinyMCE access. More ideas?? (hope so!)
Peter

wmostrey’s picture

Hey petervm,

Are you the only person who is not seeing the TinyMCE GUI? Have you tried different browsers, different PCs? Is the GUI also unavailable as admin user?

petervm’s picture

Hi,
I've tried on Firefox, Opera and IE7 both on my local development machine and on the actual site (which luckily is not operational yet but should be in a few days). I also tried several different users ('superuser', admin (with full rights) and a 'moderator' with restricted rights. No combination yielded succes.

Peter

wmostrey’s picture

Did you read the install.txt correctly? A common mistake with this module, is that you have to create a "tinymce" within the "tinymce" folder. So the content of the directory

modules/tinymce/tinymce

should look like this:

changelog
docs
examples
jscripts
lgpl.txt
readme
todo

The jscripts directy should thus be here:

modules/tinymce/tinymce/jscripts

Is this the case with your setup?

petervm’s picture

Yep, read it, checked, read it again, rechecked etc.
Apart from lglp.txt and todo everything is there and in the proper place both at home and "on site".
Within jscripts there's again a tinymce directory and that one contains:
4 dirs: langs, plugins, themes and utils
5 files: blank.html, license.txt, tiny_mce.js, tiny_mce_popup.js, tiny_mce_src.js and on the production site tiny_mce_gzip.php.

It may or may not be of importance but I think I should mention it anyway (sorry, didn't think of it when wrote the original post). At one time I have had the taxonomy-access module installed which caused problems (people were shown the Drupal welcome screen). Wading through the documentation and support pages I found out that it was not uncommon for this to happen, unnstalled and deleted the module and then the tables and entries it had left in the database to get things working properly again. I'm not entirely sure and not blaming anyone but I've got a feeling the TinyMCE problems started about the same time (but only became apparent/were noticed later).

Peter

hairylunch’s picture

I was having this same problem. Looking over the tinyMCE compressor readme.html, the first line is:

Copy the tiny_mce_gzip.js and tiny_mce_gzip.php to the tiny_mce directory. The same directory that contains the tiny_mce.js file.

Apparently I hadn't copied over the tiny_mce_gzip.js, and once I added it, everything worked.

From what I can tell, the install.txt for the module needs to be updated to include this . . .

ufku’s picture

if disable rich text is printed then mceToggle should be there too. they are output of the same function.
check the html source. if there is the javascript function mceToggle(id, linkid) in the head section then it is blocked in some way. try disabling the modules that are adding javascript to head.

--
ufku
Geneticists from METU

petervm’s picture

Sorry, no javascript in the head section.
There is some just following the textarea tag but there's no function declaration in it (it only results in showing the "disable rich text").
Still, you may have shown the right path of investigation: in page.tpl.php I have built my own head section as I want to do some simple browser checking to incude the proper css for IE/other browser. Perhaps I ought to include something to get TinyMCE running??

Peter

petervm’s picture

Yes, that's it!!

Commented out my 'priavte' header section and put back the original
print $head
print $styles
and promptly there's a whole lot of javascript there.
I guess I can tackle it from here but any suggestion on how to best combine my idea and Drupals' is welcome!

Thanks everybody!

Peter

tkgafs’s picture

I have also been having this problem

after a system crash I had to reinstall all the drupal code my db was fine, so obviously I got the latest 4.7 versions of everything

but there seems to be some sort of problem with tiny_mce_gzip.php

if the file exists then tiny_mce only shows "disable rich text" below the text box if you remove tiny_mce_gzip.php everything works fine

hopefully this may help others in the same position

tkgafs

keesje’s picture

I added in this file: tinymce.module

this line:
if ($init) drupal_set_html_head($js_toggle);

just below:
if ($init) drupal_set_html_head($tinymce_invoke);

Just put the line into place (line 239)

This is solved in latest version of this module.

Regards

Webbased applicaties, content management systemen, websites, webdesign

uchauhan’s picture

Same problem here. I did everything (installing, deleting, reinstalling, copying 10 times), still TinyMCE does not show up.

Help !!

venkat-rk’s picture

Did you check it out by logging in as the user for whose role you enabled it? It seems (I am not 100% sure) that the toolbar won't show up for admin (uid1). Of course, this is assuming you edited your TinyMCE profile to enable the buttons for the various plugins.

---
Previously user Ramdak.

niklp’s picture

This admin issue doesn't appear to be present any more. I have just set up a version from the 5.x-1.x-dev 2007-May-06 release, and I can confirm that I am seeing Tiny in admin's create content screens.

I would advise anyone installing this to ignore compression and spellchecking etc until after they have got the proper standard release working! There are known complications with the gz.

AppSol’s picture

Before you start hacking the scripts, I'd check your directory structure. I had the same problem, installed ok, got the TinyMCE plugin admin, set up roles, etc, etc, but still no TinyMCE interface. I got the "disable rich-text" toggle, but this is created by the plugin, not TinyMCE.
So, best plan - view source, and lo and behold there is the issue. The plugin requires this directory structure (working from your modules directory, which in my case is sites/all/modules):
tinymce/tinymce/jscripts/tiny_mce/tiny_mce.js
The TinyMCE download unzips to a directory called tinymce which contains the "docs" and "examples" directories as well as the "jscripts" directory, which in turn contains nothing but the "tiny_mce" (note the underscore) directory. So the temptation is to save space and upload time to just upload the "tiny_mce" (with underscore) directory. But of course the plugin cannot see the tiny_mce.js file which is what it is going for.
So check your source, write down the required directory structure, open ftp client and make sure that is what you've got. You dont need the examples and docs directories so you can leave them out, just preserve the correct path.

janusman’s picture

Upon upgrading to 5.1 from 4.7 I had the same problem:: despite everything installed correctly, profiles, etc. I couldn't get tinyMCE to appear (only the "disable Rich text" link showed ok).

I found out that the included templates now have a <? print $scripts ?> line as well in page.tpl.php. I included that line on my template and lo and behold, tinyMCE now works fine.

Hope this helps y'all!

foaad’s picture

$output .= drupal_get_js();

My problem was that the theme_page() function wasn't including javascripts, including the one TinyMCE adds. It should go in the header section.

jsimonis’s picture

This was our problem as well. I'd been upgrading 4.7 custom themes to 5.x. I'd gotten everything in the body, but missed that in the header. Now the sites are all working.

--
Jenni S.
http://www.nu-look.net
Portland, OR metro area
Contact Me

Greg Go’s picture

This solved it for me! Thanks janusman!

It's kinda buried in the instructions for converting 4.7 themes to 5.x, but my own fault for not RTFM'ing more carefully.

mbria’s picture

A new one with a self-done 4.7 theme that need some tunning.

I checked everything before I start searching the forum... silly me !! ;-)

Thanks a lot. It was driving me crazy.

mbria’s picture

To avoid problems with php don't miss the "php" at the opening tag:

<?php print ($scripts) ?>
oligoelemento’s picture

You need a tinyMCE profile with 'authenticated user' role allowed to be able to use tinyMCE with superuser or uid1 user account.