Multiple URLs - Sitefinity - General Discussions

All Replies

Posted by Community Admin on 19-Feb-2013 00:00

We redesigned our website. Our old site was running Sitefinity 5.0 and our new site is also running Sitefinity 5.0. Because we restructured the pages, wrote all new content, and redesigned the look and feel, it was easier to create it in a new Sitefinity website. We are using multiple urls to handle any links external to our website that point to information from our old site. Most of our multiple urls are working correctly.

I am having an issue as follows:

A page on the new site located at /campus-life/chapel-webcast">http://<domain>/campus-life/chapel-webcast has a multiple url at ~/webcast

Typing /webcast">http://<domain>/webcast will redirect appropriately to /campus-life/chapel-webcast">http://<domain>/campus-life/chapel-webcast

Another page on the new site located at /athletics/sports-webcast">http://<domain>/athletics/sports-webcast has a multiple url at ~/webcast/sports/live

Typing /webcast/sports/live">http://<domain>/webcast/sports/live tries to redirect to /campus-life/chapel-webcast/sports/live">http://<domain>/campus-life/chapel-webcast/sports/live resulting in a 404 error instead of going to /athletics/sports-webcast">http://<domain>/athletics/sports-webcast

Is this a configuration issue?
Is this a bug that has hopefully been fixed in 5.1, 5.2, 5.3, or 5.4?
Or is this intended behavior?

Posted by Community Admin on 22-Feb-2013 00:00

Hello Jeff,

I tested this behavior on a 5.4 project and was not able to reproduce it. I suppose this has been related to another bug, which was fixed before 5.4.

Regards,
Jen Peleva
the Telerik team

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 22-Feb-2013 00:00

Thanks for your reply Jen.

I am working towards upgrading our site to 5.4. I did a test upgrade to 5.2 yesterday. I just tried the problem url and it is redirecting properly now. So, it must have been a bug that was fixed in either 5.1 or 5.2.

This thread is closed