Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 1 reply, has 2 voices.

Last updated by Nigel 1 year, 11 months ago.

Assisted by: Nigel.

Author Posts
July 16, 2023 at 12:46 pm #14044505

mariaA-45

I am trying to:
Set up WooCommerce Multilingual
(- sitting in Denmark)
(- with MaxMind GeoLocation enabled in WC-settings)
- with multi-currency enabled
- "Show currencies based on" => Client Location
- with automatic currency exchange rates disabled
- custom rounding rules configured

Link to a page where the issue can be seen:
It's a backend issue.

I expected to see:
When I edit product prices on the back end, then WPML will give me these options:
- Calculate prices in other currencies automatically ( Show )
- Set prices in other currencies manually

The "Show" (in option one) link has a tool-tip that states "Click to see prices in the other currencies as they are currently shown on the front end". So I would expect all prices to be shown "as on the front end".

Instead, I got:
Prices on front end and back end differ. On the front end, all prices are shown after currency conversion and rounding, i.e. as expected. However on the back end, prices appear to be shown after currency conversion BUT BEFORE applying rounding rules. That's weird to me. The whole point of previewing prices in all currencies on the back end is to get a quick overview (avoiding the front end, where geo-location rules apply), isn't it? If yes, then this feature is currently broken.

Best,
Maria

July 17, 2023 at 10:17 am #14048081

Nigel
WPML Supporter since 02/2016

Timezone: Europe/Madrid (GMT+02:00)

Hi Maria

I have checked the issue and can confirm it, rounding isn't applied on the back-end preview.

I have escalated this to my colleagues so that it can be fixed. I don't know which version it will get worked on, but a fix should appear in a future update.

Thanks for bringing it to our attention.