Support » Plugins and Hacks » [Plugin: W3 Total Cache] MobilePress compatibility

Viewing 15 replies - 1 through 15 (of 40 total)
  • And is it compatible? Anyone tried?

    Right now it’s not compatible although the latest release of W3TC does have a number of new mobile options.

    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?

    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.

    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? 🙂

    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. 🙂

    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?

    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.

    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!

    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.

    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?

    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).

    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 🙂

    @stevefree have you tried the solutions above?

    @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

Viewing 15 replies - 1 through 15 (of 40 total)
  • The topic ‘[Plugin: W3 Total Cache] MobilePress compatibility’ is closed to new replies.