Display custom user fields on checkout registration form

I am also interesting in displaying the full register form, as well as the login form in the same state as real form (e.g. if you user email_registration module).

I think we should try to create a RenderElement with PluginFormInterface that will add UserLogin and UserRegister form obtained with help of the snippet in the description.

+1

I think I would class this as a bug rather than a support request.

If your registration form has additional required fields then enabling this checkout register form lets you bypass them. I was very surprised when I looked at this and saw it didn't follow the standard registration form.

I think this is Critical issue since Commerce must use Drupal standard registration form.
Imagine if Drupal Registration form contain a Required Field which will be by passed by Commerce form.

Is there a workaround or example to solve this issue?
I need to add Phone Number on user registration form as required field.

@drupalisme

Yes there is a work-around, we chose to use use hook_form_alter() to replace the checkout register form entirely with #markup, which just links the user to the normal register page, and redirects them back to the checkout after registration.

You could also use the same technique to add fields back into the form, but you would need to handle the submission/validating/saving of these manually.

I would be interested to hear if anyone has managed to seamlessly replace that form entirely with the RegisterForm instead, I imagine it must be possible.

@mattjones86 can you share the code? I face this issue and still try to alter /contrib/commerce/modules/checkout/src/Plugin/Commerce/CheckoutPane/Login.php this week.

NB: Just updated to Commerce latest version 8.x-2.11 but does not include solution for this issue.

We use something like this:

function hook_form_alter(&$form, \Drupal\Core\Form\FormStateInterface $form_state, $form_id) {

  if ($form_id === 'commerce_checkout_flow_multistep_default' && $form['#step_id'] === 'login') {
    $form['login']['returning_customer']['forgot_password'] = [
      '#type' => 'link',
      '#url' => Url::fromRoute('user.pass'),
      '#title' => t('Forgotten password?'),
      '#attributes' => [
        'class' => ['button']
      ],
    ];
    $form['login']['register'] = [
      '#type' => 'fieldset',
      '#title' => $form['login']['register']['#title'],
      '#attributes' => $form['login']['register']['#attributes'],
    ];
    $form['login']['register']['register'] = [
      '#type' => 'markup',
      '#markup' => Markup::create(t('<p>In order to proceed to checkout you must have an active account with us. Please <a href="@register">click here</a> to register for a website account.</p>', ['@register' => Url::fromRoute('user.register')->toString()])),
    ];
    $form['login']['register']['register_link'] = [
      '#type' => 'link',
      '#url' => Url::fromRoute('user.register'),
      '#title' => t('Register now'),
      '#attributes' => [
        'class' => ['button']
      ],
    ];
  }
}

This is a feature request, and normal. This is a request to expand the currently functionality.

I have worked on this over in #2857157: Implement registration after guest checkout and will review adding this to the Login pane's registration functionality.

I need to add test coverage. But this should expose fields.

Adds testing for custom user fields; fixes a bug in last patch.

+
+  /**
+   * Tests that you can register from the checkout pane.
+   */
+  public function testRegisterOrderCheckoutWithCustomUserFields() {

Looks like this method has a newline too many both before and after.
The docblock is also incorrect (doesn't mention custom user fields).

Code changes look good.

Thanks the patch in #18 seems to work well.

The only thing I had to add was a weight to the submit button so it always stayed at the bottom of the form. Otherwise it wasn't possible to reliably add registration form fields after the commerce password field but before the submit button (I'm my case a newsletter signup tickbox)

That makes sense. type=>action should have a weight of 50, or whatever the normal pattern is.

This addresses #21 and #22.

Generated a very bad patch in #24.

Thank you, mglaman!

Hi Mglaman,

Thanks for your great work,its working fine now I am able to get all my accounts fields in checkout registration form.
But I am getting an error in the last step of checkout i.e checkout/%/payment page.
I am getting the following error can you please help me to fix this issue

Errorr:

"Drupal\Core\Entity\EntityStorageException: Query condition 'users_field_data.mail IN ()' cannot be empty. in Drupal\Core\Entity\Sql\SqlContentEntityStorage->save() (line 805 of /mnt/md1/support-docseducation/support_backend/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php)."

Was there any progress on this issue? It definitely is a bug if it doesn't show the custom fields on the user account.

I'm also wondering if there is a way to choose which registration form is used if using multiple_registration module https://www.drupal.org/project/multiple_registration