Active
Project:
Mobile Plugin
Version:
6.x-2.0
Component:
Miscellaneous
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Oct 2010 at 18:40 UTC
Updated:
26 Apr 2011 at 16:35 UTC
I am wondering if there is a way to force my desktop browser to show the mobile theme. I have the mobile garland theme enabled, but I intend to develop my own mobile theme and I want to be able to view it in a browser 'on demand' during development. I have two domains set up ex: m.mydomain.com and www.mydomain.com with the automatic device detection enabled. Is there a rule that I can write that will change the theme on my desktop browser if I type in m.mydomain.com and then switch it back if I type www.mydomain.com? Thanks for your help and thanks for this great module.
Comments
Comment #1
nrackleff commentedA little more info. I just discovered the block that you can add to switch to and from the mobile version. I added that block to both the mobile and regular themes. When I am on www.mydomain.com and click the link to "Show mobile version" nothing happens. I don't mean nothing happens, what I mean is the url in the address bar changes to http://m.mydomain.com/?destination=node, but the theme doesn't change. Do I need to fix another setting somewhere else? thanks again.
Comment #2
nrackleff commentedI have changed the title of the issue as it now appears that the plugin may not be working properly.
More info: I tried going directly to m.mydomain.com today with an iTouch. When I first hit the site, it did show the mobile theme. As soon as I clicked a post title to navigate to another page, it reverted to the default site theme and stays on the default theme. It does seem to be properly detecting the device and assigning it to the correct group, but it's displaying the default theme instead of the mobile one.
HTTP_USER_AGENT: Mozilla/5.0 (iPod; U; CPU iPhone OS 4_1 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7
Detected group: mobile
Detected touchscreen: true
I do have automatic device detection enabled.
The link to "Test group until the end of the session" does work.
Any ideas why this might be happening?
Comment #3
nrackleff commentedComment #4
nrackleff commentedComment #5
ethernutza commentedI am having the exact same issue as nrackleff.
Comment #6
SpiderFudge commentedI am having this exact same problem. Anyone know why this is happening?
Comment #7
restyler commentedthe module is just not working - for me and for a lot of other people in this thread. I've enabled mobile switcher block and when I click "Mobile version", nothing happens. In my detection rules, I have "m1" group active for touch devices and not-touch devices, and the module should switch the theme for that group. I think that's critical.
Comment #8
designotb commentedSeems like an issue with page caching. After installing Mobile Tools and going through the settings for that it said that if page caching was turned on it would cause issues. I disabled the page caching on www.kamloopstodo.com and it seems to have resolved the issue.
It wasn't overly clear in the installation instructions how this would work or behave with page caching turned on.
I was receiving very inconsistent results before. If I changed to mobile, it wouldn't always change, other times it would change and then not change back. Clear all the caches and it would work, took me some trial and error to narrow down this problem.
Hope this helps someone else.
Comment #9
blaiz commentedSubscribe. Doesn't work here either. I uninstalled Boost module and disabled caching and still doesn't work.
Comment #10
rajmataj commentedIt seems like this module is no longer being updated and this thread has continued for a long time without any resolution.
Mobile Tools is an alternative to mobile recognition and theme switching and is actively maintained. Head there instead.
Comment #11
blaiz commentedActually, could be related to Availability Calendars. Having this problem here at first, I switched to Mobile Tools and had the same problem. I then updated Availability Calendars to the latest dev version and the issue was resolved.