Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

All other Modules /

Discuss all other Modules here.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

mobile module: redirect loop


Go to End


4 Posts   2065 Views

Avatar
Anatol

126 Posts

1 July 2011 at 2:30pm

There seems to be a problem with the $FullSiteLink feature of the mobile module. When I test this on a mobile device I end up with an endless redirect loop between mydomain.com and m.mydomain.com .

$FullSiteLink in a template creates a link with ?fullSite=1 at the end. The MobileSiteControllerExtension then *should* create a cookie so that for 30 minutes a mobile device would display the actual (non-mobile) site. This doesn't work. The same problem appears with the "full site" link on http://m.demo.silverstripe.com/ .

I tried to print_r($_COOKIE), but it doesn't print any 'fullSite' cookie, neither on a mobile device nor on a desktop browser. Is there not enough time or any other problem with trying to create the cookie just before the redirect?

Any hints would be highly appreciated. For now I will just remove the link but I would love to find a solution for this.

Cheers!
Anatol

Avatar
ht_kanrisha

Community Member, 9 Posts

20 December 2011 at 10:46pm

I have the same problem as Anatol's. Any advice from a SilverStripe expert?

Avatar
Willr

Forum Moderator, 5523 Posts

9 January 2012 at 7:22pm

Running the latest mobile module? A couple recent patches should fix the issues

https://github.com/silverstripe/silverstripe-mobile/pull/4
https://github.com/silverstripe/silverstripe-mobile/pull/3

Avatar
ht_kanrisha

Community Member, 9 Posts

10 January 2012 at 1:39pm

Yes, installing the latest mobile module solved the problem. Thanks!