-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Email may not be sent if Magento has enabled asynchronous email sending on multiple websites. #32239
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
…mail sending on multiple websites.
Hi @engcom-Kilo. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests 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 |
@magento run all tests |
@@ -100,12 +100,11 @@ public function __construct( | |||
*/ | |||
public function send(Creditmemo $creditmemo, $forceSyncMode = false) | |||
{ | |||
$this->identityContainer->setStore($creditmemo->getStore()); |
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.
It feels more like a workaround as it's changing the shared object that was injected through DI. Right?
Could you provide info on where it used? Can we create a new identity container using the factory, set the correct store, and pass it further where it used?
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.
@ihor-sviziev
It's not injected via di, CreditemmoSender extends from abstract Sender which has dependency on identity interface. Here we use creditmemo identity container implementation for this interface. As far as I found, the creditmemo identity container not used in other places.
As you may see, such workaround has been used from the beginning(and it's true for almost all senders, including abstract one), set store just been called to late which led to issues.
Yes, it'll be more cleaner to create creditmemo identity container via factory, but we already have coupling between objects to high for this sender and adding new dependency will make it even worse.
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.
Ok. I see there used shared="false"
in order to prevent state changing. Let's keep it as is for now.
magento2/app/code/Magento/Sales/etc/di.xml
Line 334 in 91aaeec
<argument name="identityContainer" xsi:type="object" shared="false">Magento\Sales\Model\Order\Email\Container\OrderIdentity</argument> |
Note: seems like it used only here
magento2/app/code/Magento/Sales/Model/Order/Email/Sender.php
Lines 144 to 150 in c4570d2
protected function getTemplateOptions() | |
{ | |
return [ | |
'area' => \Magento\Framework\App\Area::AREA_FRONTEND, | |
'store' => $this->identityContainer->getStore()->getStoreId() | |
]; | |
} |
Hi @ihor-sviziev, thank you for the review.
|
@magento I am working on this |
@zakdma the branch with code successfully imported into |
Hi @engcom-Kilo, thank you for your contribution! |
Description (*)
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)