I believe this conflict with Super Cache is documented to some degree. :)

I'm running 2.8.4 with the latest of Super Cache and the latest of this plugin.

This is the only setting that works for me so try it:

wp dashboard > Appearance > Mobile Switcher

Set it to Browser Detection ONLY and NOT BOTH.

See:

http://www.thevegasgeek.com

HTH :)

Hi,

Yea I've been using the same settings. Unfortunately it's not working for me. mobile users are getting the regular page only, now.

I guess something happens when it's cached by super cache and then it appears to desktop users as the mobile theme.

Disappointed I must say as it was a great plugin for using on gprs.

Will deactivate now as I don't want desktop users getting messed around

Interesting....

(1) In Super Cache make sure the check box is cleared for Mobile device support. This plugin uses its own caching so Super Cache should NOT cache Mobile Devices

(2) It's a shame but you could always edit “lite_detection.php” James would be the expert on that and will probably ask you a bunch of technicall questions. :)

(3) I just thought of something...it would be nice to have an error log created only when you want it. Ideally, it would log the user agent and try and identify the phone. Gather enough data on "failed Mobile Themes Display" to permit you to either edit the detection file or see whats going on.

Yea it's a shame.

I need super cache on. So editing the htaccess is the only option. Would like to hear from some others, or someone who's done this and can say it's been successful. Or not as the case maybe?

Or even if there's a link to another discussion about this on the forum.

Meanwhile I'll disable mobi :(

Wish I could help more however Super Cache is still ON for your desktop site with the check box cleared for Mobile Devises. Try it and see what happens? Thats exactly the way I run it.

No worries thanks for the advise.

I've tried checking it on and off. Uninstalling the plug in. etc. Only way it will work for me is if Super cache is on half on mode.

Or possibly if I insert a change to httaccess. Which I don't want to touch, unless someone feeds back positively about it.

Last time I didn't notice desktops were getting mobile mode for 2 days :(

Anyway, I'll hang tight for a while and see if support or anyone who's tried the htaccess with supercache onfull can tell of their exp.

Thanks again

Undersstood and it's a shame. :(

I don't give up easily. :)

I presume that running the Launch ready.mobi benchmark and phone preview with this plugin via Appearance > Mobile Theme produces OK preview results for the Phones they offer? It's easy to miss since you need to scroll the page down.

Since we have a similar set up and if you can find one of your Mobile Users who is still getting the desktop theme, send them to my site via their Phone. I'm curious and would like to see if the Mobile Theme and autosence displays properly. ---> http://www.thevegasgeek.com/

James should be around.

This is a known issue of wp-super-cache. We are working on this, but there is no release date set. Let's just say that we won't release until it really works ;)

Hi guys,

I have successfully run WP-Super-Cache and the dotMobi plugin myself, but it required two things:

1) making small changes to the Super-Cache source code (so that the caching is aware of the switching algorithm and interstitial pages)

2) making changes to .htaccess or nginx conf file (so that you are not routed straight through to an .html file if you don't have the wpmp_switcher cookie yet)

Unless you are comfortable doing both these things and fiddling about, I'm afraid you should probably wait.

My intention is to have the mobile plugin detect that Super-Cache is installed and provide instructions as to what to do that are specific to your particular install.

Suffice to say, Super-Cache provides another moving part in a complex piece of machinery and I would be cautious to provide blanket advice at this stage.

I should also say that the 'mobile' checkbox in the Super-Cache admin page is not all that is required. That adds a separate set of user-agents to the .htaccess file for device recognition and may cause wholly unexpected effects.

This entire area is next on the list of things to tackle. Please stay tuned for v1.2 - I'm hoping to get something out in mid October, travel permitting.

Thanks
James

A long time has gone now, but I assume this is still an issue for some. During these months Super Cache added a hook for plugin developers and now we have been able to write a small extension for WPMP that plugins into that. With the next release, coming out in a few days, you will be able to use WPMP with Super Cache instantly, without any changes.

We are also working with Donncha (super cache author) to make the integration tighter and better, so expect further improvements in the following weeks.

A preview note on my personal blog: Making Super Cache and mobile work well