-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Add missing order_data array to EmailSender classes #27454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hi @kassner. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @kassner: Could you please sign Adobe CLA? And arcording to Magento DOD, please cover your changes by Unit Test. Thank you very much!
@magento create issue |
Hi @sidolov, thank you for the review. |
Hi @edenduong, thank you for the review. |
@magento run all tests |
Note: Functional Tests B2B and Functional Tests EE are failed |
Note: Automation tests are passed |
Hi @kassner, thank you for your contribution! |
Description
Magento 2.3.4 now recommends using scalar variables instead of objects within the email templates. Unfortunately, not all classes were migrated. For example, \Magento\Sales\Model\order\Email\Sender\ShipmentSender was given the new array, despite now it being deprecated, but its replacement, \Magento\Sales\Model\Order\Shipment\Sender\EmailSender did not.
This change was introduced in commits like fd721b1#diff-7b993c70d2652919564eeaf30afe7326. Several more do change the email templates to use
order_data
instead.Manual testing scenarios
{{order_data.is_not_virtual}}
(as opposed to{{order.is_not_virtual}}
);\Magento\Sales\Model\Order\Shipment\Sender\EmailSender
;Contribution checklist
Resolved issues: