We always assume that mail sends successfully, so when it fails, we give the user confusing messages.
For all usages where mail is sent using MailManagerInterface::mail (including wrapped calls such as in user.module), assign the output to a variable and check $mail['result'] before printing success messages.
Rewrite the patch for Drupal 7 completely looking for all usages of MailManagerInterface::mail and a success message is displayed.
Needs work
11.0 🔥
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
This was previously tagged for issue summary update in #21 which still needs to happen
Tagged for subsystem review to see what they think about this change.
Tagged for tests also.
Thanks.