Thanks for that reference, Mauno. I've actually found a few more similar trackers, but there doesn't seem to be a clearcut cause or solution. I'm at a loss on this one.
Tech support at the MP hosting our site thinks it's one of my plugins or something specific to my site. Part of this is I guess because I installed my own plugins, but I'm also the only site on the server reporting this problem.
However, I have the identical moodle version and setup on a different hosted server (our test site) and the editor opens correctly in IE. We've actually accessed both sites with IE from several different computers, and every time, the test site works and the production site doesn't.
The MP site, of course, has far better hardware, the most recent software updates and moodle-specific configurations. It's running PHP 5.2.2 with
Apache 2, were as the test site is running PHP 5.2.1 with
CGI.
Regardless, I would think if it was something specific to my site, or my plugins, I would see the same editor behavior from both servers. If it was exclusive to IE, again, it would this would occur with both sites. While the new site solved some major performance issues, created a few new issues (I can't use Activity locking on the new site, for example, but it still works on the test site running the same moodle version).
Unfortunately, I only have
ftp access to the new site, so I can't examine server or script error logs or anything else outside of the moodle root folder.
Hopefully, someone will stumble along the post with some ideas, any would be most appreciated. I hate to have to force students to start using a specific browser, especially the ones who have been using IE all along.
Thanks!