Closed
Description
Preconditions (*)
- M 2.3.5-p1, 2.4-develop
- English and German locale
Steps to reproduce (*)
- Create an order in english store
- Go to order in backend with an german locale (de_DE) set in admin account profile
- Resend the order E-Mail
Expected result (*)
- The formatted address in the E-Mail should contain an english country name
Actual result (*)
- The formatted address in the E-Mail contains a german country name
The problem:
The function \Magento\Sales\Model\Order\Email\Sender\OrderSender::prepareTemplate() is called before \Magento\Email\Model\AbstractTemplate::applyDesignConfig() starts store emulation. So prepareTemplate() uses the locale and config for adminhtml. Not frontend.
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- 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.
- [ X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Metadata
Metadata
Assignees
Labels
The issue has been fixed in 2.4-develop branchGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 1 Passed. Automatic verification of issue format passedGate 4. Acknowledged. Issue is added to backlog and ready for developmentMay be fixed according to the position in the backlog.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branchAffects non-critical data or functionality and does not force users to employ a workaround.Has been reviewed and prioritized during Triage with Product Managers
Type
Projects
Status
Done
Milestone
Relationships
Participants
Activity
m2-assistant commentedon Jul 20, 2020
Hi @bernd-reindl. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance- upcoming 2.4.x releaseFor more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue:
@magento I am working on this🕙 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, please join the Community Contributions Triage session to discuss the appropriate ticket.
🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
bernd-reindl commentedon Jul 21, 2020
@magento give me 2.4-develop instance
magento-engcom-team commentedon Jul 21, 2020
Hi @bernd-reindl. Thank you for your request. I'm working on Magento 2.4-develop instance for you
magento-engcom-team commentedon Jul 21, 2020
Hi @bernd-reindl, here is your Magento instance.
Admin access: https://i-29209-2-4-develop.instances.magento-community.engineering/admin_57e5
Login:
44aaae2aPassword:28ebd1d8e8e8Instance will be terminated in up to 3 hours.
bernd-reindl commentedon Jul 21, 2020
@magento-admin unfortunately i didn't receive the order mails in the 2.4-develop instance. So i can't validate the bug in 2.4-dev.
m2-assistant commentedon Jul 29, 2020
Hi @engcom-Delta. 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).
Details
If the issue has a valid description, the labelIssue: Format is validwill be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is validappears.2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Descriptionlabel to the issue by yourself.3. Add
Component: XXXXXlabel(s) to the ticket, indicating the components it may be related to.4. Verify that the issue is reproducible on
2.4-developbranchDetails
- Add the comment@magento give me 2.4-develop instanceto deploy test instance on Magento infrastructure.- If the issue is reproducible on
2.4-developbranch, please, add the labelReproduced 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: Confirmedonce verification is complete.6. Make sure that automatic system confirms that report has been added to the backlog.
8 remaining items
stale commentedon Jan 29, 2021
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
magento-engcom-team commentedon Feb 12, 2021
Hi @bernd-reindl, @zaximus84.
Thank you for your report and collaboration!
The related internal Jira ticket
MC-36269was closed asFixed.The fix will be available with the upcoming
2.4.3release.