- Issue created by @Johan den Hollander
- First commit to issue fork.
- last update
over 1 year ago 6 pass - @sakthi_dev opened merge request.
- Status changed to Needs review
over 1 year ago 12:57pm 10 July 2023 - Status changed to Needs work
over 1 year ago 2:18pm 10 July 2023 - 🇳🇱Netherlands Johan den Hollander
Changing back because the warning is on line 81 and 171.
The MR is not fixing both problems. - First commit to issue fork.
- last update
over 1 year ago 6 pass - Status changed to Needs review
over 1 year ago 9:14pm 10 July 2023 - Status changed to RTBC
over 1 year ago 6:01am 11 July 2023 - 🇮🇳India keshavv India
Reviewed the #6 MR and confirms that it will fix the above warning.
- 🇳🇱Netherlands Johan den Hollander
Confirming that the added checks remove the warning while emails are still being send out.
- Status changed to Postponed: needs info
over 1 year ago 4:45pm 14 July 2023 - 🇬🇧United Kingdom adamps
I don't see how to hit this issue. When you save Mailer Policy configuration containing WrapAndConvertEmailAdjuster then it will set
$this->configuration['swiftmailer']
. Please try it - save your policy again and the problem should be fixed.Please can give steps to reproduce.
- Status changed to RTBC
9 months ago 6:23pm 13 February 2024 - 🇨🇦Canada RobLoach Earth
While I understand re-saving the configuration can fix this, one should likely not depend on
$this->configuration['swiftmailer']
always being there. With the config not there, this code would be fine in PHP <= 5, but PHP is a bit more strict nowadays. I'd recommend bringing this change in because it will save many other cases where this issue occurs. - 🇨🇦Canada RobLoach Earth
Found another PHP strict issue. Here's a patch for
plain
too... - Status changed to Postponed: needs info
9 months ago 10:36am 14 February 2024 - 🇬🇧United Kingdom adamps
> one should likely not depend on $this->configuration['swiftmailer'] always being there.
But why not? I don't see how it can be missing in correct usage. As it says in #10, please can give steps to reproduce. That's the information needed before changing the status please.
- 🇺🇸United States ExTexan
I agree with @RobLoach. The condition IS being encountered, so it's better to fix it, even if you can't imagine how it is possible.
In my case, I upgraded a site that was on D8.9, through D9.5, to D10. In doing so, I started with the D8.9 database (cloned from the live site), and ran a massive (1200+ entry) config sync on it. In the D8 site, I was using SwiftMailer, but uninstalled it during the updates of Drupal core, contrib and custom modules, during the move to D10. Somewhere in all that syncing, the configuration for symphony_mailer ended up in such a state as to trigger this error.
So, by performing normal steps to upgrade Drupal and contrib modules, this condition was created. Please tell me how I could have done it differently to avoid the error?
- 🇨🇦Canada bbombachini London, ON
If it helps I have this issue on a site I have installed from scratch which I have copied over the config from another site that I have migrated from switfmailer to symfony_mailer.
Now, I tried to re-save the config, I've removed manually and re-imported, and I still get this error.Hope this helps.