The big problem about using returnid on urls
Posted: Thu Aug 28, 2008 6:49 pm
Since I started using cmsms, I think that returnid on the url is a bad idea, I will explain why:
On News Module, you´ll get duplicated content even using pretty urls( news/1/57/name.html )
57 is the returnid. For example if we set the detail page param, the returnid will always be the same. The fix our duplicated url problem.
But, that´s a quick and dirty fix. Anyone can create a link from anywhere on internet, changing the returnid to a valid return id on your site, then you´ll get duplicated content indexed, because of a malicious user, so if you use cmsms news, even with that detailpage param, anyone can screw you with dup content.
Suggestions?
On News Module, you´ll get duplicated content even using pretty urls( news/1/57/name.html )
57 is the returnid. For example if we set the detail page param, the returnid will always be the same. The fix our duplicated url problem.
But, that´s a quick and dirty fix. Anyone can create a link from anywhere on internet, changing the returnid to a valid return id on your site, then you´ll get duplicated content indexed, because of a malicious user, so if you use cmsms news, even with that detailpage param, anyone can screw you with dup content.
Suggestions?