DISQUS

Community Page on DISQUS

what is this?

The Inquisitr

Jump to original thread »
Author

Site Meter causing Internet Explorer failure

Started by Duncan Riley · 4 months ago

Traffic measuring tool Sitemeter is blocking users of Internet Explorer for accessing sites using the service.

According to a tip to The Inquisitr, the problem happens when anybody using Internet Explorer tries to open any sites with the Site Meter code present, and thousands of we ... Continue reading »

17 comments

  • Sue Charles

    4 months ago

    Thank you for posting this -- I thought I was the only one, that something was wrong with my computer.

    However, my browser is ATT Yahoo and I'm unable to open any Site Meter sites as of a few hours ago. I read a notice from SM a few days ago saying they were in the process of updating the service and that the SM logo on some sites would appear off and on, but not to be concerned.

    Looks like someone screwed up.
    reply
  • Sue Charles

    4 months ago

    Oops, I just checked and my ATT Yahoo has IE 7.0. But still, I'm not gonna change my browser -- I'm used to it and this is the first time I've had an issue. You all blame IE and god knows it's not perfect but this is Site Meter's problem!
    reply
  • Sebastian

    4 months ago

    IE isn't "not perfect", it's a piece of crap. Just about every user of a different browser will tell you the same. Join the good side, join the productive side, join the Mozilla or Opera side!

    This is a clear Site Meter problem, though. But nobody's blaming IE.
    reply
  • Sebastian

    4 months ago

    I have a similar issue with the latest Google Maps API code, which is online for about two weeks now. It broke access to each site that loaded the JavaScript-file, without any interference from my code. (I deactivated all JavaScript completely and just had Google Maps API activated.)

    After I switched back to the stable version of the API (I used the "normal" versions, not the "sneak peak" versions), everything worked again.
    reply
  • John Martin

    4 months ago

    This is common issue with Internet Explorer and JavaScript. It happens if you try and manipulate the DOM before the element has been fully parsed. E.g. if a SCRIPT tag is within a DIV and the JavaScript tries to manipulate the said DIV.

    It doesn't effect other browsers because Internet Explorer's rendering engine is much more "strict" in the way that it handles DOM manipulation.

    This really isn't Internet Explorers' fault because this is a well known DOM issue in Internet Explorer and any decent JavaScript developer should know about it.

    Bad show chaps.
    reply
  • Thomas

    4 months ago

    The ultimate fix, sitemeter.com is the problem. If you go into your internet explorer security settings and add the following to restricted sites then the page loads.
    http://*.sitemeter.com
    reply
  • Sue Charles

    4 months ago

    Thomas -- THANK YOU THANK YOU THANK YOU!!!

    Just out of curiosity, does this also mean that Site Meter cannot "read" my data? If so, that's not such a bad thing.
    reply
  • Krieg

    3 months ago

    Thanka a million!!!!!!!!!!!!!!!!
    reply
  • Lawrence

    4 months ago

    this wouldn't happen if people would just simply use Firefox.
    reply
  • LizN

    3 months ago

    Actually, this problem started happening for me using FF and when I tried on IE and found I still couldn't access the site, I decided to look into it further.
    reply
  • greggo

    4 months ago

    This is only a problem with the sitemeter JAVASCRIPT code. Using the HTML only code seems to be a decent workaround.
    reply
  • rockmanac

    4 months ago

    Seems to me like this is just another excuse to encourage the masses to come over to FF3!
    reply
  • bob e

    4 months ago

    I noticed the same problem - I thought it was Gizmodo that had code issues! These people should test their code on the worlds most popular browser - IE~
    reply
  • John Doe

    4 months ago

    It happens because the people at SiteMeter are modifying the DOM in their javascript code before the DOM is ready. They can't do that, its against browser standards. It's not an IE problem -- Firefox just ignores the issue and moves on and doesn't present it to the user.

    Site owners can fix this by just moving the JS code to the bottom of their page, underneath the </body> tag, at least until SiteMeter people fix their code
    reply
  • Keith J. Farmer

    4 months ago

    so all those firef*x users.. are running a buggy browser!

    No surprise, really.
    reply
  • Felipe

    4 months ago

    Ouch! That's why I developed my own web analyitcs app: http://www.i-stats.com and Google Analytics is NOT real-time (I have no idea how they can get away with that), so if you use Google Analytics and your site is mentioned on a high traffic blog, you won't know until a day or so later...
    reply
  • clustrmaps

    4 months ago

    As a 3rd party analytics provider, we feel SiteMeter's pain... blackouts/blockages like this are no fun for anyone.

    Like SiteMeter, ClustrMaps provides a 'plain vanilla' option - pure HTML, simple JPG only, no javascript, no cookies, nothing fancy. Unlike SiteMeter's detailed stats, ClustrMaps is complementary in that it provides a 'gestalt map' showing at a glance all visitor locations... many user's have both ClustrMaps and Sitemeter for this reason... anyway, here's wishing everyone a speedy recovery from this blip... outages/blockages like this are bad for all of us in the analytics/geolocation business, so it's good for everyone to get this resolved soon, to restore user confidence!

    -The ClustrMaps Team
    reply

Add New Comment

Returning? Login