I thought everyone had switched to other browsers by now. (I always tell my students that friends don't let friends use IE, so at this point they've all switched to Firefox, Safari, or one of the lesser-known browsers.)
Actually, if you run Maxthon on top of the IE6 or IE7 engine, you've got yourself a real snappy browser, with a selection of plugins that's superior to FF's, IMO. Personally, I use both.
Meanwhile, SiteMeter has finally acknowledged and "resolved" their recent conflicts with IE -- and they want their disgruntled users back!
I like Firefox, but if I leave my machine running for a few days I find Firefox grabbing more & more memory. IE doesn't do this. I end up having to kill FF to get other apps running properly. Fortunately they've given us the feature that supports going back to the session that was killed (without all the allocated memory) when you restart.
Just thought you might like to know that SiteMeters been fixed. I found this notice on their website:
SiteMeter IE Issues Resolved
Dear SiteMeter Users,
We corrected a compatibility issue with our SiteMeter tracking code and IE7 and IE6 browsers that started last night.
The problem was related to some work we were doing on the backend system for our upcoming website launch.
We’ve identified and resolved two separate but related issues -
1 - IE Users viewing pages - The error occured when the SiteMeter tag was not a direct child of the body tag (e.g. if the tag was within a table or div). Recent changes we made created a failure for visitors viewing sites using Internet Explorer 7 and Internet Explorer 6.
2 - Accessing SiteMeter and Stats - Individuals trying to access or view their SiteMeter stats by clicking on their SiteMeter logo/icons were unable to gain access. This again appears to have affected only individuals using IE7 and IE6.
At this time both problems have been fixed and our services are fully operational.
For those who removed the SiteMeter code from your pages please be assured that the problem has been resolved and we sincerely apologize for the inconvenience.
If you have any questions please let us know by submitting a support ticket at support.sitemeter.com.
Sincerely,
The SiteMeter Team
This entry was posted on Saturday, August 2nd, 2008 at 3:14 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.
up
Voting closed 0
Support Universal Hub
Help keep Universal Hub going. If you like what we're up to and want to help out, please consider a (completely non-deductible) contribution.
Comments
Yet another reason not to use IE.
I thought everyone had switched to other browsers by now. (I always tell my students that friends don't let friends use IE, so at this point they've all switched to Firefox, Safari, or one of the lesser-known browsers.)
Actually, if you run Maxthon
Actually, if you run Maxthon on top of the IE6 or IE7 engine, you've got yourself a real snappy browser, with a selection of plugins that's superior to FF's, IMO. Personally, I use both.
Meanwhile, SiteMeter has finally acknowledged and "resolved" their recent conflicts with IE -- and they want their disgruntled users back!
I like FF - but
I like Firefox, but if I leave my machine running for a few days I find Firefox grabbing more & more memory. IE doesn't do this. I end up having to kill FF to get other apps running properly. Fortunately they've given us the feature that supports going back to the session that was killed (without all the allocated memory) when you restart.
Firefox 2 or Firefox 3?
Which version of Firefox exhibits this behavior (or do both of them do this)?
I forget - it's my work
I forget - it's my work machine and I don't remember if I upgraded yet. I'll VPN in and check.
(update: It's 2.x; I wonder if my problem's fixed?)
SiteMeter's been fixed!
Just thought you might like to know that SiteMeters been fixed. I found this notice on their website:
SiteMeter IE Issues Resolved
Dear SiteMeter Users,
We corrected a compatibility issue with our SiteMeter tracking code and IE7 and IE6 browsers that started last night.
The problem was related to some work we were doing on the backend system for our upcoming website launch.
We’ve identified and resolved two separate but related issues -
1 - IE Users viewing pages - The error occured when the SiteMeter tag was not a direct child of the body tag (e.g. if the tag was within a table or div). Recent changes we made created a failure for visitors viewing sites using Internet Explorer 7 and Internet Explorer 6.
2 - Accessing SiteMeter and Stats - Individuals trying to access or view their SiteMeter stats by clicking on their SiteMeter logo/icons were unable to gain access. This again appears to have affected only individuals using IE7 and IE6.
At this time both problems have been fixed and our services are fully operational.
For those who removed the SiteMeter code from your pages please be assured that the problem has been resolved and we sincerely apologize for the inconvenience.
If you have any questions please let us know by submitting a support ticket at support.sitemeter.com.
Sincerely,
The SiteMeter Team
This entry was posted on Saturday, August 2nd, 2008 at 3:14 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.