Closed (fixed)
Project:
Entity Registration
Version:
3.0.x-dev
Component:
Registration Wait List
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Apr 2023 at 23:06 UTC
Updated:
10 Feb 2024 at 23:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
john.oltman commentedThanks for the post! I took a look at the D7 version and it doesn't look too bad. I should have something for you by next week for D9 / D10.
Just curious about your use case - how do people get off the wait list? They have to wait for someone to cancel a completed registration? Does your site use the "held" state perhaps? Any info would help me test.
Comment #3
joelpittet@john.oltman Thanks for being so on top of your queue! I wish I could be that responsive 😅
I work with Frances, who's away today, but the use-case referenced in the issue summary is a port of a Java application, though we have a D7 site that needs to be migrated too that uses this, so we have two reasons to get this functionality.
For the Java port use-case:
From what I gather from the Java code
For the D7 port use-case:

It's how the D7 module works but we have the patch from this issue applied #2850243-7: Waitlist should not warn when editing existing registration.
I don't think I totally understand the "held" state, maybe the administrators use it, but the database only contains entries of "waitlist" and "complete" at the moment.
Here's a screenshot of the states we have:
Let us know if you need more info or how we can help if you'd like us to test anything
Comment #4
john.oltman commentedThanks @joelpittet! You maintain many more projects than me, it would be impossible to stay on top of that many! Excellent info re: the use case, that helps a lot. I do recommend Commerce Registration (I did the D10 port) but be advised, and you probably know this already, but Drupal Commerce is a complex module to configure. Extremely powerful, but if you are new to it, there is a steep learning curve.
I will be in touch here when there is something to test.
Comment #5
john.oltman commentedI have Wait List working locally, need to fine tune and do a bit more testing, but plan to commit to the Dev release for you to try out within the next day or two. Will post again once committed.
Comment #6
joelpittetAwesome thank you @john.oltman
Comment #7
franceslui commentedI greatly appreciate your help to implement my requested waitlist feature so quickly.
Comment #8
josh.fabeanThanks for working on this, just commenting to show support and I will gladly test this as we have client currently asking if this is a thing.
Comment #10
john.oltman commentedWait list has been committed to the Dev branch, please pull that branch down and test it out at your convenience. If things look good it will make it into the next release candidate that will be out in a week or two. I have a couple odds and ends to add to it later, but what is out there now should be plenty to test with and is functionally equivalent (but better than) the D7 version. I am marking this fixed since it is passing tests, if you find major problems you can re-open this, or if there are minor things please open a new issue for those asks. I will update the README to indicate wait list is available as part of the next release candidate.
Comment #11
john.oltman commentedComment #12
john.oltman commentedIncluded in rc2 release
Comment #13
joelpittetThanks @john.oltman for getting that in. We'll be testing that feature while we build and provide MRs or patches if anything needs it (maybe even tests!)
Comment #15
joelpittet@john.oltman We are doing our testing on this and coming up to some challenges with commerce_registration + waitlists. I'll create an issue over there once I find out more what we are attempting can't be done. Just a heads up.
Comment #16
john.oltman commentedSounds good, thanks @joelpittet
Comment #17
john.oltman commentedThe latest release of Commerce Registration now has support for waiting lists:
https://www.drupal.org/project/commerce_registration/releases/3.1.1
Comment #18
john.oltman commentedComment #19
joelpittetWe’ve been using it, thanks for implementing this @john.oltman!