WordPress › Support » [Plugin: W3 Total Cache] MobilePress compatibility

Gravitydk
Member
Posted 2 years ago #

I would wonder if you could check on making Total Cache compatible with MobilePress.
http://wordpress.org/extend/plugins/mobilepress/

http://wordpress.org/extend/plugins/w3-total-cache/
RavanH
Member
Posted 2 years ago #

And is it compatible? Anyone tried?
Frederick Townes
Member
Posted 2 years ago #

Right now it's not compatible although the latest release of W3TC does have a number of new mobile options.
RavanH
Member
Posted 2 years ago #

Just upgraded to the latest and must say IT ROCKS ! Mainly the database caching on disk option is pretty useful without memcached installed.

I also see a list of mobile browsers to be detected by W3TC in the options. Can you explain what this is for?

Are there any mobile plugins that do work with W3TC?
Frederick Townes
Member
Posted 2 years ago #

You could always use some mobile plugins with W3TC depending on how they work. But the rejected user list allows the pages for mobile user agents to not be cached so you can either do a theme switch for mobile or use the mobile detection to redirect your user to a domain with a mobile version of your site. More mobile support is coming in the next release.
RavanH
Member
Posted 2 years ago #

Ok, so if I do not define "Redirect mobile users to:" than nothing special is done with mobile users? Or are all in the "Mobile user agents" list excluded from seeing cached pages?

And can I ask you what you are planning for the next release? :)
Frederick Townes
Member
Posted 2 years ago #

Ok, so if I do not define "Redirect mobile users to:" than nothing special is done with mobile users

Correct

Or are all in the "Mobile user agents" list excluded from seeing cached pages?

No, "rejection" must accur for this to happen.

And can I ask you what you are planning for the next release? :)

Sorry not yet, let me make sure the idea is practical and how long it takes to finish first. :)
RavanH
Member
Posted 2 years ago #

Sorry not yet, let me make sure the idea is practical and how long it takes to finish first. :)

I understand, no problem...

Ok, so I am still in doubt about which mobile plugin will suit my need. I have seen plugins that use external services like Wapple or Mippin and other plugins that are doing similar things but by themselves. The first category works with some kind of redirect (I guess) to this external provider while the second seems to depend on an alternative theme installed either in themes or in the plugins own dir...

Can you shed some light on the impact of W3TC on these two approaches?

Better yet... Could the Mobile Agents detection provided by W3TC be used to do the redirect instead of another plugin? That would be just perfect :)

Let's say my blog is on http://free-jazz.net then the stripped down (english) mobile version by Google would be on http://www.google.com/gwt/n?hl=en-GB&mrestrict=xhtml&u=http://free-jazz.net
How would I need to configure W3TC to do a mobile agents redirect to Google Mobile Version? Can this be done dynamically for all posts/pages or will it be a static redirect?
Frederick Townes
Member
Posted 2 years ago #

Right now, if you have a plugin that does theme switching you can reject mobile user agents using the appropriate field in the various cache types to get your theme working (without caching).

For plugins related to hosted services like mofuse, you don't need to install their plugin, you simply enter the domain name of the mobile version of your site on the page cache tab and the plugin will automatically redirect those mobile devices because that domain name is present.
RavanH
Member
Posted 2 years ago #

For plugins related to hosted services like mofuse, you don't need to install their plugin, you simply enter the domain name of the mobile version of your site on the page cache tab and the plugin will automatically redirect those mobile devices because that domain name is present.

Right, excellent :)

So will that be a static redirect (meaning no matter where the mobile agents lands on your blog, it will be redirected to that one URI) or is there some possibility to do dynamic redirecting (meaning the landing page can be incorporated in the redirect) like the google mobile version example above?

Thanks!
Frederick Townes
Member
Posted 2 years ago #

If a mobile user agent lands any page of your site and the redirect "Redirect mobile users to" field is set, the user will receive a 302 redirect to the domain name you specified there and for the same page they requested.

Consequently their browsing will continue at the new domain and the plugin (your original domain name) is then irrelevant.
RavanH
Member
Posted 2 years ago #

I'm still not clear about how this can be used other than for a complete redirect to a whole different website...

If I set "Redirect mobile users to:" to "mymobiledomain.com" without the "http://" (!) then mobile agents landing on myregularblogdomain.com will get redirected to myregularblogdomain.com/mymobiledomain.com and mobile agents landing on myregularblogdomain.com/about/ will be redirected to myregularblogdomain.com/about/mymobiledomain.com

But if I do use the "http://" then mobile agents landing on myregularblogdomain.com will get redirected to mymobiledomain.com BUT... mobile agents landing on myregularblogdomain.com/about/ will ALSO be redirected to mymobiledomain.com (without the /about/)

Is that how it is designed to function?
Frederick Townes
Member
Posted 2 years ago #

If I set "Redirect mobile users to:" to "mymobiledomain.com" without the "http://" (!) then mobile agents landing on myregularblogdomain.com will get redirected to myregularblogdomain.com/mymobiledomain.com and mobile agents landing on myregularblogdomain.com/about/ will be redirected to myregularblogdomain.com/about/mymobiledomain.com

But if I do use the "http://" then mobile agents landing on myregularblogdomain.com will get redirected to mymobiledomain.com BUT... mobile agents landing on myregularblogdomain.com/about/ will ALSO be redirected to mymobiledomain.com (without the /about/)

Is that how it is designed to function?

No.

I'm still not clear about how this can be used other than for a complete redirect to a whole different website...

Again, if you have a theme switcher plugin you can have a mobile theme(s) and according to the settings of that plugin, reject any mobile user agents in the reject list so that the plugin will work and direct them to the proper theme at your domain.

If you don't want to do that, then you can enter a domain name and send all the user agents in the mobile user agents list to an entirely different site (which means you probably need to have a service provider for that).
SteveFree
Member
Posted 2 years ago #

I'm having the same issues. Each time I activate either MobilePress or WPTouch, I get the mobile themes using my PC on IE and Firefox.....

http://wordpress.org/extend/plugins/mobilepress/
http://wordpress.org/extend/plugins/wptouch/

I posted the problem here:

http://wordpress.org/support/topic/346012?replies=1

But the WPTouch guys don't seem to want to touch that one :)
Frederick Townes
Member
Posted 2 years ago #

@SteveFree have you tried the solutions above?
SteveFree
Member
Posted 2 years ago #

@Fredericktownes - Which Theme do you recommend? I see several in the extend repository however I cant find one that specifies a theme based on User Mobile Agent
Frederick Townes
Member
Posted 2 years ago #

To host your own mobile theme, you need a plugin to switch themes based on user agent, for this I have no specific recommendation. I do believe there are some themes/plugin combinations that do the theme switch for you and for them to work, mobile users must be "rejected" from minify, cdn (unless using origin pull) and page caching.
SteveFree
Member
Posted 2 years ago #

I'm a writer not a developer so I need a simple solution. That's the whole point of wordpress right? It's easy to install, maintain and install plugins. Once you start talking about minify and user agents and theme switching.... i'm lost. Especially since the new mobile plugins don't expose a mobile theme to choose from (WpTouch and MobilePress).

It would be nice if you had just a checkbox on your plugin that would disable the entire plugin for mobile clients or at a minimum page caching. Mobile is probably just .5% of my traffic so that would be good enough for me :)

I've moved back to WP Super Cache and I'm back up and running for now. I do like your plugin for the database caching and other options but until I see something in your release notes that has a simple solution for Mobile themes I'll just be watching from the sidelines.
Frederick Townes
Member
Posted 2 years ago #

Right now if you use a service like mofuse, the plugin is already designed for that. There are plans to build in a mobile theme switcher, but everyone fails to see how many assumptions are required to make "simple" things. Anyway, for now, if you have a theme switcher, a mobile optimized theme etc you can add mobile user agents to the rejected field for any tabs that you're using, which until today has been fine for everyone else.
strictlyonlinebiz
Member
Posted 2 years ago #

I succeeded in getting this plug-in to work with WordPress Mobile Pack.
As Frederick Townes suggested, under Page Cache Settings, I added the list of Mobile user agents to the list of rejected user agents, then deleted everything withing the mobile user agent field.

I left the Redirect mobile users to field blank.

So far so good, it's working just fine.
Frederick Townes
Member
Posted 2 years ago #

Great.
Gravitydk
Member
Posted 2 years ago #

I just swapped back to W3 Total Cache, and also changed to WP Touch (for mobile users). I have done as Strictly suggested, too:

1) copied mobile user list from the existing field, provided on install
2) pasted into rejected user agents
3) deleted the mobile user list
4) saved.

I can confirm it's compatible.
Frederick Townes
Member
Posted 2 years ago #

3) deleted the mobile user list

This step is unnecessary, but I'm glad you're all set now.
Jakets
Member
Posted 2 years ago #

So I have done whats been listed here and it works fine. There is one thing I noticed however. When I add the mobile list and save, if you view the page in IE8 (possibly other versions as well, I haven't tested) it says: Page Caching using disk (enhanced) (user agent is rejected)

If I remove them its fine again. I checked my user agent and it displays as: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

I tried removing IEMobile from the list and that didn't help, not sure which of the 101 agents is causing it not to display a cached page to IE8, but if anyone knows that would be great!
Frederick Townes
Member
Posted 2 years ago #

Page Caching using disk (enhanced) (user agent is rejected)

I'm not really sure what user agent you're trying to match? In general that list of devices in the mobile list in the plugin is exhaustive. If you're specifying something that's not listed there, it's not confirmed supported.
Jakets
Member
Posted 2 years ago #

@ fredericktownes: Nope, looks like you didn't fully understand what I was saying. When I add the mobile list to rejected clients (so as not to serve a cached page to mobile devices) Internet explorer 8 also does not receive a cached page, but Opera, Firefox and Chrome all do like they should. One of the mobile agents is also causing IE 8 to be considered a mobile client and not receive a cached page. I'm trying to figure out which one to remove so that IE users still get a cached page.

Thanks.
Frederick Townes
Member
Posted 2 years ago #

What I'm trying to indicate is that you *must* have specified a user agent similar to MSIE, which is the root of the matter.

If you re-purpose the user agent list provided in the plugin this case does not exist; this has already been tested and proven.
Jakets
Member
Posted 2 years ago #

@ fredericktownes: I'm simply copying and pasting the user agents from the mobile detection list. I haven't added any manually at all. If I remove those and save, it doesn't show the user rejected, but if I add them it does. So its one of the stock 101 from the mobile detection list.

This is the stock list:
bot
ia_archive
slurp
crawl
spider

With that it works fine (obviously my mobile version doesn't work because I haven't added the mobile ones)

and here are the ones I added from your Mobile user agents list:
2.0 MMP
240x320
ASUS
AU-MIC
Alcatel
Amoi
Android
Audiovox
AvantGo
BenQ
Bird
BlackBerry
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
SIE
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
iPhone
iPod
nokia
portalmmm
vodafone

Once I add this IE8 says user agent rejected and serves up a non cached page (works on all the other major browsers, haven't tested below IE8 however). Let me know if I'm somehow wrong, but like I said, I didn't add anything to that list, its a direct copy paste of your default mobile agents.

Thanks.
Frederick Townes
Member
Posted 2 years ago #

I am still not able to duplicate this. Can you try clearing cookies in your browser and make sure you're not logged in to WP Admin?
Jakets
Member
Posted 2 years ago #

I tried that just now and still no luck. Feel free to check for yourself: http://farmvillefanatic.com/

Let me know if it shows user agent rejected for you on IE8. My rejected list is exactly what I posted above.

Thanks.