WordPress 3.2 and IE9 issue

Does IE8 not rely on the same thing then?

In the back end of wp? Probably not the same for IE8 and 9. If you use IE8 you get the browser out of date warning and you don’t with IE9. The entire backend is basically run with javascripts.

Have you checked this document, https://www.ads-software.com/support/topic/troubleshooting-wordpress-32-master-list?replies=7

I’ve downloaded the lastest copy of java as well as reset IE9’s settings, all with the same results.

(Oh, there’s an edit button! Color me blind for not noticing before now.) I have encountered the same problem with a clean install of 3.2 using IE9 on a Vista machine and a Windows 7 Home 32-bit machine, but it worked fine for me on a Windows 7 Professional 64-bit machine.

All the machines I’ve tested on have been Windows 7 64-bit. I’ve tried the 32-bit & 64-bit version of IE9 with the same results on both.

Downloaded IE9 on my laptop and my desktop. WordPress 3.2 dashboard works fine in both. Tested IE9 x86 and x64, both machines run Windows 7 x64.

If the problem is not with WordPress or your local machine, the only possibility is with your host/server.

1: Does the server use any page compression or caching, such as GZIP? Can you turn it off?

2: Are pages being server by an intermediary? I have seen Content Delivery Networks (CDN’s) cause issues with WordPress’ dashboard. Do you (or your host) use CloudFlare protection? There is a known issue between the two.

As much details as you can provide about your setup is all that will be helpful here.

I’ve just tried installing WordPress 3.2 on a completely different host and I am still getting the same results. Surely this means it can’t be server related!?!

I have a copy of XAMPP on my machine, a dedicated server running WHM/cPanel and an external host, all running WordPress 3.2 and keep getting the same results.

What about other software running on your machine(s)? DO you have any common toolbars, antivirus applications, plugins, IDE’s etc etc? Perhaps a firewall or script blocker?

I’m starting to get a little short on ideas…

None of the above. I’m extremely short on ideas too. I’ve been doing so much trial and erroring the last few days.

I’m having the exact same issue with the admin. The front end works fine, but the admin looks like duncmorley’s in only IE9.

I’ve tried this on a few other machines with testers. Out of 14 other computers, 1 of 2 Vista machines displayed the problem, 0 out of 4 XP machines displayed the problem, 3 out of 8 Win 7 machines sorted the problem.

On 2 out of 3 of the malfunctioning Win 7 machines, fully updating the OS resolved the problem but it failed to do anything on the other machine. It may be a coincidence but may be worth nothing, all 3 of the failing Win 7 machines in this round run on Core Duo 2 processors.

Are you on a Core Duo machine? Do you have automatic updates turned on and if not, are you fully updated?

I am sorry but this is NOT a processor problem. Nice WAG though.

Javascript – execution or conflict. File coruption. The back-end is driven for the most part by javascripts. Work around – run the back end in IE8 . . . the whole idea is to get your blog up for folks to read – the mission. Just do it.

I have the latest version of javascript. I asked a friend of mine to check in IE9 and he had no problems.

It’s not the case of just trying to get the website/blog up but more of a case of making sure that this same thing isn’t going to happen once I pass the website/blog onto my client.

Just found your post on a Google search–running into similar problems developing a site for a client.

You making any progress? I wonder if there are some bizarre CSS issues going on…I see all the code for the dashboard in sourceview but most of it is not displaying in IE9. I may try and unlink the stylesheet and see what happens.

I just did a fresh install of WP 3.2 and went directly to the dashboard.

Am on Vista 32-bit right now…

Classic IE headaches again, if I had a dollar for every hour I’ve spent over the years working around IE issues.

I’ve updated to WP 3.2.1 today and i think that’s solved it for me.