WordPress.org

1. artesea
   Member
   Posted 2 years ago #
   

   I've got Mobile Pack set up to display the mobile version of my site when someone visits http://m.libdemvoice.org/ by using a cname back to the master domain.
   However I'm finding that my CSS and JS are being misdirected, eg
   http://aws.libdemvoice.org/http://www.libdemvoice.org/wp-content/themes/mobile_pack_base/groups/nokia_high/styles/reset.css.gzip
   I assume the fault is because Mobile Pack is displaying www. whilst Total Cache is watching for m. but was wondering if anyone has found a way to fix this issue.

   If there was a menu option to replace http://aws.libdemvoice.org/http://www.libdemvoice.org/ with just http://aws.libdemvoice.org/ it would help.

   My current hack is to dump mobile useragents in the CDN Rejected user agents box, and this ensures the mobile site still looks ok on mobiles, but not when using a PC.

2. Frederick Townes
   Member
   Plugin Author
   Posted 2 years ago #
   

   If you're using a CNAME, W3TC is unaware of the subdomain. Unsure what your exact settings are, but I'm not really following how this outcome is created.

3. artesea
   Member
   Posted 2 years ago #
   

   What would be the recommend option for running an m dot version of a site?
   I need to ensure that the cache of m doesn't mix with www
   It worked fine with WP-Super Cache.
   I've had to redirect m to www and display the main site for the moment as the caches kept clashing.

4. Frederick Townes
   Member
   Plugin Author
   Posted 2 years ago #
   

   WP Super Cache is irrelevant, it has far less features and capability.

   W3TC will unique cache files for every user agent it can detect, so if you have a mobile theme or a mobile site to redirect users to you can manage those options per group on the user agents group settings tab.

5. artesea
   Member
   Posted 2 years ago #
   

   But like I said I had a CNAME for m.libdemvoice.org pointing at http://www.libdemvoice.org
   The Mobile Pack plugin detects if you are at m. and displays the mobile version of the website.
   With WP Super Cache I ended up with two cache directory, one for www and one for m.

   With W3TC I found that my main site at one point was displaying the mobile version, and a few times on my phone I ended up with the full site.

   I don't want to use UA detection in which theme to display, nor do I want a cache for every UA, what I want is for people visiting www to get the full site, and those visiting m to get the mobile one.
   This allows people to choose which version they want, not which version I think that they might need.

   I don't mind playing about installing another plugin if that will result in W3TC understanding that m. is a different version and needs it's own cache.

6. Frederick Townes
   Member
   Plugin Author
   Posted 1 year ago #
   

   I'm not clear on the problem. The user agent groups make sure that there are separate caches for separate groups of browsers. The mobile plugin you use has no bearing on how W3TC creates it's cache files, it's job is to make sure that different browsers do not receive the incorrect type of page. I suggest testing without m. and then with and without W3TC and with so we can be sure which piece of the puzzle is creating the unwanted effect. W3TC is already compatible with many mobile plugins btw.

Topic Closed

This topic has been closed to new replies.