Currency symbol loaded from another locale than defined in store

[ivanko-dev]

Preconditions and environment

Magento version 2.4.6-p1

Application configured to de_DE locale and have different currencies data displayed on pages. The expected currency symbol for MXN (Mexican peso) is "MX$", but "$" is displayed on pages.

Magento uses symfony/intl extension now to load locales specific data instead of magento/zendframework1 used before. The logic for currencies data loading is implemented in \Magento\Framework\Currency\Data\Currency. As result method responsible for loading currency symbol (\Magento\Framework\Currency\Data\Currency::getSymbol LIne 250) uses hardcoded locales for specific currencies (\Magento\Framework\Currency\Data\Currency::$displayLocale Line 53) to change locale on symbol loading (Line 258).

In this way currency symbol is loaded using another locale es_MX (vendor/symfony/intl/Resources/data/currencies/es_MX.php) than defined in the store configuration de_DE (vendor/symfony/intl/Resources/data/currencies/de.php)

Steps to reproduce

Display MXN, MAD, SAR, BHD, ... currency for de_DE locale in store.

Expected result

Currency symbol from vendor/symfony/intl/Resources/data/currencies/de.php (for de_DE locale) shown.

Actual result

Currency symbol from another locale displayed.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ivanko-dev. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @ivanko-dev,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Display MXN, MAD, SAR, BHD, ... currency for de_DE locale in store.

We are able to get the all configured currencies in German store.

MXN Currency

MAD Currency

BHD Currency

SAR Currency

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[engcom-Bravo]

Hi @ivanko-dev,

Kindly provide latest update on this comment #37780 (comment) still you are working on this issue if you are able to reproduce the issue please elaborate the steps to reproduce and let us know if you are still facing any issue.

Thanks.

[ivanko-dev]

Hello @engcom-Bravo
I am sorry I was not able to look into this issue earlier.

These are steps to reproduce it on the admin panel:

1. Change locale for admin user to "Deutsch (Deutschland)" to get de_DE like a main locale for admin panel config
2. Configure Base Currency (Stores -> Configuration -> General -> Currency Setup -> Currency Options -> Base Currency) to use Mexican peso
3. Clear cache
4. Start to create a new order from admin panel and try to add products to order
   Received result: all items in the products list use "$" for Mexican peso
   
   Expected result: all items in the products list use "MX$" for Mexican peso (screenshot below received on local server with excluding \Magento\Framework\Currency\Data\Currency::$displayLocale for locales forced change)
   

Initially, I got this issue in the custom module code, which loaded multiple currency data on the same store product page. I didn't investigate all sequences of actions in detail but looks like \Magento\Framework\Currency\Data\Currency::$displayLocale property forces to change the locale for loading currency symbols data, when the initial currency for locale was already loaded. Probably this was done to prevent cases when no currency symbol specified in the currency locale configuration file (eg. no config for MXN into Resources/data/currencies/ak.php file in symfony/intl package, but it exists in Resources/data/currencies/de.php).

I am not sure if this is important issue, because it was not confirmed on store frontend pages at this moment, but I think would be good to confirm what is the purpose of mentioned several times property with currency - locale pairs: \Magento\Framework\Currency\Data\Currency::$displayLocale

[engcom-Bravo]

Hi @ivanko-dev,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps To Reproduce

• Change locale for admin user to "Deutsch (Deutschland)" to get de_DE like a main locale for admin panel config
• Configure Base Currency (Stores -> Configuration -> General -> Currency Setup -> Currency Options -> Base Currency) to use Mexican peso
• Clear cache
• Start to create a new order from admin panel and try to add products to order

We have Mexican peso as a base currency it is showing MX$ in admin and frontend.

While placing an order in admin it is showing in $ for the products.

But after adding the products to the cart it is showing usually as a MX$ while placing an order in admin panel.

Hence Confirming the issue.

Thanks.