SOLVED: WooCommerce Checkout V2: Account Creation Settings and Login Required Message Behaviour

I’m testing WooCommerce Checkout V2 and noticed some behaviour that I’m not sure is expected or a possible issue.

In WooCommerce → Settings → Accounts & Privacy :

When “Allow customers to create an account during checkout” is enabled, WooCommerce adds the Create account checkbox element to the checkout page.

However, it seems this only works correctly when both options under Account creation options are enabled:

  • Send password setup link
  • Generate account login

Otherwise, a username/password requirement error appears.

Is this expected WooCommerce behaviour, or should the checkout account creation option work independently?

If this is normal behaviour, I think WooCommerce (or Checkout V2) should validate these required settings before adding the Create account option to the checkout page, because currently it can create confusion.

Also, is there a way to allow customers to choose their own username and password during checkout instead of WooCommerce automatically generating the account details?

Another issue:

When I disable:

WooCommerce → Settings → Accounts & Privacy → Checkout → Enable guest checkout

the checkout page only shows:

“You must be logged in to checkout.”

My understanding is that this condition should trigger the Bricks Checkout V2 → Login Required option/element instead of only displaying the default WooCommerce message.

Can anyone confirm whether this is:

  • a WooCommerce limitation,
  • a Bricks Checkout V2 issue,
  • or a missing configuration?

Thanks!

Hi @Binu

Thanks for the detailed report. We confirmed issues with Checkout V2’s account-creation settings and required-login state and added them to our internal bug tracker. We’ll update this thread once they’re fixed.

Regards,
Jenn

1 Like

We’ve addressed this in Bricks 2.4-beta3 (beta release), now available for manual download from your Bricks account.

Please read the changelog entry before testing, and let us know if you experience any issues. Note: beta builds are not recommended for production sites.