WP-Rocket doesn’t work well with this plugin

Also, I have read that your plugin considers “mobile” to mean both tablet and mobile. However, we have found that the tablet view is inconsistent. Just now I found that the main page is being served for tablet, and the mobile page (which also has a tablet view) is not being served for tablet. Mobile page is only being served for mobile.

So I am not sure if “mobile” truly means “mobile + tablet” or just “mobile.” Please advise.

Hi @wordpressdharma

I suggest reading here: https://www.ads-software.com/support/topic/the-mobile-pages-are-only-for-backend-and-be-careful-to-the-cache/

For simplicity let’s consider the page https://yoursite.com/page-example/

1) You don’t need to cache https://yoursite.com/page-example-mobile/, because this page doesn’t exist for not logged-in users. The only page that exists is https://yoursite.com/page-example/.
If WP Rocket caches https://yoursite.com/page-example/ making 2 versions, one for mobile and the other one for desktop, it’s ok.
2) Imagine you have the page https://yoursite.com/page-example/ with the text “This is the desktop content”, then you create the mobile version that if you are logged-in you can reach https://yoursite.com/page-example-mobile/ (all people will see it always at https://yoursite.com/page-example/ also on mobile devices). Let’s say on the mobile version you replace the text with “This is the mobile content”.
This plugin works in this way: when you visit https://yoursite.com/page-example/ with a desktop device, you will see “This is the desktop content”. When you visit https://yoursite.com/page-example/ with a mobile, you will see “This is the mobile content”.
Nothing else. This plugin does only that.
The page layout and style will depend on CSS and screen size. This is not something that is managed by Specific Content For Mobile. You need a responsive design to adjust your layout on mobile devices.
3) The only operation that this plugin does with the trash is the following:
– If you trash https://yoursite.com/page-example/ it will trash https://yoursite.com/page-example-mobile/ too
– If you trash https://yoursite.com/page-example-mobile/ it will disconnect the relation between the trashed page https://yoursite.com/page-example-mobile/ and https://yoursite.com/page-example/
– If you untrash https://yoursite.com/page-example-mobile/, it will check if it’s related to a desktop page, if so, it will create again the relation between https://yoursite.com/page-example/ and https://yoursite.com/page-example-mobile/
– When you delete the plugin, it disconnects all relations between desktop and related mobile versions. It does absolutely nothing with the trash.

Before investigating deeper, please let’s be sure you are completely aware of what the plugin does and what it can not do.

After clarification, let me know the issues you still have.
I had already tested WP Rocket and I had no issues.
But of course, if you still have issues, I will install WP Rocket again and check it.

Hi @wordpressdharma
this plugin uses the core function wp_is_mobile. You can find here the details about this function: https://developer.www.ads-software.com/reference/functions/wp_is_mobile/
From the official codex source: “Test if the current browser runs on a mobile device (smart phone, tablet, etc.)”.

However, if you want to exclude tablets, you can add this line of code in your wp-config.php:

define( 'SCFM_EXCLUDE_TABLETS',true );

Put it before the comment /* That’s all, stop editing! Happy blogging. */

You would have something like this:

define( 'SCFM_EXCLUDE_TABLETS',true );
/* That's all, stop editing! Happy blogging. */

I think your issue is related to responsive design. As said in my previous comment, this plugin only replaces the content with specific content for mobile, but then the layout and style depend on the CSS and the device viewport size.

If on desktop you want the text “This is desktop” and on a mobile device, you want the text “This is mobile”, this plugin will help you. If you want a different style, this plugin will not help you. You need that the design is fully responsive.
The scope of this plugin is replacing heavy content with lighter content for mobile devices. And it also helps you if on a mobile you want for example a block in another position, or completely remove some images instead of only hide them, but you need responsive design to have nice layouts on all devices.

Hi Jose,

I understand what you are saying. Our Divi theme is fully responsive.

I guess the main issue we are experiencing is that the plugin is causing a lot of crazy things that are happening.

Just this morning I went to our website and was horrified that the main page on desktop was showing the “desktop” view from your private mobile page.

To explain, the only reason we are using this plugin is exactly what you intended it for. We have large video background files that we don’t want to be downloaded for mobile, and then hidden, because there is no reason to hide those videos if they have already been downloaded. So we wanted to completely eliminate those videos from the mobile page so they are never downloaded. In addition, we deleted any desktop elements that are not seen on mobile. So this accomplishes what you are saying: All desktop elements that are not visible on mobile are deleted on your mobile page so they never get downloaded and thus save loading time.

However, our constant experience is that SOMETIMES (and the word “sometimes” is important here) when we save the mobile version, it somehow overwrites the desktop version. This is what happened when I discovered it this morning. The desktop version on our private mobile page is pure junk, because it will not be seen. Yet that is what was showing live all night!

To solve this problem I had to go into the real desktop page and save it — TWICE — before the correct desktop version would show live. This is a very strange bug. It means that whenever we edit the mobile page and save it, we could be actually somehow changing our live desktop view to the junk desktop view on the mobile page. This is a serious problem.

Please advise.
Thanks,
Lucas

Regarding trashing the mobile page and your comment above:

Yes, we understand all this. But the problem was: We had trashed the mobile page permanently. And there was no way to recreate a new mobile page. Your plugin would not allow it. It only gave the alert that “Page not found, did you delete it?”

Yes, we had deleted it, and there was no way given to create a new one. We could not undelete the page. So we had to completely uninstall the plugin and start all over.

Hi @wordpressdharma
thank you for the information.

You wrote “However, our constant experience is that SOMETIMES (and the word “sometimes” is important here) when we save the mobile version, it somehow overwrites the desktop version.” => That SOMETIMES make me think about something related to cache issues (WP Rocket or/and the inbuilt cache by Divi).
Are you completely sure the cache is distinguishing between mobile cache and desktop cache? This is very important.
Consider this scenario if the cache doesn’t distinguish between mobile and desktop. You have a mobile version of https://yoursite.com/page-example/.
The first visitor visits the page https://yoursite.com/page-example/ on mobile. The cache is built and stored. Then all the other visitors will see the mobile version, even if they visit the page with a desktop.

You wrote “It only gave the alert that “Page not found, did you delete it?”. I can ensure you that this message doesn’t come from my plugin. You will not find anywhere in the code anything that gives this message or that don’t let you create the mobile version.
The code of the plugin only doesn’t show you the button or the action link to create the mobile version in case you already have a mobile version, nothing else.

Please, before we go ahead I would like you to confirm the following points:
1) You understand that you don’t need to cache https://yoursite.com/page-example-mobile/. The message given by WP Rocket for that page is not a problem, because no logged-in users don’t go to https://yoursite.com/page-example-mobile/
2) You have set up WP Rocket to distinguish between mobile and desktop, so you have enabled “Separate cache files for mobile devices”. This is very important.
3) You don’t have other page caches, as e.g. CDN cache of the entire pages that don’t distinguish between mobile and desktop.

In any case, even after doing many tests, I can’t reproduce the issues you described. On my installation, all works right with WP Rocket.

If you want you can create a copy of your installation with All In One WP Migration and provide me the exported file. Then I can install it on my computer and see with my eyes what’s going on with your plugins/theme. You can use my email [email protected] for providing me the exported file.

Thanks for all this info!

Yes, we have Rocket set to “separate cache for mobile”.

One thing you said above confused us: You said:

You have a mobile version of https://yoursite.com/page-example/.
The first visitor visits the page https://yoursite.com/page-example/ on mobile. The cache is built and stored. Then all the other visitors will see the mobile version, even if they visit the page with a desktop.

What do you mean “all other visitors will see the mobile version, even if they visit the page with a desktop”? Surely people who visit our site on desktop will only ever see the desktop version.

Thanks,
Lucas

@wordpressdharma
No, it doesn’t work as you think if you don’t distinguish between mobile and desktop cache. The cache must work distinguishing between mobile and desktop.
As a default, almost all cache plugins, including WP Rocket, don’t distinguish between mobile and desktop cache. If you have a CDN with page cache enabled, usually as default you have a caching system that doesn’t distinguish between mobile and desktop cache.

Without distinguishing between desktop and mobile cache, if you visit the page https://yoursite.com/page-example/ for the first time with a mobile device, the plugin will replace the desktop content with the mobile content and the cache will be stored on the server with the mobile content.
When you visit it a second time with a desktop device, if the page is served by the cache that was created with the mobile content, the user will still see the mobile content.

Don’t confuse the content that is taken from the database or from the cache, with the design that depends on the content itself, but also by the CSS and the device viewport.

Please confirm also the points 1 and 3

1) You understand that you don’t need to cache https://yoursite.com/page-example-mobile/. The message given by WP Rocket for that page is not a problem, because no logged-in users don’t go to https://yoursite.com/page-example-mobile/
3) You don’t have other page caches, as e.g. CDN cache of the entire pages that don’t distinguish between mobile and desktop.

Point 3 is very important.

Jose,

OK, I’m trying to understand, please bear with me.

First, yes, Rocket does seem to have separate cache for desktop and mobile, as I pointed out earlier. This is a new feature that came out perhaps a month ago. And yes, I have check the box to enable “separate cache for mobile”.

As for point 1 above: yes, I understand that your mobile page cannot be cached by Rocket. Indeed, there is no option to do so, and it is greyed out.

Point 3: We do use Rocket’s “individual page” cache, which is set on the desktop version of the page. There is no way to do an “individual page” cache on your mobile private page, as stated above.

Other than this, we are also using Rocket’s own CDN, which is Stackpath. So we do not know how this works.

@wordpressdharma
thank you for the information.
I think WP Rocket itself is not causing the issue because you have set “separate cache for mobile”. I’ve tested WP Rocket in the past with this option enabled and all was working right.

So, for me the most probable causes are
1 conflicts with other plugins
2 the CDN cache that doesn’t distinguish between desktop and mobile
3 you have an additional server cache system

I can check the first point if I have exactly your set of plugins and the theme and the same settings. It would be great if you can export the installation with All In One WP Migration. If you can’t because you have sensitive information, I totally understand it. In that case, you could import the exported file on a new installation, delete all the sensitive content, and export it again. At least I would have exactly the same plugins, the theme and settings.
If you can’t do it, please give me the list of all active plugins. It will be less easy, but I can try to reproduce the problem.

About point 2, I also don’t know if Stackpath distinguishes between mobile and desktop page cache. It could also be that you don’t have full page cache, but only resources cache (images, fonts, stylesheets, scripts…). In that case, the CDN is not the root cause.
In any case, if possible, you could disable Stackpath for a couple of days and see if you still have the problem.

About point 3. Be sure your server (it looks Liquid Web) doesn’t save the pages in the server cache.
Check also the folder wp-content/mu-plugins. Many servers write code in that folder to manage the server cache. If you find some files there, check that they are not for server cache.

I @wordpressdharma I will close this thread for inactivity. If you still have issues don’t hesitate to open a new thread.

For some reason, in the wp rocket plugin
When I select “enable mobile caching”, my page doesn’t show up on mobile devices
It only shows up on mobile when I don’t test this item
You guys help me with this problem
For the time being, I have to turn this mode off so that the website can work on mobile devices but it runs quite slowly

Hi @toantoan
Have cleared the cache of WP Rocket?
If the page is shown without problems without cache, maybe when WP Rocket created the mobile cache the page had a problem that was “frozen” in the mobile cache. First, try deleting the cache if you haven’t done it yet.

Can you share the URL of the page where you have problems?

I have cleared the cache many times but it still fails
For you to understand the problem, now I will turn on the memory mode for mobile devices
When you access the device you will understand better
https://tolosy.com

this is the image
https://scontent.xx.fbcdn.net/v/t1.15752-0/p280x280/122788728_2702631183310619_8696740291208536186_n.png?_nc_cat=108&ccb=2&_nc_sid=ae9488&_nc_ohc=mHFcOzQfsPwAX8YSg-o&_nc_oc=AQlCUb2qwv6Qw9CyRwuGs-XJi7ju_SBlUx6Y0-uwlm-a_bi7U0IslKs-z9JEEiX5xwg&_nc_ad=z-m&_nc_cid=0&_nc_ht=scontent.xx&oh=6337ef7a30df0ead2dfc82714de9f4ff&oe=5FC07250

this browser is also the same as the mobile device
https://scontent.xx.fbcdn.net/v/t1.15752-0/p280x280/122858093_2766811786900819_2532926867644653774_n.png?_nc_cat=104&ccb=2&_nc_sid=ae9488&_nc_ohc=sLfB5APe6AoAX8OlJzJ&_nc_ad=z-m&_nc_cid=0&_nc_ht=scontent.xx&oh=5df457460d2c938d5014cd5c82d47817&oe=5FC1DAD2