As I pointed out in the earlier post, we were having problems with IE which resulted in IE not sending us the data on Windows based visitors (hence low numbers). In fixing that though we seem to have exposed a really nasty bug in Internet Explorer itself.
Basically the ITK code needs to be placed in the body of the web page on your site for the bug to not rear it's head. We think that's unacceptible and are working out our own solution to Microsoft's problems. In the meantime we're rolling back the ITK code to the earlier version so that the crashes IE users are experiencing go away.
TrackBack
TrackBack URL for this entry:
http://www.typepad.com/t/trackback/2530054/25843116
Listed below are links to weblogs that reference Internet Explorer bug causes ITK problems:
Comments (RSS)
Maria said...
So... do we need to make adjustments in our blogs at this point too like pasting new codes or something?
Feb 6, 2008 4:39:42 AM
Peter Wright said...
No, no changes are necessary.
Feb 6, 2008 7:56:46 AM
Carla said...
I do not know if this is related, but I was unable to access my blog yesterday. I kept getting "Internet Explorer cannot open the requested page, operation aborted" messages. I was able to access the blog a few hours later though. It seems as if other blogs were having the same problem also.
Feb 6, 2008 11:44:53 AM
mistipurple said...
yes, carla, i had the same problem. now it just has the 'done, but with errors on page' on my webpage. come to think of it, it's here too!! lol! at the bottom left of this very page i'm commenting on!
Feb 6, 2008 12:09:14 PM
Bill said...
I was also getting that error. It seems to have cleared up mow.
It also appears that you are saying that we have been required to change our code at least once, maybe twice, yet we have not been notified?
Are we supposed to now have the code in the body of the page?
Feb 9, 2008 9:58:36 PM
Pete Wright said...
Hi Bill,
No, that's absolutely not the case. Microsoft's bug had a work around which was to move the code into the body of the page (between the BODY tags). However, we try very hard indeed to not force code changes on you guys. Where possible we try to modify our end of the equation and make the scripts fairly intelligent about where they live and how they work.
That's another reason we pulled the update. Not only was it causing problems thanks to Microsoft's mess, but the only fix at the time would have been to require a code change. Instead, we went away, Daniel coded his brains out and we deployed a fix that requires no changes from any of you, but which rectifies a bunch of problems. I haven't blogged that release yet as we've been watching for a few days to make absolutely certain that everything is A-OK. So far it is :)
Feb 9, 2008 10:28:42 PM
ThinkBlogger said...
I cannot wait for the new release then :) Hopefully everything will continue to work without problems and will be released shortly :)
I also see the IE error at the bottom, though I hardly use IE as much anymore so I didn't notice it until this post; then I decided to check, hehe.
Feb 10, 2008 12:35:02 PM
Parag Desai said...
You can try using Other Alternate Browsers, if problem is really with your Internet Browser or the system.
Jun 4, 2008 9:22:52 AM