Thats a browser warning not related to medium trust.

No idea why you get that message but I suspect something in your content or custom module rather than something intrinsic to mojoportal. You don't get that error on demo.mojoportal.com do you?

The WebPart issue seems to be a new bug, its doing the same on my local machine. I will look into it.

Best,

Joe

So it sounds like some IE security warning triggered by loading a css file from a different domain. I think its because browser settings for the local zone where localhost runs may be configured too strictly. It doesn't want to allow loading this file in the intranet/local zone. So the problem may not happen on a real server because the site will run in the internet zone not the local zone as far as IE is concerned.

It seems like totally an IE issue I don't think its related to IIS.

I'm not sure about the default browser security for IE on XP, I did not think it was that strict but I've certainly seen how IE is so locked down on Win 2003 server by default. Possibly if your xp machine is a domain member then strict browser settings may get pushed down by group policy.

Hope it helps,

Joe

Does this happen on localhost or a public internet site? IE has different security settings for the local or intranet zone vs the internet zone. So if this issue happens on localhost it does not mean it will happen on production.

You can host the files locally to your installation, its not per domain it would need to have the files installed its per installation.

Hope it helps,

Joe

Hi Neil,

The files can still be cached by the browser when served locally. With the CDN the files may be cached before he even visits your site if he visits another site that uses the same version of the script from google CDN, but that is generally a very minor benefit.

I don't think its worth the effort to try and build something to auto update the files. For one thing the files don't change on google CDN, the files are version specific and have version specific urls, so for example when the next version of jquery comes out google will make it available but it will have a different url and the old version will remain available. http://code.google.com/apis/ajaxlibs/documentation/

There is no urgency about upgrading unless something isn't working or you are having trouble with something related to the script and sometimes upgrading can break things. For example there exist newer version of YUI but in mojoPortal we still use version 2.6.0 because I found that newer versions break the FCKeditor in some cases like if there is more than one on a page or the editor is inside a tab in IE the editor did not work (was fine in other browsers).

So I would host the files locally in your situation. If you see me mention that I updated mojoPortal to a newer version of those things in the release notes blog post you can consider whether you want to update your local copies.

Best,

Joe