KAPman

Hi Emilio,

After a few days of seeing and dismissing the message dozens of times, I received your answer, and then went back into my Dashboard, and no message! A mystery, but nice timing.

Thanks for your response, and your excellent plugin.

Hi,

I agree with the original post, AND I have updated to 4.3.13.1 AND I still get the annoying message all the time.

Sorry, my mistake – nothing to do with this plugin!

Thanks for a great plugin. It has worked beautifully for years.

The clash happened when I updated to WPTouch version 4.1.6.

Using a mobile phone, when I visited my website and tried to navigate to a new page using the menu, I would just stay on the landing page.

This problem stopped when I deactivated your Simple Full Screen Background Image plugin.

Cheers

A PS to my previous post.

This problem started with WPTouch version 4.1.6

Hi Daniel,

Thanks, definitely a nice addition.

Hello simpsonhf,

As I tried to explain in my two posts just before your’s, the problem is that the list of User Agents given at the top of this thread DOES NOT match the list of User Agents used in the actual WPTouch plugin as defined in
wptouch/core/mobile-user-agents.php

For example, for Android devices the code is:

if ( $settings->enable_android_phone ) {
$wptouch_smartphone_list[] = array( ‘Android’, ‘Mobile’ );

The really important thing here is that an Android device is defined as a mobile device if it is an Android AND a mobile, whereas the list at the top of this thread just says Android, ie ANY Android device.

So, if a non-mobile Android first lands on a page, WPTouch recognises it as a non-mobile device, as so serves up a desktop theme, then your caching plugin, using the list at the top of this thread sees the device as an Android, ie a mobile device, so the caching plugin will cache a desktop theme as a mobile!

The list User agents for configuring cache plugins given at the top of this thread is, I believe, WRONG. The definitions of what are mobiles are too broad.

I am really disappointed that my previous comments were never answered!

Just a PS to my previous post.

The problem with this mis-match of user agents really showed up when I wanted to cache both my desktop theme and my WPTouch mobile theme.

As a starting point, I used your exclusion list as an inclusion list for deciding if a visitor was a mobile.

What happened was that WPTouch recognised an iPad visitor (correctly) as a desktop, but then the caching plugin recognised it (incorrectly) as a mobile, so the desktop theme was cached!

Hello, and thanks for a great plug in.

However, there seems to be a mis-match between your “User agent list for configuring cache plugins” and the actual list of user agents in your plug in.

In particular, you have included “iPad” in your list of user agents above, but iPads are not included in your plug in.

I think your plug in is correct (for caching purposes iPads are desktops, not mobiles), so including iPads in the exclusion list means that iPad visitors don’t cause an uncached page to be cached, or don’t get served an already cached page.

Thanks

Hi,

I didn’t know that, so thanks for the info , and also for making the change.

Hello,

Further to my previous post.

I disabled the HTML Compression experimental feature and my Home page is now being cached, and there is no fatal error.

Thanks.

Looks good

Keith