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?
The big problem about using returnid on urls
Re: The big problem about using returnid on urls
I actually have a problem with this.
When I click on the news [more] link I hit the 404 page.
I can go to the news details when I strip off the "&cntnt01returnid=12" part.
Is there a way to fix that ?
How can I make CMSMS use the correct returnid ?
When I click on the news [more] link I hit the 404 page.
I can go to the news details when I strip off the "&cntnt01returnid=12" part.
Is there a way to fix that ?
How can I make CMSMS use the correct returnid ?
Re: The big problem about using returnid on urls
Hello,
Actually you can do modifications to your news module if you´re familiar with php. Otherwise you´ll always have to pass returnid.
Actually you can do modifications to your news module if you´re familiar with php. Otherwise you´ll always have to pass returnid.
Re: The big problem about using returnid on urls
how do you do this ?
how do you set the detail page param so that the returnid will always be the same
???
This return id is killing me !!!
how do you set the detail page param so that the returnid will always be the same

This return id is killing me !!!