Registrations not created during checkout

Created on 3 February 2023, almost 2 years ago
Updated 4 February 2023, almost 2 years ago

Problem/Motivation

D9.5.2, PHP 8.1.14, latest commerce install ( 8.x-2.33). While developing a shop my checking out with the manual payment module makes registrations visible in commerce's "orders" but neither in the product variation registration tab nor in the commerce menu under reg./reg. summary (if this is intended at all). I seem to remember that it probably did work a week ago or so when I tried all sorts of things to decide which way to go for registrations. I am almost certain I did send a few test mails from within a reg tab and thought this would be way easier than creating a new announcement list for participants in Mailman. Perhaps this was before my local entity registration upgrade from 3.0.0-beta2 to 3.0.0-beta3 which I did locally only a few days ago, creating test registrations again only afterwards. I couldn't say of course which module probably suffers from a potential bug. The registrations are visible as "completed" in the orders list which perhaps is intended because the order was completed, although the reg. itself is "pending" in the Payments tab until a payment has been added, BTW, it would be nice to see the "payment pending" status in a list (wherever, in orders or in the reg. menu items or the individual prod.var. reg. tab) without having to enter an individual registration's payment tab first.

Steps to reproduce

On a Drupal install with versions and a manual payment module as mentioned above create a product, a prod. variation to which you add the Registration field. Buy the item, checkout. The order can be seen in the commerce menu item "orders". Product variety Registration tab is there but the registration itself is not visible there, and no Entries under the two Reg./Reg. summary items in the Commerce menu

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Version

3.0

Component

Registration Pane

Created by

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

Comments & Activities

  • 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.

  • Issue was unassigned.
  • Status changed to Fixed almost 2 years ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024