TinyMCE not showing up

doh, im stupid, didnt choose to enable it… youd think clicking a button called “enable extensions” would enable the extensions wouldnt you

once again, EE’s dodgy interface lets itself down

What’s dodgy about it?

Thought I would wake this thread up instead of making another one just like it.

I am running EE 1.6.0, Build: 20070705 and I am having trouble displaying tinyMCE. tinyMCE is installed at the root of my server, and the extension and language files are uploaded to their respective folders within the EE system. Extensions are enabled and the tinyMCE extension is also enabled (see attachment). Cache is also emptied several times. I have tried both Firefox and Camino (Mac).

Still nothing is showing up in the publish area. Are there any settings, tips or tricks I have not tried yet?

All help is much appreciated 😉

To help I would need to see your tinyMCE settings. If you like, you could take a look at a related thread where I published my settings. Just delete the plug-in calls for those you don’t have or need.

Thank you for the quick reply. I have not read or understood too much of the settings yet, but my settings are like this:

URL of Tiny MCE Script: http://macbruker.com/tinymce/jscripts/tiny_mce/tiny_mce.js

Tiny MCE Configuration:

mode : "textareas",
theme : "simple"

I checked that the tiny_mce.js loades correctly through the Safari Activity Window. Site is set to offline, so only I can see what is going on behind the curtain while I am logged in.

Have you looked at the settings I published? (See link in my previous reply.) If what you are showing is ALL you have in your settings, it will not work. You need something like:

tinyMCE.init({
    mode : "textareas",
    theme : "simple"
});

I am aware of that, so I checked the source of my publish page in the browser just to be sure, and I think your start and finish lines are automaticly added.

At least this is the snippet about tinyMCE in my source:

//<![CDATA[
    tinyMCE.init(
    {
        mode : "textareas",
        theme : "simple"
    }
);
//]]>

I’ll try to disable the extension and re-upload the two needed files to my server.

Edit: I’ll leave the problem for some hours now, just to clear my head. The hours spent are not worth it if I keep walking down the same problem path every try. Thanks for your help so far.

If there are any other EE CP settings or .htaccess conflicts I should be aware of when trying to enable the tinyMCE extension, just shout it out 😊

I checked that the tiny_mce.js loades correctly through the Safari Activity Window.

Try another browser, because the TinyMCE support for Safari is not perfect…

CJ

I am aware of the browser support issues concerning TinyMCE. My use of Safari was just to see what resources was loaded on the publish page through the Activity Window.

Since it’s my own site I am working on, I have decided to let go of the tinyMCE problem and focus on getting my site online soon. Thanks for getting involved, I bet the solution wasn’t too far away 😉

This is starting to look like a bug.

When I use your settings via the SAEF, they work fine!

In the CP publish area, the same settings do not work AND the closing part, namely //]]>, of the

//<![CDATA[ … //]]> inserted by EE appears in the top of the rendered page. Same on Firefox.

Martin, do you see this too?

The only differences between the source of the tinyMCE snippets from CP Publish page and the source of my SAEF, are this pair of codes.

Hopefully one of the EE tech support people will become involved?

EDIT: Actually, what shows up in the rendered CP Publish page is } ); //]]>, not just //]]>

Bump - is anybody from tech support reading this?

The extension with the latest version of TinyMCE appears to be working fine in Firefox, Camino, and WebKit Nightlies. TinyMCE does not support Safari.

Derek - I guess I pissed you off so badly by cross-posting from the bug forum, that you decided not to read my reply of 27 August 2007 04:28 PM to this thread?

So, if I may, I will itemize the parts from that posting which I believe are germane:

1. This problem shows up using the settings proposed by Martin Berglund, when used via the Publish CP (I have not tried the Edit CP), but
2. The identical settings work perfectly from the SAEF
3. A stated in my post, the problem DOES show in Firefox.
4. Alternative settings may or may not work. I have tried a number, but Berglund’s settings never work.
5. The symptoms of the problem are:
   • tinyMCE does not “attach” to the textarea and
   • the characters } ); //]]> appear immediately above the CP window.
6. If you are interested in helping to verify this, I suggest you try Berglund’s settings, because I have got other settings to work. If you get a satisfactory result I will accept that this is a tinyMCE problem and nothing to do with EE.

My build is 20070815

I apologize for cross-posting to get attention.

PS -puzzled by the purpose of your link to the tinyMCE compatibility page, since it shows Safari as “OK” under 10.4. Slightly irrelevant since the bug shows under Firefox??

I’m not pissed off, JohnD, that’s simply not helpful to post a topic in any forum with no content other than a link to another thread. Especially in the bug forum, if you want positive attention from the staff, please follow the posted guidelines for the forums.

I’m using default TinyMCE settings, and it works. Using Martin’s settings works fine as well. Just for clarification, as Martin pointed out, the settings in the Extension Manager, do not use the ‘tinyMCE.init(…’ portion as the extension outputs that for you.

So the relevant questions are: what version of TinyMCE do you have installed? Have you downloaded the tinyMCE extension again to make sure you have the most up-to-date code? What version and build of EE are you running? What other extensions do you have installed?

PS -puzzled by the purpose of your link to the tinyMCE compatibility page, since it shows Safari as “OK” under 10.4. Slightly irrelevant since the bug shows under Firefox??

No, it shows “OK(3)”, and if you follow the footnote, you’ll find: “(3) - Latest nightly build of webkit works “OK”. You can disable TinyMCE for this browser by using the browsers setting.” It’s relevant since it had not been definitively stated in this thread, only intimated by Chris Jennings.