[Resolved] Follow up to Site Language resetting the cache

Hi John,

Thanks for the feedback. Our cookie name is "wcml_client_currency" and we set it only when explicitly defined by the filter https://wpml.org/wcml-hook/wcml_user_store_strategy/ otherwise we use WC session to store the currency.

I am not sure why the cookie "wcml_currency" is being set. Are you using some kind of custom code/plugin?

Please let us know if htaccess code fixes the issue otherwise finding that cookie code and removing it should fix the issue.

Thanks

Hi John,

Yes, I understand but I was asking you to contact LiteSpeed as you are a customer and it will be more faster than us.

Anyway, I can see there is no resolution to your problem so I decided to debug this further in LiteSpeed plugin and found the problem.
After enabling the LiteSpeed logs I can see that cookie "wcml_currency" is being set but this cookie name does not exist in our entire plugin 🙂
After checking the LiteSpeed cache plugin code I found it is being set from LiteSpeed itself see here \plugins\litespeed-cache\thirdparty\wcml.cls.php

	public static function apply_client_currency( $currency ) {
		if ( $currency !== wcml_get_woocommerce_currency_option() ) {
			self::$_currency = $currency;
			add_filter( 'litespeed_vary', __CLASS__ . '::apply_vary' );
		}

		return $currency;
	}

	public static function apply_vary( $list ) {
		$list[ 'wcml_currency' ] = self::$_currency;
		return $list;
	}

As per this code, this seems to be expected behavior. They are setting a vary "wcml_currency" to create cache per currency meaning changing the currency or closing the browser will reset the cache.
If they have added this that means there was some currency issue with caching.

I am not sure what we can do here because if this is by design then only LiteSpeed can improve this.

I will ask our compatibility team to reach LiteSpeed regarding this question but if you wish you can also ping them and please ask them to send your query to the development team. This is not the support question anymore.

For, now I have made a minor change to bypass this class in the LiteSpeed plugin (same file) and the issue is fixed but not sure if there will be any problem regarding the currency.

I will update you as soon as we have any updates.

Thank you for your understanding.

Thank you for the wonderful feedback! 🙂

I have already asked our team to contact them. I will keep you posted.

Have a nice week you too!