Hi All, I upgraded to EE 1.6.4 yesterday and now the TinyMCE bar doesn’t appear for Internet Explorer users. Appears fine in Firefox.
Any suggestions?
In case the install is just a coincidence, I also added the Playa extension last week sometime. I’m not able to pinpoint when TinyMCE stopped working as I use Firefox myself. User said ‘it’s been gone for a day or so’.
I’m using LG TinyMCE v1.2.1.
It is possible that our IT people have done a patch to IE or something that might have changed things, but I wouldn’t know what settings to look for.
Any thoughts or suggestions? Thanks.
So at present it’s only not working on your local machine? Have another computer you could try to access it on? When it fails, are there any Javascript errors? I’ve never used it, but some IE users mention using Fiddler for client-side script debugging.
It works for me in Firefox only, not in IE. Five other people I’ve checked with, who have the same computer/image as me, cannot see it either. But one person, who should be on the same image as us, can see it without any problems.
When I publish or edit a file in IE, the field just displays without a toolbar. I can’t see any errors.
I’ve downloaded Fiddler and had a quick look, but I’m going to need a second degree to work out what I’m looking at! Will keep reading.
Thanks for your help Derek.
When you view the HTML source, is the TinyMCE javascript in there? If you’d like another datapoint, you can email me (not PM please), CP access and I can give it a try on my IE7/Vista installation. Other factors might be 3rd party utilities and security applications installed. AVG has some that I think are known to detect plenty of Javascript as malicious and prevents it from running.
There is some javascript in the source, but I’m unable to tell if it is correct. Fiddler is showing a 404 alerts for tiny_mce/plugins/imagemanager/editor_plugin.js and tiny_mce/filemanager/plugins/editor_plugin.js which I’m guessing might be causing the problem.
I do have two extensions in the manager called File by Mark Huot and LG Image Manager but these are disabled. Do you think it might be related to those?
I’ll set up an account for you and email shortly. Thanks heaps.
Just glancing at Safari’s activity window, I’m getting 404s on those two files as well.
tiny_mce/plugins/filemanager/editor_plugin.js tiny_mce/plugins/imagemanager/editor_plugin.js
And also the GZip version that is in your extension settings 404’s, though the browser isn’t accessing it.
tinymce/jscripts/tiny_mce/tiny_mce_gzip.js
But it appears to still work just fine. Screenshot of IE7/Vista below (7.0.6000.16681)
It’s not likely to be a problem with other extensions, particularly since some people, myself included, see TinyMCE working fine. All signs point to something local, though I couldn’t guess what it is outside of my previous hunches.
Thanx Derek, I’ll wait on our IT people to get back to me and tell me if they’ve rolled out anything new in the last few days.
Those files that are 404ing don’t exist, I’m wondering why the system thinks they should. The download of TinyMCE doesn’t include them. It probably isn’t the problem, since as you say others can see the toolbar.
I’ve done some further testing.
I went home and could no longer see the toolbar in IE on Vista on my home machine either.
Everyone can see an example TinyMCE, regardless of their browser, at http://wiki.moxiecode.com/examples/tinymce/installation_example_02.php
I disabled the LG Custom Field Tiny MCE extension and tried to revert back to the regular EE extension. The tinymce toolbar still won’t display in IE, but works fine in Firefox.
I’ve been told that it would not be a java problem since it doesn’t rely on local machine java to run.
I’m now going to start removing the last lot of add-ons I installed to see if that will make a difference.
Nope, removing plugins didn’t help either. I also upgraded to the build 20080710 just in case. No difference. I had a developer take a quick look. He thinks the java might be failing to initialise/load when the page is created. Not sure why that would apply in IE only. I will keep fiddling, but am starting to run out of ideas!
The Javascript is being output to the page correctly, which means that any failed interaction is client-side, so I wouldn’t expect updating EE or your other add-ons would have any effect. If they were at fault, I’d expect it to not work in any browser, on any machine. It’s working in other browsers, and in IE as well except for what it sounds like are machines specifically within this setting (an office?)
I can’t find any logic to it at all!
There are 5 of us in this office with the same machine setup, same version of IE. I am the only one with Firefox, and I can see the toolbar in that.
One person can also see the toolbar in IE. The only difference I can see is that she always has that prompt ‘there are secure and insecure items on this page do you accept…’ which she selects Yes to each time instead of choosing the always option that the rest of us have.
In two separate buildings in this workplace (different machine setups), where the clients have IE 6, they can’t see the toolbar in IE. They can however see the toolbar when using another system that also has TinyMCE.
At home, completely different setup with Visa, I can’t see the toolbar in IE, but can in Firefox.
Everyone can see the example toolbar I linked to above.
So, it is something specific to EE and our TinyMCE installation. I just can’t figure out what :( It is something that happened recently, since everyone could see the toolbar until I upgraded to 1.6.4.
I’m still waiting on our IT people to get back to me as I’m not all that technical and have no idea where to even being looking for the cause of this problem. Guess they might be unsure too or they would have come back sooner!
I don’t see how EE is involved at all, honestly, Deborah. I’m still able to see TinyMCE on your site just fine in all browsers on both Mac and Windows. It’s likely coincidence that the problem started or began to be noticed following your update. If the PHP application were at fault, your output would be changing; the output to the server is identical, which means that EE is consistently sending the same HTML on every request to everyone.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.