WPTouch W3 Total Cache – must disable browser caching?

I did a little more troubleshooting. I reset W3 Total Cache to defaults and tried testing with just browser caching disabled, without the Rejected User Agent list, but that seems to have the same problem. Restoring the Rejected User Agent list (as above) re-enabled the correct WPTouch behavior on my Droid.

That’s how I’m running right now – browser cache is off and the Rejected User Agent list is in place – but I’d really like to use browser caching if anyone has a working setup to share.

I’m thinking about buying WPTouch Pro, but I’d rather know I can make it work well with W3 Total Cache before doing so.

Thanks.

This still seems to be the situation in 0.9.2.2. I’d love to get browser caching enabled if anyone has any tips.

Megazone,

We just went through this with a customer’s blog and finally got resolved by adding the following long list under Page Cache, Minify and CDN. There is hope on this one as we were a bit frustrated too. We are using Pro version of WPTouch. Good luck with it.

iphone
ipod
ipad
aspen
incognito
webmate
android
dream
cupcake
froyo
blackberry9500
blackberry9520
blackberry9530
blackberry9550
blackberry 9800
blackberry 9780
webos
s8000
bada
2.0 MMP
240×320
ASUS
AU-MIC
Alcatel
Amoi
Audiovox
AvantGo
BenQ
Bird
Blazer
CDM
Cellphone
DDIPOCKET
Danger
DoCoMo
Elaine/3.0
Ericsson
EudoraWeb
Fly
HP.iPAQ
Haier
Huawei
IEMobile
J-PHONE
KDDI
KONKA
KWC
KYOCERA/WX310K
LG
LG/U990
Lenovo
MIDP-2.0
MMEF20
MOT-V
MobilePhone
Motorola
NEWGEN
NetFront
Newt
Nintendo Wii
Nitro
Nokia
Novarra
O2
Opera Mini
Opera.Mobi
PANTECH
PDXGW
PG
PPC
PT
Palm
Panasonic
Philips
Playstation Portable
ProxiNet
Proxinet
Qtek
SCH
SEC
SGH
SHARP-TQ-GX10
SPH
Sagem
Samsung
Sanyo
Sendo
Sharp
Small
Smartphone
SoftBank
SonyEricsson
Symbian
Symbian OS
SymbianOS
TS21i-10
Toshiba
Treo
UP.Browser
UP.Link
UTS
Vertu
WILLCOME
WinWAP
Windows CE
Windows.CE
Xda
ZTE
dopod
hiptop
htc
i-mobile
nokia
portalmmm
vodafone
BlackBerry7100i
Nokia6650d
SAMSUNG-SGH-A737
HTC_P3650
HTC_HD2_T8585
HTC-ST7377
htc_touch_pro2_t7373
HTC_Dream
HTC-P4600
HTC_Touch_Pro_T7272
HTCP3300
LG-CT810
LGE-MX380
BlackBerry9650
BlackBerry9700
BlackBerry9630
BlackBerry9000
BlackBerry8330
BlackBerry8703e
BlackBerry8820
BlackBerry7100i
BlackBerry7130e
BlackBerry7250
BlackBerry7230
BlackBerry7730
Cricket-A200
MOT-COOL0
MOT-V9mm
MOT-L6
MOT-V3r
MOT-V3i
MOT-A-1C
MOT-V620
MOT-V600
MOT-E398
mot-V3
Samsung-SPHM800
SAMSUNG-SGH-A867
SonyEricssonW595
SonyEricssonK800i
POLARIS

I added a similar list (see my first post) to all three of those as well, but it seems like I still need to also disable browser caching to get rid of the page ‘sticking’ problem on mobile browsers. I need more time to play with this, but I suspect it is tied to the .htaccess rules added by enabling Browser Caching, and the headers they insert.

I think a solution would be if WPTouch did something to alter the URL when toggling the theme (mobile/desktop) so that the browser would refetch the page instead of pulling it from cache. For example, adding ‘?wpt=mobile’ when using the mobile theme, or something similar.

Hmmmm. . .browser cache is a big part of the bennefit. Sucks to have to do that. Our re-writes are in NGINX so sharing ours with you wouldn’t do you a lot of good.

Ask WPTouch guys as I too agree that the solution likely is over there.

Yeah, if I find some time I may dive into the WPTouch code to see if I can add a query string when in mobile and see if that does work. But I’d love for the Brave New Code guys who chime in here. I’m probably going to buy WPTouch Pro, but I’d like to get this working first to know it can be solved.

The lack of responses makes me think there isn’t a good existing resolution to this. Maybe I’ll find some time to dive into WPTouch and see if I can fix it.

OK, I whipped something up *very* quickly as a proof-of-concept. It is quick & dirty. A small modification to wptouch.php in the bnc_filter_iphone function:

if ( isset( $_GET['wptouch_redirect'] ) ) {
                                $protocol = ($_SERVER['HTTPS'] == 'on') ? 'http\
s://' : 'https://';
                                $redirect_location = $protocol . $_SERVER['SERV\
ER_NAME'] . $_GET['wptouch_redirect'];
                        }
/* START NEW CODE */
                        if (strstr($redirect_location, "wptview")) {
                          $redirect_location = str_replace("&wptview=normal", "\
", $redirect_location);
                          $redirect_location = str_replace("?wptview=normal", "\
", $redirect_location);
                          $redirect_location = str_replace("&wptview=mobile", "\
", $redirect_location);
                          $redirect_location = str_replace("?wptview=mobile", "\
", $redirect_location);
                        }
                        if ($_GET['wptouch_view'] == 'normal') {
                          if (strstr($redirect_location, "?")) {
                            $redirect_location .= "&wptview=normal";
                          } else {
                            $redirect_location .= "?wptview=normal";
                          }
                        }
                        if ($_GET['wptouch_view'] == 'mobile') {
                          if (strstr($redirect_location, "?")) {
                            $redirect_location .= "&wptview=mobile";
                          } else {
                            $redirect_location .= "?wptview=mobile";
                          }
                        }
/* END NEW CODE */
                        header( 'Location: ' . $redirect_location );
                        die;

What it does is probably fairly obvious – it sticks a query string on the redirect when changing modes, with minimal checks for an existing query string. (It doesn’t check for a fragment anchor, like I said, quick & dirty.) For simplicity’s sake before setting the query value I strip out any existing ones, the most direct approach.

As a proof-of-concept, this works. I can turn on all the browser caching bells & whistles – expires header, cache control, eTag, etc. – and toggle back and forth between themes without getting ‘stuck’.

There are obvious flaws – it is only concerned with changing that one page and the query strings are only on that first reload. When you first load the page, say it is mobile, it’ll be the bare URL. Then you toggle to normal, it reloads with ?wptview=normal in the query string and looks fine. Then you follow a link to another page, that page will load with no query string and in normal mode. Now follow a link back to the first page, which will load with the bare URL – and you’ll see the mobile version. Why? Because that’s what the browser cached on that very first load.

A possible solution to this would be to have WPTouch tag a query string on *every* link as the pages are served. Or at least when serving pages in the non-default mode. (If you default to ‘mobile’ then only add query strings when in ‘normal’ mode, and vice-versa.) Then bare URLs are default and query tagged URLs are the alternate.

If not in the free version, perhaps in WPTouch Pro? Having WPTouch working fulling with caching would be a nice feature. I did this mainly to make sure my theory worked in practice. I’m not sure I’ll have time soon to try to make extensive changes to WPTouch Pro. Frankly I’d rather just pay for a version with this working than do the work. ??

I have to finished confog it… But speed download page only 56% … When I use W3TC 0.9.1.3 , it speed 85% ..

So boring.. Because it can work when check Auto : Minify mode …

Can you check here… I have creat Subdomain: Start.CuiBap.Org and Config CDN move CSS, Img, J…. ec

https://www.cuibap.org/anh-dep/gallery-allbum/

It link of Img changed to subdomain

Thanks everyone, so what’s the consensus here on the recommended user agent groups and any feature conflicts in W3TC?

I’m currently using the UA group that I posed above, and the conflict with WPTouch seems to be Browser Caching. I haven’t had any time to do more hacking since what I posted above, just been a busy week (business trip and then my folks were visiting). I did the hacks on WPTouch, but if there is a way to do URL re-writing in W3TC to force browsers to reload the pages when different themes are used (mobile vs. normal), or another way to solve the caching problem, that’d be great.

For now I decided having mobile users sometimes get ‘stuck’ on one version of the page is the lesser of two evils, so I’ve turned on browser caching and I still have my quick & dirty WPT hack in place.

Hello,

megazone i have wptouch pro and i try to find the bnc_filter_iphone function in wptouch-pro.php but i can’t find.

You have already the pro version? Can you please check if is on the same file in pro version?

Thank you

Tropa – Sorry, I’m still using the free version so the function may be different in the Pro version.

I’ve actually upgraded WPTouch and I haven’t reapplied my hacks to the update yet. I just haven’t had time to work on it and I’m willing to live with the issue for now.

Can anyone help with the final word?

Frederick,

I’d be happy to send you my current configuration for both W3 Total Cache and WPTouch. But even with that configuration there is still the issue of the browser caching causing the ‘sticking’ on mobile clients when toggling between the mobile and desktop themes in WPTouch. Adding some kind of query string to the URL seems to help, as in my proof of concept.