Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...SiteMap.aspx errant link to dotnetnuke.comSiteMap.aspx errant link to dotnetnuke.com
Previous
 
Next
New Post
6/7/2007 7:16 PM
 
Turning off copyright under the host account worked like a charm. Thanks, John.
 
New Post
6/7/2007 8:23 PM
 

Same here.  :)

I agree that it should be fixed, but since we have a workaround, I hope that it isn't prioritized too highly.

 
New Post
6/7/2007 8:27 PM
 

Looks like another attempt at getting a hidden back link from all the installed sites out there.

 

 

It would be nice if we could lighten up on the conspiracy theories.  This seems to only involve sites that have chosen the host setting to include visible copyright credits.  Fear, uncertainty & doubt are not constructive or helpful in a community... though it does make for great headline opportunities for those looking to do so.


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
6/7/2007 8:49 PM
 

That is the only explanation?  Why would that link be added to a site map that is distributed to third-party sites?

There is way too much of this type of behavior in the recent releases, and it should be stopped, but it won't stop if people just accept it.

I am not fearful, but I am uncertain and doubtful of the intentions for these actions. 

It is really hurting the image of the application, and in turn that hurts everyone who puts any serious effort into our project.

Please stop with these practices, it is not worth the small gain.

 


DotNetNuke Modules from Snapsis.com
 
New Post
6/8/2007 2:57 AM
 

Ok, so how do I say this?

I am not ashamed... but I am embarrassed.

What I mean is that I take full responsibility for this code - I wrote it ( so thanks to the earlier comment from someone about it at least being well written! ). And I am not ashamed because I wrote the code with specific intentions in mind.

As stewards of the project, one of "our" duties is to increase its visibility through as many channels as possible. Why is this important? Because the size of the project and community matters. The larger and more visible the project becomes, the more opportunities become available to all members of "our" community and ecosystem ( users, vendors, partners, hosters, publishers, consultants, etc... ).

For example, do you think we would have been able to secure a spot for DotNetNuke in the DevConnections conference this fall had it not been for our recent activity and project momentum? Do you think we would have received the 2007 Editors Choice Award from Visual Studio Magazine? Or how about even getting official recognition from Microsoft, in order that community members who are active in these forums stand a chance of being recognized as MVPs? As much as we have a great product which is licensed under a liberal BSD license, there is still a lot of traditional marketing efforts and management which need to happen. We do the best we can with our severely limited resources and due to the nature of the project, online marketing is one of "our" best channels to increase visibility.

When I added the node to the end of the sitemap feed, I did so under the assumption that those people who were willing provide credit to the project by displaying copyright credits, would also be willing to provide credit through search engines. As such it was wrapped in the Show Copyright Credit? logic which can be modified through the Host Settings. I hoped that adding the node would provide some additional credit back to DotNetNuke, raising the profile of the main site and the community, and opening up new opportunities. 

So this gets to the embarrassing part...

When I implemented this in the 4.5.0 release, I tested the SiteMap validation for dotnetnuke.com. Of course the validation error never appeared ( because the extra node has the same URL as the site ). To be honest, I had no idea that there would be a validation issue in doing this. Well obviously I was mistaken ( I am not afraid to admit when I am wrong ).

And I certainly don't mind writing this post and providing a full explanation. I definitely appreciate when people report application issues, as it provides us with the opportunity to solve them. However, I do mind that there are some people who seem intent on twisting various unrelated items into some kind of sinister plot ( maybe its easier to think this way than to try and grasp the bigger picture ).

Regardless, I have now removed the offending code  ( and logged it under Gemini 5765 - thank you Mitchell for your assistance ).


My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...SiteMap.aspx errant link to dotnetnuke.comSiteMap.aspx errant link to dotnetnuke.com


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out