- Issue created by @dgwolf
Got one step further: When I drill down from the commerce products menu item to a single product variation, this variation does have a register tab beside the manage registrations tab. That register tab works but I have to choose from the dropdown menu for whom I am registering. This step seems not to be happening or be dealt with when checking out through the cart. Therefore the aforementioned way of registering has nothing to do with commerce's payment module and the checkout workflow. Did I miss a configuration step?
- Assigned to john.oltman
- πΊπΈUnited States john.oltman
Yes @dgwolf, the Registration Process pane has to come before the Payment Process pane in your checkout flow:
/admin/commerce/config/checkout-flows/manage/default
Once you make that change, registrations will be created during checkout and will appear in the tabs. They will also appear in the Commerce Registrations listing at /admin/commerce/registrations. Currently, the payment process redirects to the Completion step before the Registration Process pane can do its work, so no registrations are created.
Sorry about that, I will update the README to note this requirement.
I also noticed that somewhere along the way, you created an Event content type and enabled it for registration, and created events that pointed to a Registration Type ("def_register") that has since been deleted (I'm assuming that was an early effort that you replaced with the commerce method). This causes some inaccurate reporting on the Manage Registrations listing for those Events. I know you are probably not using those anymore, but for others, I will add a constraint that prevents deletion of a Registration Type that is in use by any entities - users will need to edit those entities before deleting the type.
-
john.oltman β
committed 81eec6c8 on 3.0.x
Issue #3339074 by dgwolf, john.oltman: Update README to explain why...
-
john.oltman β
committed 81eec6c8 on 3.0.x
- Issue was unassigned.
- Status changed to Fixed
almost 2 years ago 5:23pm 4 February 2023 Automatically closed - issue fixed for 2 weeks with no activity.