Jeremy,

The reason the sitemap link was an issue is that with the link there the sitemap was invalid and would NEVER be processed by google or other search engines.  Therefore that link under all scenarios (Other than on the actual dotnetnuke.com website) had to be removed as it was a breaking bug.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

off topic but in-line with the discussion of inclusion of dotnetnuke.com in various places of code..

1.  AdSense

2.  SiteMap

3.  Checking for updates    http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=5616 

Note my issue was withdrawn but submitted again in Gemini by somebody else.

I'm not sure but my #3 also can let you track all installs of DotNetNuke by the referral source of the website trying to access that image.    Beyond that, it also causes a problem in ssl mode, if you are operating on an internal network only and references code outside of the source.

 

 

#3 is a feature which has been part of the application since 4.3 ( over a year now ). It notifies Host users when a new version of the application is available. In order for this notification to work it needs to call a remote location and compare the currently installed version with the  latest version number. It then serves the appropriate image. This is a value added service for users of the platform, but we knew that some people would not want the behavior. So we included a host option for Check For Updates? which can be easily disabled. In the most recent release we made a change for the notification to be displayed to Host users in the Control Panel. This change was made based on community feedback from users who told us that they were not aware when new versions were released, because they never visited the Host Settings page after the initial application set up. So we wanted to make it more obvious to Host users and the Control Panel seemed to be the most visible area.  I understand that the current implementation does not work well with SSL. We experimented with a web service - but it does not work in medium trust. So there is no perfect solution. But since we provide the option for users to disable the upgrade check - there are very simple workarounds to override the behavior. So if you are an individual that does not like the feature, would prefer not to use it, or are working in an environment where it is a problem - please feel free to disable the option. However this is definitely not a bug, as it actually provides value to many community members.

---

My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com