04 Aug 2008
28 Jul 2009
Link to this post
I have encountered this following dilemma involving the URLs of the pagination repeater in the news list in sitefinity 3.2 sp2
It is worth noting that in our live environment this issue does not seem to be present (and i cannot find any code that would do some kind of rewriting of the URLs).
Basically, we have our test CMS sitting on a server that is not publicly accessible. Our test site is publicly accessible and all calls to the content area of the site are routed to the CMS and then returned through our front end.
On the live web server (e.g. www.live-site.com) all links in the pagination are as expected: http://www.live-site.com/news?page=2.
However, in the test server (e.g. www.test-site.com) all links seem to be absolute and are pointing directly to the CMS server (e.g. on an IP address 10.11.12.13) so that the pagination links are http://10.11.12.13/news?page=2. As i said, due to our CMS server not being directly publicly accessible, this means that the links cannot be followed.
The fact that it works in the live environment could mean that someone has put code in place to rewrite these URLs, but even so, why is it that absolute URLs are used? wouldn't it be better to use a relative URL so that such problems aren't encountered? Is there any way that i can change this behaviour?
Thanks for your help and suggestions in advance. This is the only problem stopping us going live with a major redesign and so i wish to get this fixed so that i don't have any more people barking down my neck ;-)