FOX Currency Switcher Pro v1.4.9 - Currency selector not working on cached pages + rollback request
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Hello FOX Currency Switcher Support Team,
I am using FOX Currency Switcher Professional for WooCommerce (Version 1.4.9 released on 12 June 2026).
After updating to version 1.4.9, I started experiencing an issue where the currency selector stops working on cached pages.
Issue details:
- Currency switching works correctly on pages where cache is disabled (cart, checkout).
- Currency switching does not work on cached pages — the selector is completely unresponsive, no page reload or currency change occurs.
- The issue appeared after updating to version 1.4.9.
- My website is hosted on Hostinger and uses LiteSpeed Cache.
- A caching plugin is active on the website.
- All website and server caches have been cleared.
- The issue still occurs after clearing all caches and testing in an Incognito browser window.
- When logged in as admin (no cache served), the selector works correctly.
- After visiting a non-cached page (e.g. cart), returning to a cached page temporarily fixes the selector
I also found another user reporting the exact same issue after updating to version 1.4.9, which confirms this is not an isolated case.
Rollback request:
While waiting for an official fix, I would like to roll back to version 1.4.8 to restore functionality on my site. Unfortunately I am unable to find a download link for previous versions of the Pro plugin. Could you please provide a direct download link for version 1.4.8 (or the latest stable version prior to 1.4.9)?
Could you please check whether this is related to the latest update, provide a fix or workaround, and share a download link for the previous stable version in the meantime?
Thank you.
Hello
Thank you for the detailed report.
Before assuming this is a regression in 1.4.9, please check one setting first, since this exact behavior is the typical symptom of a cache plugin not being told to cooperate with the currency switcher, regardless of plugin version.
Please go to WooCommerce Currency Switcher settings, tab Options, and find the option called I am using cache plugin on my site. Set it to Yes. Once you enable it, a Custom price format field will appear, please set it to something like PRICE (CODE). We also recommend enabling the option called No GET data in link right below it, this avoids duplicate entries in the currency switch statistics when caching is active.
After enabling these options, please clear all caches on your site (LiteSpeed Cache, any server side cache, and CDN cache if you use one), then test the currency selector again on a previously cached page.
Regarding rolling back to version 1.4.8, here is how to do it.
If you purchased the Pro version through CodeCanyon, log into your Envato account, go to Downloads, and download the full package again (All files and documentation), not just the installable plugin zip. Inside that package you will find an Archive folder containing previous versions of the plugin, including 1.4.8. Extract the 1.4.8 plugin zip from there.
To install it, first deactivate the current plugin from Plugins in your WordPress admin. Then delete the currently installed plugin folder (either through Plugins, Delete, or via FTP/File manager in wp-content/plugins). After that go to Plugins, Add New, Upload Plugin, and upload the 1.4.8 zip you extracted from the Archive folder, then activate it.
Please let us know if enabling the cache compatibility option above solves the issue, since in most cases it does, and a rollback would not even be necessary.
Hello,
Thank you for your quick response.
I followed all the steps you suggested:
-"I am using cache plugin on my site" was already set to Yes.
- I set the Custom price format to PRICE (CODE).
- I enabled the"No GET data in link" option.
- I cleared all caches (LiteSpeed Cache, server-side cache, and CDN cache).
- I tested in an Incognito window to ensure no cookies were present.
Unfortunately, none of these changes resolved the issue. The currency selector continued to be completely unresponsive on cached pages after applying all recommended settings.
I then proceeded with the rollback to version 1.4.8 following your instructions (CodeCanyon → Downloads → All files and documentation → Archive folder). After installing 1.4.8 and clearing all caches, the currency selector seems to be working correctly again on all cached pages.
I will stay on 1.4.8 until a fix is available. Please let me know when a corrected version is released.
Thank you.
Hello
Thank you for the update and for confirming that 2.4.8 resolved the issue on your site.
We looked into this closely and compared the code changes in the recent release, and there is nothing in that update which touches the currency selector logic, caching headers, or the way the switcher interacts with cache plugins. The only changes in that release were a security fix and some internal error logging, none of which are related to the selector behavior you described.
Based on this, our suspicion is that the issue was not actually caused by the plugin version itself. A more likely explanation is that your cache had already built up stale pages before you enabled the cache compatibility option and the custom price format setting. When you later did a full plugin reinstall, you also performed another full cache clear at the same time, which most likely is what actually fixed it, rather than the version rollback.
To confirm this, could you try installing the current version again, making sure to fully clear all caching layers (LiteSpeed Cache, server side cache, and CDN cache if applicable) right after activating it, the same way you did during your rollback. If the selector keeps working correctly on the current version after a full cache clear, that would confirm the version itself was never the actual cause.
Let us know how it goes.