Motley Moose – Archive

Since 2008 – Progress Through Politics

Troubleshooting: IE Bug – SOLVED

UPDATE: The IE Comment Issue has been SOLVED. All IE users should be able to resume normal Moosey activity. Three cheers for John Allen!

As many of you know the Moose is currently experiencing some technical difficulties when it comes to the commenting abilities of our IE users. Soapblox is looking into the problem, but, is actually having a hard time replicating it. They have IE versions 7-10 working on their end.

Based on this, we are asking for your help in figuring out which version(s) of IE are having the most trouble.

Pleasestandby2

Wanna lend a hand?

We are asking that anyone willing to help out a bit with the troubleshooting open IE on their computer, check the version and release (click the ‘gear’ symbol in upper right and select ‘About Internet Explorer’), and then try to ‘Post a Comment’ to this diary with your version/release.

If NOT able to ‘Post a Comment’, please use the ‘workaround’ of ‘right-clicking’ on the time/date stamp of the FIRST comment in this diary, choose ‘open in new tab’, then reply to the comment with your version/release.

Sricki and I just ran our own little test (neither of use IE normally). We have the same version of IE 9 (9.0.8112.16421)…though mine is 64-bit.

She is able to comment….I am not.

/shakes head (IE evil!)

Hopefully the information gathered about IE version/release will help Soapblox suss out what is going on.

For now, if able, we suggest using Firefox, Chrome, Safari, Opera, or some other browser to participate on the Moose.

For those of you unable to access another browser, we are so very sorry for the inconvenience. Please be patient, we are doing all that we can and I am sure a solution will be found.

So, if you can, please lend us a hand and help us help Soapblox!

UPDATE: The IE Comment Issue has been SOLVED. All IE users should be able to resume normal Moosey activity. Three cheers for John Allen!

Photobucket

Categories: Uncategorized.

/ 32 Comments

32 comments

  2. JanF

    Version 8.0.6001.18702, fully patched.

    I also get a non-responsive script when I open the Moose there. It asks me if I want to wait for the script to finish or stop.

  6. Via Chicago

    I still can’t post from work, not sure what version we’re on, I’ll check today.

    The work around doesn’t work for me either, as the “open in a new tab” is gray’d out when I try it in that way. Also tried some other things like grabbing the HTML Link of the reply, etc. Nothin’!

  7. Peter Jukes

    I’m going to temporarily remove the blogads module which could be causing theproblem. It has no ad at the moment and is giving no revenue. I’ll save the previous code just in case it’s hard to reinstal

    Let’s give this a whirl

    Refresh your pages with a control f5 and try again

  9. Avila

    i don’t see active scripting options in IE 9, but Microsoft likes to confuse me . . . . script debugging is likely “bundled” with scripting controls. this seems to be their default setting.

    in IE, Tools –> Advanced –> Browsing

  10. uncheck automatic recovery from page layout errors
  11. uncheck script debugging
  12. uncheck script debugging (Internet Explorer)

    try to avoid compatibility mode in IE . . . and better still, don’t use IE unless you have to. “open in new tab” in IE 9.0 doesn’t render a webpage reliably ‘cuz IE is extremely resource-dependent.

    Chrome and/or Firefox are safer and can deal with 20 tabs, and can be used simultaneously, even if IE is the default browser.  YMMV.  i dabble but am no code jene-ee-us. 😉

Comments are closed.