TinyMCE not working in IE after upgrade to 1.6.4

Hi all, me again - no-one’s emailed me that old version calendar file yet. It’s been 7 days without the toolbar and people are getting a bit narky over here. Can I get an ETA on a fix, or can I please get the old version file emailed over ASAP?

No ETA on a fix because the problem has not been identified yet, Deborah. I’ll email you the old files, but you could have just restored them from your backup prior to your update to 1.6.4. It’s not clear that it will certainly fix the problem either, so reverting to those files was a troubleshooting measure taken on Diana’s site because it’s not live yet, not a recommendation for a live site.

Hey Derek - thanks for the files, it worked! Our toolbar is back. Thank you! 😊 😊 😊 This’ll keep us going for a while.

Please do let me know if there’s anything we can do in terms of testing for this problem.

The only difference I can see is the required field component. What happens when you make he tinymce field required in the working weblog? Does it break?

Hi Leevi. In our installation it makes no difference whether the field is required or not. Same behaviour results (in IE only, versions 6 and 7 are all I’ve had available to test in).

It also doesn’t make a difference whether I use your LG TinyMCE extension or the other regular EE Textareas one.

If the date tab is there TinyMCE won’t display. If I take the date tab away, the toolbar is back.

Derek (and Derek),

Have you made some changes in my files? I see that now TinyMCE generates an error, “tinyMCE is not defined”. (but the paths look correct, and tinyMCE is present and enabled.)

My internal customers may be looking at this application soon, so I’d like to be error-free soon (end of this week?), even if they can’t use IE.

(by the way, I never do see the EE formatting toolbar next to the field, it only appears once, high on the page, is that how it works, or is this symptomatic?)

—Diana

Diana, neither of us have been given FTP access, so we have not made any changes to the files on your server.

Yes, the EE formatting toolbar only appears once on the page.

(I’m not accusing or anything, if my tone sounded that way, please accept my apology.)

I was surprised that TinyMCE isn’t working at all now in either IE or FireFox, because it was working yesterday. I thought maybe you made some changes in the TinyMCE configuration? That’s editable from admin.

If you are still working with my site, please let me know, otherwise I’ll just put things back.

If you’d like FTP access to try out code, please let me know.

—Diana

Yes, FTP would be super helpful if you don’t mind. This may take another day or two to track down. I’ve hit stumbles at many turns, but we’ll do our best to keep you in the loop in this thread. If you don’t mind emailing ftp I’d be happy to take a look.

Hi All. Just an update. I’ve been unsuccessful trying to recreate this locally. I’ll attempt to solve this directly on Diana’s server now. Thanks for your patience so far.

A followup question that may have been asked and answered already, but I’d like to recollect it into one place. Were you able to recreate this if using the first-party tinyMCE plugin, or only using LGtinymce?

Hi Derek, I’m experiencing this with the first party extension. I’m on php 5.2

oh, I didn’t even know there were two plugins.

For some reason, when I searched for this feature some time ago, I only found the LG version.

Should I try the other one? I don’t want to mess around if you’re in the midst of testing on my site.

… I just uploaded the first-party tinymce extension files, if you want to enable it.

Path to my tinyMCE isn’t in root, it’s in scripts/tinymce/jscripts/tiny_mce.

Hi!

I see you guys have been trying things out. Interesting: I see the first-party TinyMCE extension (which gives all textareas a few WYSIWYG buttons) is working in FireFox but not in IE7 (for me, anyway.) — but at least it isn’t throwing any errors.

How’s it going? (I think this sort of problem is the worst to debug.)

—Diana

Hey Diana.

You’re right, still plugging along. I’ve isolated the cause of this, but now the tricky part is figuring out how to resolve it. Thanks for your patience, I assure you I’m still on it (should have updated you earlier).