Send Drupal Core welcome email to new registrations during checkout

Created on 20 September 2019, almost 5 years ago
Updated 9 May 2024, about 2 months ago

I may be missing something here but I have looked everywhere for this. On a site I'm developing (loose term I'm more of a site builder) the user received the standard welcome email when they use the user registration form, you know the one that starts off with "Thank you for registering at [site:name]".

I've edited the default checkout flow to have the Login or continue as guest set to NOT ALLOW guest checkout but to ALLOW registration. The user is presented with the login form on the left and the user registration form on the right and after registering they are then taken to the payment information form and finally complete checkout where they receive the order receipt email.

The thing is, there's no welcome email sent at all during this process, just the order receipt. I can't find where this is meant to be configured. Does commerce 2 simply not send the welcome email when the user registers during checkout at the moment? Should this be a feature request instead of a support request?

Thanks in advance :)

✨ Feature request
Status

Needs work

Version

2.0

Component

Checkout

Created by

🇬🇧United Kingdom vaccinemedia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇦Ukraine init90 Ukraine
  • I created a new patch, based on comment #10, compatible with commerce 2.36.

  • Status changed to RTBC about 2 months ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
    last update about 2 months ago
    793 pass
  • 🇫🇷France Nicolas Bouteille

    Thank you the patch works great for us on Commerce 2.38.
    RTBC!

  • Status changed to Needs work about 2 months ago
  • 🇮🇱Israel jsacksick

    Feels weird to expose all the different "operations" like this... What would be the usecase for using any of the emails not starting by "register_"?
    Also, we use "\Drupal::configFactory()" instead of injecting the config factory. I get that this was probably done not to add an extra dependency breaking code decorating the login checkout pane, but this is not best practice.

    I wonder if we should expose the "human" labels instead of the operations machine names for the email options (See the attached screenshots):

    Current options:

    Suggestions:

Production build 0.69.0 2024