🇪🇸Spain @sluc23

Account created on 13 July 2011, over 13 years ago
#

Recent comments

🇪🇸Spain sluc23

I'm facing similar issue but in my case I use AEgir to create Drupal9/10 websites including symfony_mailer as part of the Drupal platform. AEgir installation succeed most of the process but it fails at the very end when it sends a welcome email to notify the site installation.. it tries to send the email as

$mail_success = \Drupal::service('plugin.manager.mail')->mail('install', 'welcome-admin', $mailto, $langcode, $mail_params, $from, TRUE);

ref: https://gitlab.com/aegir/aegir3/provision/-/blob/7.x-3.x/platform/drupal...

and the result is similar as described here:

Error: Call to a member function fromArray() on null in <drupal_root>/web/modules/contrib/symfony_mailer/src/MailManagerReplacement.php on line 89 #0 <provision_root>/platform/drupal/install_9.inc(42): Drupal\symfony_mailer\MailManagerReplacement->mail()
#1 /data/disk/lspiegel/.drush/sys/provision/platform/drupal/install_9.inc(187): install_send_welcome_mail()
. . . 

Definitely this is a different use case as the described as part of the ticket in test suite, but seems to be similar causes.
I'll probably find a workaround to overcome this problem.

🇪🇸Spain sluc23

thanks @demeritcowboy for tagging. I'm fine with any workflow you defined for webform_civicrm.. It just seems weird to use github repo for the community to collaborate with PRs, when the latests tags are not updated in that repo.. in my POV that could lead to some unwanted misunderstanding while working in these PRs.. but I was curious about the process.. thanks for responding I can close this!

🇪🇸Spain sluc23

hi @KarinG.. I don't understand your comment " I generally don't create tags for the Github repo." all tags are historically in that repo except for 6.2.5 (https://github.com/colemanw/webform_civicrm/tags).. that means you are not going to create any new tag in github from now on?

that will be weird because we do PRs in Github, and not in drupalcode, so not having tags and fully updated repo in github could lead to misunderstanding and wrong processes in the PRs.. am I missing something?

thanks!

Production build 0.71.5 2024