Plugin Author
Scott
(@scottsweb)
This is mentioned in the documentation of the plugin.
Because mobble works on the server side the output is easily cached by caching plugins. If a mobile user generates your W3 total cache it is possible a desktop user will actually see the mobile tweaks.
If W3 total cache has an option to not skip PHP then it might still work.
To truly solve this problem, mobble needs to be re-developed using JavaScript. This is an ongoing idea and work has not yet started.
Thanks for the quick response and info Scott. I will take a closer look at the documentation. In case it doesn’t say there, do you have any further advice for people who want to use mobble but also to use performance speeder-upperers of some kind?
I was looking at the super cache plugin but presumably that would have the same issues?
Do you know if there are any w3tc settings that can be safely used alongside mobble?
If push comes to shove I will choose mobble over w3tc in this case, but it would be a shame not to optimise performance as much as possible.
Thanks.
Plugin Author
Scott
(@scottsweb)
Unfortunately most caching plugins will suffer from the same problem.
This very issue is also why I have not updated mobble that recently. I have started looking at some JS tools which may help:
https://github.com/conditionizr/conditionizr
https://github.com/WhichBrowser/WhichBrowser
But have yet to determine a neat strategy for integrating this with the current plugin.
Thanks for the feedback
Any news about this issue?
Plugin Author
Scott
(@scottsweb)
No further updates at the moment.
Can you not just enable the “User Agent Groups” in W3TC? The default “low” and “high” groups should segregate a good deal of your mobile traffic, then you can add additional groups as you find the odd user agent that loads incorrectly. The end result should be that any mobile user agent uses separate W3TC cache files.
I know for sure that this works with older browsers where we have some IE-specific HTML. If an IE user happened to build the the cache it looked weird for all other browsers. Once we created the appropriate user agent group, this was no longer a problem. I’m hoping it works the same for mobble.
We just went live with this configuration this morning. We’re in a high-volume season so I should know fairly soon if it’s not working. I’ll post back in a few days if we have problems.
Plugin Author
Scott
(@scottsweb)
@wstringer2 Thanks for the info, it sounds like you have found a possible solution.
I have not used W3TC for quite some time so it’s good to get input from folks using it day to day. Look forward to more news.
Thanks again.
You’re welcome Scott…thank you for the nifty plugin!
I think this works for the most part. We are having some issues where W3TC is serving images to desktops that were cached by mobile devices, so they’re grainy. This only happens from time to time though.
I’m not positive, but I’m pretty sure this issue could be solved by creating user agent groups in W3TC based on the user agents returned by your plugin.
EXCUSES NOT IN THE GOOD FILE !
Is mobble still being maintained? Any updates on this issue?
Plugin Author
Scott
(@scottsweb)
It is being partially maintained. There is a more recent version of the plugin on GitHub: https://github.com/scottsweb/mobble
As I do not use the plugin myself at the moment, I have not released an update here. I am hoping to get feedback on the GitHub version before pushing an update on .org.
Plugin Author
Scott
(@scottsweb)
As for updates on this issue, there is a possible solution above.
Hi thanks for your response. Well there is an ability to set user agents in w3tc, but what should i set for the mobile devices, so that these pages wont be cached? Or am I understanding it wrong?
Thanks
Are the groups are already filled in, fixed it for me!
Plugin Author
Scott
(@scottsweb)
Sounds like you fixed it then? Would you mind sharing your process for other people here.
If you need specific help with W3TC I recommend reaching out to the plugin author.
This thread is now closed.
