-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Magento 2.3 contact form not sending emails( No log entry). #32730
Conversation
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 |
Looks good to me. Let's wait for test results |
Hi @ihor-sviziev, thank you for the review. |
✔️ QA passed |
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.
Hey @dmitriyprime @engcom-Kilo ,
It looks like that's not OK that an exception was thrown there and a customer came to the report page. It wasn't expected. The correct behavior should be exception logged to var/exception.log or var/system.log file
@magento import code to https://github.com/magento-tsg/magento2ce |
@zakdma the branch with code successfully imported into |
Hi @engcom-Kilo, thank you for your contribution! |
@@ -100,7 +110,8 @@ public function sendMessage() | |||
|
|||
$this->laminasTransport->send($laminasMessage); | |||
} catch (\Exception $e) { | |||
throw new MailException(new Phrase($e->getMessage()), $e); | |||
$this->logger->error($e); | |||
throw new MailException(new Phrase('Unable to send mail. Please try again later.')); |
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.
@engcom-Kilo @zakdma, we have regression here. The original exception should be passed as a 2nd param here to understand why it failed, as it was in the past.
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.
FYI here is a PR that fixes this regression #33419
@ihor-sviziev This is completely useless pull request. With
we already knew what the exception was. |
@tuyennn, before this PR, we hadn't any log record about email sending failure. |
Description (*)
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)