TinyMCE not working in IE after upgrade to 1.6.4

feh, no improvement.

I had a problem like this in WordPress, and found that it had to do with there being an extra line in a config file, inserted accidentally during an update process. That seemed to affect the order of loading for scripts. When I cleaned up the config file line spacing, the problem went away.

But I didn’t see anything amiss with my EE config files! :(

Such an issue should be consistent, though, at least with a given browser, behaving the same for everyone using that browser. Go ahead and check your index.php, path.php, and config.php file for extra whitespace after the closing PHP tag, though, to be thorough.

Checked all those, all fine. Did remove extra linefeeds in index.php, but there is no whitespace or linefeed after the closing PHP bracket.

Here’s something weird.

I am also using another set of custom fields for another type of post. Guess what. tinymce is working there!!

OK, what’s the difference?

Where it’s working, here’s the configuration: Field type: WYSIWYG (naturally.) 10 textarea rows Default Text Formatting for This Field: None. Hide Formatting Menu Is this a required field? No. Is field searchable? Yes. Show this field by default? Yes.

Where it is NOT working, here’s the configuration: Field type: WYSIWYG 6 textarea rows Default Text Formatting for This Field: None. Hide Formatting Menu Is this a required field? Yes. Is field searchable? Yes. Show this field by default? Yes.

I confirm that tinymce is loading in the publish page (by seeing it in the source.)

Strange problem. Why not displaying in this particular template?

Diana can you email me login access to the two publish forms you refer to above? I’d like to confirm both that I am unable to see TinyMCE in IE7, and inspect the source to see if there are any notable differences. Nothing about this is making any sense, though it’s a Javascript wysiwyg editor, so that’s shooting par. 😉

done.

I’m comparing the source myself, too (tho I know very little! I’m a code-monkey kind of webmaster).

Maybe I should try disabling the URL Field Extension (v.1.0.4), and see if that makes a difference? That is one big code difference between these two templates. I don’t think IE handles JS the same way FF does.

I could also disable gzip on tinymce if you think that might make a difference, too.

I don’t want to do that if you’re in the middle of checking it out, though. Let me know if you think I should give that a shot.

I won’t be able to log into your site and check until later tonight, Diana, so feel free to try in the meantime.

OK: disabling URL Field Extension didn’t make a difference, and turning off GZIP for tinymce didn’t make a difference.

Interesting, sometimes the About publish page (the short form with WYSIWYG field) has to be loaded twice to see the tinymce controls.

IMO this could be a tinymce problem in IE. I’ll look around for info.

woohoo! Fixed.

I hadn’t added the compressor PHP versions of the file.

Steps to fix:

1) Update tinymce to current 3.1.x version. 2) Add the Moxie gzip compressor files, a separate download, if you want the benefits.

a. Where to get them b. Download this file: Compressor PHP tinymce_compressor_php_2_0_2.zip c. How to install them

thank you for the help, and maybe this will help someone else, too!

—Diana

aaargh, no, it’s not fixed. grrr.

I saw the buttons once… and I haven’t seen them again. Deleted internet cache, checked the gzip settings, etc. etc. even turned off gzip. No dice.

—diana

when I compared the source for the same page in FF and IE, the only difference I found, besides the obvious differences of session ID and time/date, is this:

FireFox 2: Script executed in 0.1654 seconds   21 SQL queries used

IE 7: Script executed in 0.1744 seconds   20 SQL queries used

I wonder why the diff in SQL queries?

interesting…. verrry interesting.

When I move up the position of the field to #4, the buttons display.

When I move the field back to the bottom (#14 or #20) the buttons do not display.

So, I’ve moved it up.

I played around with the field order, and it looks like, if it’s a long form, that the WYSIWYG buttons did not appear if the field was at the bottom of the form.

Hi Derek, thanx for persevering with me on this. I’m totally willing to concede that EE may not be the problem. I really don’t have much idea about technical issues. It just seems odd to me that the toolbar works fine outside EE, just not within it. And the problem isn’t restricted to our environment at work, my home PC (Vista/IE7) can’t see it either. But your PC can see it. Maybe we have some weird Australian settings?!!! That the one person who can see it in IE doesn’t have?

I think I’ll just try and get Firefox installed for all these people.

Same thing, I have no issues with TinyMCE on your site Diana, in IE7/Vista.

@Deborah - I have no idea what could be causing it. Have you tried disabling all of your third party security software? And are you running any browser add-ons like Google Toolbar or anything? I remember that causing problems to no end for me.