page error on ie 7

after upgrading from ie6

[jvanroos]

i have just installed ie 7; I have several users on my pc (windows xp prof sp2. My userid is working find with ie 7 but the others do not. They are all giving "page errors" for certain websites (such as this on [login.live.com...]

I tried to find out what the difference would be between the settings of my userid and the others, after a number of hours comparing all settings I am out of inspiration.
Could somebody give me some hints where to look for, or eventually how I could copy my IE settings to the other users to solve the problem.
Thanks very much for your help.
Jos

[SteveWh]

Are the page errors "Object expected"? After putting Google Analytics on my site, my pages started giving such errors. It was because the JavaScript provided by Google for their Analytics comes in two parts. One part is directly on my web pages and the other is only on the pages as a <script src=...> pointing to the remote code, which is served by Google Analytics. My Internet Zone setting is High. My site is of course in my Trusted Sites list. That allows "my" part of the JS to run. Google is a Trusted Site, too, but the JS isn't served by Google. It's served by http:// www. google-analytics.com (spaces inserted to prevent it becoming a link), which was NOT my in Trusted Sites, so their part of the JS code didn't run, which caused my part of the code, dependent on it, to give an error. The simple fix was to make the above site a Trusted Site. I suspect this will fix many apparently broken sites for people who normally browse with their Internet Zone security set to High. It's not just Google Analytics, either. Other sites serve bits and pieces of their pages from a variety of their corporate servers, and this same problem can result if you have made ONE of those servers Trusted, but not others.

You won't get this problem if you have JS globally enabled or globally disabled. It only results when two pieces of code run (or don't) in two different security zones.

Can't be sure this is the problem you're having, but this seemed like an opportune place to mention this new discovery, and it should fix a lot of sites that have been appearing to be broken.