There is a critical compatibility issue in the upcoming WooCommerce 10.3 release that causes miscalculation of product variation prices. To avoid problems on your site, update to WPML Multilingual & Multicurrency for WooCommerce 5.5.2.2 before updating to WooCommerce 10.3.
WCML 5.5.2.3 is now available
Since publishing this post, we’ve released version 5.5.2.3 of WPML Multilingual & Multicurrency for WooCommerce. It includes an additional fix for currency conversion for variable products.
Miscalculation of Product Variation Prices
If your store uses multiple currencies, product variation prices could be converted twice. For example:
- Original product price: 100 EUR
- Exchange rate: 1 EUR = 1.2 USD
- Expected (correct) converted price: 120 USD
- Actual (wrong) converted price: 144 USD
This issue affects everything — from the price shown to your customers, to what they’re charged at checkout, and the price recorded in orders.
WooCommerce 10.3 is scheduled to be released on 21st of October.
To avoid this issue, update WPML Multilingual & Multicurrency to version 5.5.2.3 before updating WooCommerce to 10.3.
How to Update to the New Version?
We are gradually releasing this update to websites, but you can get it right away:
- In your site’s admin, go to Plugins → Add New Plugin and click the Commercial tab.
- Click to check for updates.
- WPML Multilingual & Multicurrency for WooCommerce version 5.5.2.2 will appear on the list and you can update your site to it.
Make sure to also update WPML core plugin (WPML Multilingual CMS) to the latest available version (4.8 or higher). This is the requirement for updating to version 5.5.2.2 of WPML Multilingual & Multicurrency for WooCommerce.
Other Fixes in This Release
Along with the critical fix above, this release also includes the following minor improvements and bug fixes.
Improved Stock Syncing for Duplicated Products
In some cases, when a WooCommerce product was translated by duplicating it, stock wasn’t reliably synced from the original to its translation. This happened when the translation had existing, but empty, stock data. We fixed how WPML detects and updates this data to ensure consistent stock syncing.
Correct Default Variations in Translations
When setting a default variation (like size or color), the translated product sometimes showed the wrong variation. This happened when internal taxonomy IDs didn’t match. The correct variation now syncs as expected.
Fixed a Deprecated Script Notice
WooCommerce 10.3 renamed a JavaScript handle used for admin interface tooltips. While this didn’t break functionality, it did trigger new PHP notices when WP_DEBUG was enabled. This is now resolved.
For a complete list of issues, see the WPML Multilingual & Multicurrency 5.5.2.2 changelog.
Need Help?
If you have any questions, please leave a comment and we’ll be happy to help.
After updating we get several errors :
” You are running updated woocommerce-multilingual, wpml-cms-nav, wpml-media-translation and wpml-string-translation, but the following components are not updated:
sitepress-multilingual-cms (required version: 4.8.0)
Your site will not work as it should in this configuration Please update all components which you are using. For WPML components you can receive updates from your WPML.org account or automatically, after you register WPML. ”
version 4.8.0 is not available??
“This plugin is incompatible with the enabled WooCommerce feature ‘High-Performance order storage’, it shouldn’t be activated.”
This was never an issue before ???
Hi Sander, thanks for reporting this. All you need to do is update WPML core plugin (WPML Multilingual CMS) to the latest version which is currently 4.8.3.
If by any chance, you’re not seeing the update to WPML 4.8.3 from your Plugins page in the admin, please go to Plugins > Add New Plugin and click the Commercial tab. On the Commercial tab, click the button to check for updates. WPML 4.8.3 should appear on the list and select and update to it.
“WPML Update is Incomplete
You are running updated woocommerce-multilingual and wpml-string-translation, but the following components are not updated:
sitepress-multilingual-cms (required version: 4.8.0)
Your site will not work as it should in this configuration Please update all components which you are using. For WPML components you can receive updates from your WPML.org account or automatically, after you register WPML..”
I’m not seeing the update from my plugins page or commercial tab. Everything else is updated but CMS update not available. What to do?
Hi Jesse! Sorry to hear about this issue. Just to confirm, when you went to the Commercial tab, did you click the “Check for updates” button? Clicking this button should always force the update to the latest available version of any WPML plugin.
If you have tried this yesterday, please give it another try today – sometimes, it takes a bit of time before the release reaches all the sites. And if it’s still not working, please create a ticket in our support forum and let our team take a look. Thank you!
I now found the updates using the add plugin / commercial / check for updates route.
They were not available in the regular plugin menyu.
Updating now to check the issues.
The updates seem to have helped.
I am not getting the errors.
Thanks =)
Great, glad to hear Sander! And thank you for confirming. 🙂
I have the issue as described.
All my prices are insane and currencys mixed up.
I have multiple currencys. How do I fix it?
WPML 5.5.2.2 was automatically installed and the new woocommerce version 10.3 is also installed.
Hi Nicky, I’m sorry to hear about this problem. In this case, please create a ticket in our Support Forum and let our team take a look. We’ll prioritize your ticket and get back to you asap.
Hi again Nicky. Just a tiny note – WooCommerce 10.3 version was not released yet because they postponed it to (most probably) today. So, I’m not sure why you are even experiencing these issues. First, make sure you update all WPML plugins to the latest version including the core plugin (must be 4.8 or higher) and String Translation addon.
If this doesn’t resolve the issue, please create a ticket in our support. Thank you!