I have created a fieldgroup with a single boolean, which is required. If the user does not click the boolean, and continues through the checkout process, an error message appears, but they are directed to the next screen of the checkout process anyway.

Comments

pcambra’s picture

pcambra
he/him
Primary language Spanish
commented

Have you tried to reproduce this with the -dev version of the module?

Steps to reproduce:

* Add a new field group to order entity
* Add a boolean field to this group, mark it as required.
* Add this fieldgroup pane to the first step of checkout.
* Required field should stop the form to continue to the second step of checkout but instead of this, an error message is displayed (?) and step 2 is rendered.

pcambra’s picture

pcambra
he/him
Primary language Spanish
commented
Status: Active » Closed (works as designed)

I'd say this is a commerce issue, proposed a fix in #1380310: Optionally require all panes on a checkout page to validate before processing them

Gauntlet-1’s picture

Gauntlet-1 commented

1. I haven't tested with -dev, and won't have the opportunity.
2. I'd say you're right about it being a commerce issue. Thanks for looking into it.

WtheM’s picture

WtheM commented

I have tested following scenario:
1. Using dev version, I have added requred textfield into the 3-rd step of checkout - success!
2. Then I have added required bolean field (single checkbox) into the same 3-rd step of checkout - fail!

Seems like there is a problem with single checkbox as bolean field.

I have successfully tested "commerce extra panes" module with "Terms of Service" build in functionality, and the required checkbox worked fine.