Mobile Redirect back to full version of site

I'm using the Responsive & Mobile Design on one specific page "Start" to redirect users to a mobile version of that page "Mobile Start". However I need to allow the user to chose to see the full version of the original page "Start" if they click the "Full Version" link on the mobile page?

Hello Kris,

Unfortunately this is not possible with out default Responsive design functionality at the moment. This, indeed, is an interesting case. However, since the mobile redirect rule gets applied always, you will be redirected to the mobile version of the website every time you try to go back to the default one. What you can do is create a custom redirect rule, which will get applied depending on the value of a cookie. For example, you can store a boolean value in the cookie ("redirect"). When you the user is redirected to the mobile version of the site, the value will be true. When he clicks on the link, pointing to default website, the value of the cookie will be changed to false. Depending on whether the value is true or false the redirect rule will get applied. You might also find this articles useful:
http://www.ytechie.com/2008/10/detecting-mobile-device-user-agents-in-aspnet.html 

http://dotnetslackers.com/articles/aspnet/Mobile-Device-Detection-and-Redirection-Using-ASP-NET.aspx 

There is, actually, a feature request on the subject. Here's the link, where you can vote for it and track its status.

http://www.telerik.com/support/pits.aspx#/public/sitefinity/12914

Jen where does this issue stand? I clicked the link for the feature request but it sent me to a general page. I have the same issue with a client running version 6.1. Is this feature in a later version or will I have to do something outside of SF to accomplish it?

 Thanks

Hello Kristin,

Our Public Issue Tracking System (PITS) has been replaced by our Portal. You can find the issue in question here. The bug is with status Not Done, meaning the behavior persists in Sitefinity version 7. We will do our best to fix this in our future releases.

Regards,
Ivan D. Dimitrov
Telerik