Pothi Kalimuthu

Same issue. Went back to version 1.9.100 that was the last working version. Disabled auto-update for this particular plugin.

Glad to know the plugin still works. Thanks for the heads-up.

Unfortunately, not with this plugin.

Thank you for your time to send positive vibes across!

You are right. I just checked. iPads are no longer detected with the latest version of iPadOS and on Safari and on DuckDuckGo browser. On Google Chrome, it is detected correctly, though. Unfortunately, I don’t know any alternatives.

• This reply was modified 2 years, 7 months ago by Pothi Kalimuthu.

You are right. wp_is_mobile indeed covers mobile phones. We don’t need a custom function. For a list of available core functions, please see https://demo.mobiledetect.net/ . Basically, wp_is_mobile and isMobile() have the same functionality.

• This reply was modified 2 years, 7 months ago by Pothi Kalimuthu. Reason: Removed iPhone detection example
• This reply was modified 2 years, 7 months ago by Pothi Kalimuthu.

Ok. As mentioned in the other thread, the cache is cleared very late in the hierarchy of events / hooks / actions, after the plugin tries to preload a post.

In order to replicate, I turned on debugging on LSWS server, visited an existing post (to generate the cache), updated the post to trigger pre-loading. What I saw in the LSWS server log is… the request from this plugin gets through at first (I could see a “hit” in the response header. Then, LSWS clear the cache.

Since, a caching plugin (such as LiteSpeed Cache) has more control over the order of actions / hooks, this plugin (preload fullpage cache) is unlikely to override such order.

I saw a not-so-practical workaround. Please see this… https://wordpress.stackexchange.com/q/56266/9584

• This reply was modified 2 years, 9 months ago by Pothi Kalimuthu. Reason: Fixed the link to the other post

From what I understand (from server’s debug log), when we publish a post or when we update an existing post, the request from our code (via add_action) gets executed at first. Only then, LSWS flushes the cache. Let me dig further, by looking into the response headers (of the request that tries to preload the post).

Unfortunately, I couldn’t figure out what has gone wrong when working with LiteSpeed server / plugin. I turned on debugging on the LiteSpeed plugin and simulated the headers (within preload fullpage cache plugin) from a real world browser too. No luck so far. Since, the cached content isn’t stored within WP filesystem, it is hard to troubleshoot. I will leave this issue open. If there are any further ideas to try out, please let me know. I have an OpenLiteSpeed server to test drive for now*.

For others, this plugin still works with WP Super Cache and WP Rocket plugins. I will update the plugin README file to reflect the incompatibility for now.

Thanks.

• This reply was modified 2 years, 9 months ago by Pothi Kalimuthu.

I confirm that the plugin doesn’t work with LSWS and its cache plugin as of this writing. I will look into it.

Thanks for the review. Happy blogging!

So this means that, simply by having your plugin installed, I have all the other methods available to me in Mobile_Detect.php ?

You are right. There is a difference, though. Mine uses a different class name to avoid conflicts with other plugins that include Mobile Detect library.

The plugin itself is dead-simple to link Mobile_Detect.php and wp_is_mobile. If you don’t want wp_is_mobile to interfere, please do not install this plugin. Instead, download your own copy of Mobile_Detect.php file and use it as you wish.

Some caching plugins use Mobile_Detect library as well. So, you may wish to use your own class to avoid conflicts.

Indeed. There is an isiOS() method. You can see the list of examples at https://mobiledetect.net/ . You can play around with the demo at https://demo.mobiledetect.net/ .

We can’t use a Nginx plugin in a server where LiteSpeed is installed as the web server. Similarly, we can’t use a LiteSpeed plugin where Nginx is installed as the web server. What web server do you have or use?

Hi @antonio24073 ,

Thanks for creating the feature request. My apologies, if my reply sounds rude.

This plugin was created for a specific use-case as mentioned in the readme…

Preload Fullpage Cache plugin is created to address a unique scenario in high traffic sites where the visitors rush to the website upon publishing the new post, even before the cached version of the post is ready to serve the initial traffic spike.

Most (full-page) cache plugins have a preload functionality that preloads all the posts of the site. For example, WP Fastest Cache, WP Super Cache, WP Rocket, etc. So, I am unlikely to add it as a feature in this plugin. Of course, it is a good idea to have a separate plugin with the name “Preload All Posts and Pages” and copy whatever the logic from existing plugins to that new plugin.

If I may ask you, why would you like have a separate functionality to preload all the posts and pages when it already exists with certain full-page caching plugins?

Thanks for the suggestion, anyway.

Kind regards,
Pothi.