Not able to translate "City" and "Street Address" fields in the Store Information

[cptX]

Preconditions and environment

• Magento version 2.4.6

Steps to reproduce

I have a magento 2 installation with 2 store views Greek and English. My site is Greek first so by default I write everything in Greek and then I select the english store view and set the english translations. The fields "City" and "Street Address" in the Store Information are not available in the English Store View: Default view: English view:

This has a result the emails sent to the english customers to have a mixed language store address at the footer!

Expected result

The fields "City" and "Street Address" should be available to all Store Views, in order to be able to translate these fields.

Actual result

The fields "City" and "Street Address" are not provided to every language store view, so it's not possible to translate them. The email templates now have mixed language store address at the footer (default Luma installation).

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.
• [X] 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[bot]]

Hi @cptX. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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[bot]]

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: :point_down:

• [ ] 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 @cptX,

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.

We are able to view The fields "City" and "Street Address" to all Store Views.

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

Thanks.

[cptX]

How is this even possible? I have 2 versions of magento 2.4.5 and 2.4.6 and both of them are lacking these fields when selecting scope Greek or English. Have you selected these scopes? Can you please check with the 2.4.6 stable version and not the dev version?

[cptX]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @cptX. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @cptX, here is your Magento Instance: https://75599f8aab504f84dd2ee218793db2a7.instances-prod.magento-community.engineering Admin access: https://75599f8aab504f84dd2ee218793db2a7.instances-prod.magento-community.engineering/admin_5b55 Login: f0571461 Password: deae7f178f42

[cptX]

@engcom-Bravo I have created a new instance and created two store views Greek and English. Please login in the admin and check it yourself!

[engcom-Bravo]

Hi @cptX,

Thanks for your update.

As per the Magento documentation https://experienceleague.adobe.com/docs/commerce-admin/config/general/general.html?lang=en#store-information

Country, Region/State, ZIP/Postal Code, City, Street Address, Street Address Line 2, VAT Number will have the scope and access for the website only.

Please check the document and let us know if we are facing any issue.

Thanks.

[cptX]

What is the point of having City and Street address not following the store view scope? City and address are written differently in every language!!!! The mentality of magento some times is so stupid... So what should we do, if this is by design please convert this issue to feature request. Don't close it, it's important!!! Now my customers are receiving mails with mixed language address of my shop! How can I translate these fields? Can I translate them in the theme level?

[engcom-Bravo]

Hi @cptX,

Thanks for your update.

We are Considering this as a Enhancement to proceed further we are marking this as a Feature Request.

Thanks.

[alex-79]

What is the point of having City and Street address not following the store view scope? City and address are written differently in every language!!!! The mentality of magento some times is so stupid... So what should we do, if this is by design please convert this issue to feature request. Don't close it, it's important!!! Now my customers are receiving mails with mixed language address of my shop! How can I translate these fields? Can I translate them in the theme level?

Hi @cptX Here is a temporary solution - https://github.com/alex-79/magento2-fix-store-information-scope

[cptX]

What is the point of having City and Street address not following the store view scope? City and address are written differently in every language!!!! The mentality of magento some times is so stupid... So what should we do, if this is by design please convert this issue to feature request. Don't close it, it's important!!! Now my customers are receiving mails with mixed language address of my shop! How can I translate these fields? Can I translate them in the theme level?

Hi @cptX Here is a temporary solution - https://github.com/alex-79/magento2-fix-store-information-scope

Hi, @alex-79 i'm checking your solution now and I don't understand what have you changed in your new suggested module. I'll comment there my questions.

[cptX]

I have tested the solution from @alex-79 and it looks like it's working correctly, at least in the emails sent to customers that purchased through my second store view. Thanks @alex-79 !! I would like this functionality to be merged in the standard magento! It's very important and necessary functionality!! It requires changing only 1 file: /vendor/magento/module-backend/etc/adminhtml/system.xml