[Assigned] Secondary currencies not working with Litespeed cache crawler

Hello there,

I got feedback from the devs.

The currency is set via client location. This will backfire and cause issues as there is the visitor from his own server.

It turns out the issue is related to how the site sets the currency based on client location. In this case, using the wcml_client_currency cookie alone isn’t enough, because WCML applies internal checks tied to the visitor’s actual geolocation (when logged out), or shipping address (when logged in).

That means the crawler, running from the server’s location, can’t always trigger the correct currency-specific cache. To confirm this, you can temporarily allow all currencies to be accessible from any location and test whether the correct cached version is then served.

Hey there,

Second tier devs ran a test with cUrl:

curl -X GET "<em><u>hidden link</u></em>" \
  -H "Cookie: wcml_client_country=CA; wcml_client_currency=CAD; wcml_client_currency_language=en" > output.html

And correctly received the page with the CAD currency.

It also works fine for the page hidden link (we can see the currency in the header). Check attached image.

Please answer these 2 questions:
1. What does he expect to see on the "Floater Frames in Cary"? (the "50$" is a content string or is a dynamic variable?)
2. Why don't we see the top bar menu with the currency switcher on his screenshot?

Thank you.