Background of the issue:
I am using WPML with the multi-currency feature on my site hidden link. I want to ensure that pages are cached properly when accessed in different currencies.
Symptoms:
The cached versions of pages aren't kept in cache for a long time. Pages are a 'miss' after a few loads and need to be cached again. This seems to happen when a page is loaded in a different currency.
Questions:
Why aren't pages cached in multiple currencies?
How can I ensure pages are cached properly for each currency and kept in cache for a longer time?
1. On your home page, I see cache 'hits' consistently, when reloading the page;
2. When switching currencies on the website's top-bar, I get a 'miss' for 'x-litespeed-cache'and 'x-qc-cache' for the first and sometimes the second time the page is loaded;
Does that describe the issue you are having? I need a consistent way to reproduce the issue, so I can escalate and describe it to developers. This seems to be one.
P.S: an important detail, is that the website didn't load the CAD currency. In product pages, it always showed USD, despite switching to CAD. Are you aware of that?
Sorry for the late reply, somehow I didn't got the email notifications.
You are right about the currency switcher not working. I selected the option for geolocalisation and the currency is auto-detected. If the user wants to change the currency, he needs to change it by changing the country in the billing address. Any way to bypass this?
I'm testing using a VPN to change the currency. Usually when I load a page in incognito, then close the incognito window and open a new one, the page is a "hit". But when I change the currency in another session/window, I'm getting a "miss".
From my understanding, the cache should be working with your multi-currency feature. Meaning that if an user is loading a page in CAD and then another user is loading the same page in USD, for following CAD and USD users will be served their respective cached pages, without having to load an uncached page. Is this the expected functionnality?
Right now my guess is that each time a page is served in a different currency, the cache is reset.
New threads created by Lucas Vidal de Andrade and linked to this one are listed below:
The fact that currencies are not changing, doesn't seem to be directly related to the caching question, even though they're involved to one another. In this case, so we don't mix the issues and can proceed productively, I've created a new ticket to address that. I'll ask for more information there:
The only way I was able to get a 'miss', was when switching currencies on the website. The currency switcher is still there, even though it's not going to be used on the website (at least in the way settings were configured when I last checked it), as there are no scenarios that allow switching currencies.
How are you going to proceed, regarding the currencies? If the switcher is no longer needed, how can I reproduce the issue?
Thank you for clarifying. So the issue would happen if a user switched places geographically, or switched his VPN settings? Since the action of changing currencies manually is not on the website. I'm trying to understand when the problem would be relevant in a real use-case. I understand when the information is not properly cached, what I don't understand is what's the impact of it and which difficulty we are actually solving.
I'll re-analyze the website and get a second opinion with my colleagues. I'll get back to you as soon as I hear from them.
- An user is loading the page for the first time. The first load is longer, since the page is not cached yet.
- Subsequent users will be served the cached version of the page, which is faster.
- The pages are cached in both currencies, meaning that the USD cached pages will be served to everyone, except the Canadian customers, that will see the CAD cached pages.
- The pages should remain in cache until a certain event happens, that will reset the cache (for example, an inventory update, a plugin update, etc...)
Am I correct?
For example take these 6 different users, loading the same page, one after the other. This is the caching scenario I'm expecting:
User #1 (Canada): Loading the CAD, UNCACHED.
User #2 (USA): Loading the USD: UNCACHED.
User #3 (Canada): Loading the CAD, CACHED (faster).
User #4 (USA): Loading the USD: CACHED (faster).
User #3 (Canada): Loading the CAD, CACHED (faster).
User #4 (USA): Loading the USD: CACHED (faster)
And this is what I think is happening right now:
User #1 (Canada): Loading the CAD, UNCACHED.
User #2 (USA): Loading the USD: UNCACHED because the previous user was in a different currency.
User #3 (USA): Loading the USD, CACHED because the previous user was in a SAME currency.
User #4 (Canada): Loading the USD: UNCACHED because the previous user was in a different currency.
User #3 (Canada): Loading the CAD, CACHED because the previous user was in a SAME currency.
User #4 (USA): Loading the USD: UNCACHED because the previous user was in a different currency.
As you can see in my example above, caching doesn't make sense in this situation, because the cached version is generated each time an user has a different currency.
It's maybe because we are using CDN too (Quic.Cloud and Cloudflare). Can you test this directly on our staging site, by disabling all the plugins and using the theme of your choice? This will be more accurate.
What I need to do, is to recreate the issue on our own controlled environment, without external influences. This way, we can confirm what's the expected behavior of WPML in conjunction with Litespeed. Recreating the issue on staging is the opposite of that, as there are many external influences and we won't know 100% what is the cause. With that, I can escalate both your website and the Sandbox, so our devs have a control group to compare your website with.
How can we achieve the same behavior in the Sandbox, to compare hits and misses?
