Skip to content
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

Merged
merged 1 commit into from
Apr 22, 2021

Conversation

engcom-Kilo
Copy link
Contributor

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Magento 2.3 contact form not sending emails( No log entry) #23645

Manual testing scenarios (*)

  1. see Magento 2.3 contact form not sending emails( No log entry) #23645

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Apr 13, 2021

Hi @engcom-Kilo. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

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.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 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

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Apr 13, 2021
@engcom-Kilo
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Apr 13, 2021

Looks good to me. Let's wait for test results
@magento run all tests

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-9000 has been created to process this Pull Request

@dmitriyprime
Copy link
Contributor

✔️ QA passed

@dmitriyprime
Copy link
Contributor

dmitriyprime commented Apr 15, 2021

After fix:
image

Copy link
Contributor

@ihor-sviziev ihor-sviziev left a 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

@zakdma
Copy link
Contributor

zakdma commented Apr 21, 2021

@magento-engcom-team
Copy link
Contributor

@zakdma the branch with code successfully imported intomagento-tsg/magento2ce repository. Branch name: imported-magento-magento2-32730.

@magento-engcom-team magento-engcom-team merged commit 78ec76a into magento:2.4-develop Apr 22, 2021
@m2-assistant
Copy link

m2-assistant bot commented Apr 22, 2021

Hi @engcom-Kilo, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@@ -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.'));
Copy link
Contributor

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.

Copy link
Contributor

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

@tuyennn
Copy link
Contributor

tuyennn commented Jun 16, 2021

@ihor-sviziev This is completely useless pull request. With

throw new MailException(new Phrase($e->getMessage()), $e); 

we already knew what the exception was.

@ihor-sviziev
Copy link
Contributor

@tuyennn, before this PR, we hadn't any log record about email sending failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage Component: Email Component: Mail Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Magento 2.3 contact form not sending emails( No log entry)
6 participants