AndreaTrasatti

donncha – if you think you will add a function that would allow a plugin like WPMP to update the user-agents and prefixes (as you already do) and then force an update of the rewrite rules, I think that will be interesting for us to use.

Either way, we would appreciate if you would refer to our plugin for the improvements you brought into Super Cache. We want to release a new version of out plugin to use the actions around the weekend as well, so your mention would be very welcome.

In general, if the mobile plugin is powerful enough and does per-device adaptation, you would need to use a cache key per device. My experience is that most plugins produce only 1 output. The most advanced like the Mobile Pack and Mobilepress have 2 or 3 presentations and all devices fall in one of those groups based on the features. My suggestion is that you do the same, i.e. define some groups for devices and use a key for those. This will reduce the cache replication and the produced pages will still be good enough.

At this stage we have a separate file to manage device group detection, see group_detection.php, but we are thinking of bringing together these functions in the lite_detection and make it an integral part of the plugin (rather than the themes as it is now).

The way I’ve done it now in the mobile pack I am completely overriding your detection (i.e. the admin will NOT turn on the mobile checkbox in the admin and the mobile pack plugins in automatically using your add_cacheaction()), so I am not sure if I need all these filters that you are adding. From my perspective, unless these filters let the other plugin affect how you cache the files, I do not need them, as I am happy to use my own detection. My view is that the detection should be in the mobile plugin and your cache plugin should offer a way to plugin (as you already do with add_cacheaction); anything that you do beyond that is a nice-to-have for plugins and themes that do not want to deal with detection (although IMHO they should!).

Finally, about modifying the .htaccess, adding checks such as the presence of the UAProf header is very simple and yet will catch most mobile devices that respect the WAP 2 requirements (not iPhones and Androids, I’m afraid) and that is still the vast majority of the devices on the markets worldwide.

Hi Donncha,
these are very good changes, thank you. I will look into the code as soon as possible and start playing with them. When are you planning the next official release that will include these?

Speaking of the function “update_cached_mobile_ua_list()”, if you look at our lite_detection.php you will notice that we use a few methods to detect if a visitor is a mobile browser. Your approach, which is very valid and will catch most browsers, is still not as complete. I wonder if we can bring any consolidation here and make sure all plugins that want to do mobile can use the same code-base.

I started a separate thread for W3 Total Cache and mobile integration and I will recommend some changes. Bringing the two caching plugins in line would make it easier for developers, of course.

WRT “late init”, I see a mention in your changelog, I’ll have to look at it. My idea would be to make the cache store the mobile pages in a separate direcory (say hostname/mobile/path/pagename/index.html) and then add new rewrite rules to pick up the appropriate path. Of course as you say, changing those rewrite rules can be dangerous although 99% of users will likely use the stock rules. On the other hand, if you now allow plugins to modify the list of user-agents for mobile, then the rewrite rules should be modified accordingly.

EDIT: Fixed a couple of typos

Has there ever been a solution?

Well, Beta 1 was just released and it’s announced as an early beta. I’m afraid we have not looked into it ??

You are welcome to suggest changes to make it work, but as it stands, we are not compatible with 3.0, yet.

I am sorry for any trouble with Google, of course we don’t have control over what they do with their index.

Could you explain better what you mean about the noindex? Was it an attribute of the anchor? Was it in your robots.txt?

One thing that we could do for the future is make the switcher link to the mobile version a nofollow so that Google and other robots will not follow it. Of course this means that they will not index your mobile site unless you specifically tell the robot to do it. In theory Google and other search engines say they will figure out themselves if the site is mobile or not, obviously it’s not as smooth as they say ??

Hello,
could you let me know your settings in the “mobile switcher” panel?

The easiest way would be via SSH or FTP. Go in your wp-content/themes directory, you will see four directories all starting by “mobile_pack_”. If you remove those you will have removed the themes.

If I understand correctly when you say you tried with Filezilla you tried to access via FTP. Is that right? I assume you installed the plugin and themes via WordPress. If you do not have permissions to remove the files you should talk to your hosting company.

Hi,
sorry for the late reply. What do you want to do? You can either create a widget (probably the most elegant solution) or you can modify the themes. The themes are installed in your themes directory. The best place is probably the mobile_pack_base. You can create your own tiny PHP file that displays the categories that you want and then include it in the right place or modify the theme. Of course if and when we release a new theme you might get out of sync (although we never overwrite your files unless you ask for it).

I have just finished and committed to SVN an implementation of the new actions of WP Super Cache that make the mobile pack work nicely with it. Unfortunately it’s still “just” the partial cache as Super Cache does not let me control how the local files are stored.

See here the changes if interested: https://plugins.trac.www.ads-software.com/changeset/234095

Next thing is make the Mobile Pack work with W3 Total Cache.

For both WP Super Cache and W3 Total Cache, I think you can safely move to our detection approach as implemented in lite_detection.php as it is more up-to-date than Alex King’s and we want to keep it updated.

I adapted the widget to use the new classes. I can send it to you, if you wish. I am going to e-mail the author and provide it as well, if he wants to update the official plugin

Hi Donncha,
I am sorry I am about to leave for a 2 week holiday and will not be able to debug this for you, but I will help you as soon as I’m back.

I hope this is OK.

I really think it’s an issue with that installation, as I cannot replicate on another hosting I have, but I would not be surprised if a similar setup is present in other hosting companies.

Hi,
bear with us while we try to reproduce the issue.

A couple of quick questions, are you using device detection alone or also domain mapping? Would you be able to give me your blog’s address, so that I can see it on my mobile?

Thank you

Hello,
could you give us some more details? What Blackberry are you using, exactly?

Which theme did you enable? Did you enable the Nokia theme? Which version of the plugin?

Thank you

Guys,
sorry about the trouble, I have a hot fix that is just awaiting the automatic script to publish it, so should be online any minute now.

Let me know if you have any further issues.

Any updates on this? Come on, how can a plugin disappear?