here is my question:

a new event has been created and the Registered Status limit is set to 30 and Wait Listed status limit is set to 0.

what happens once the 30th person has registered and the event is supposedly full now? what do anonymous users see when they view this event now? is option to register still available to them, even though the event is full now?

Comments

mdowsett’s picture

Status: Active » Closed (fixed)

when you reach 30, the system will no longer accept more signups.

What I did is create a statuses called:
- Pending Approval (renamed the default status to this)
- Wait Listed
- Approved

And put a limit of 30 approved people and no limit on the others.

The admin confirms registration by changing the first 30 from pending to approved and then the rest to wait listed. This way it keeps registration open for more people to register past 30.

pelicani’s picture

Category: support » feature
Status: Closed (fixed) » Active

I'd like to propose some changes to provide the user a form to signup for the wait list once the registration is filled.

Display the signup form, as is, until the registered limit is met.
When registered limit is met, display the wait list form.
Note: this is the same form, with a message at the top of the form.
e.g. The Signup Limit has been met. You can submit this form to be placed on the Wait List. If there is a cancellation, you can be added to the registration list and contacted.
Once the wait list has been filled, close signups.

Please post any thought/comments.

iamwhoiam’s picture

If I set registered users to 3, why can I get 4/3 users registered? (and more)

dpalmer’s picture

Version: 5.x-1.0 » 5.x-1.x-dev

I have the same issue, we are working to resolve it.

dww’s picture

Title: what happens when event is full? » Make the wait list feature work properly with per-status limits
Version: 5.x-1.x-dev » 6.x-1.x-dev
Component: User interface » Signup status limit
Status: Active » Postponed

This is going to be cleaned up and mostly working nicely via #359412: Move code for signup limits per status per node into a submodule and #241869: Improve interface for setting number of signups allowed per status. That proposal isn't directly going to address automatically moving signups from the wait list to another status when there are cancelations, but it's going to pave the way for solving this problem for real... Interested parties should review and test the patches and screenshots in those issues, and/or read the full spec at
#359412-3: Move code for signup limits per status per node into a submodule (http://drupal.org/files/issues/359412-3.signup_status_limit.spec_.pdf) and provide your feedback there. Thanks.

michellezeedru’s picture

Subscribing

goose2000’s picture

Subscribing

kentr’s picture

Curious if there are updates on this, since the issues mentioned in #5 are closed.

Do any aspects of the waitlist feature work? I've played around with limits and such and am not seeing any indication of a waitlist.

Thank you.

ezra-g’s picture

Status: Postponed » Active

As dww said in #5:
"That proposal isn't directly going to address automatically moving signups from the wait list to another status when there are cancelations, but it's going to pave the way for solving this problem for real."

And looking through the code, it seems that this feature isn't actually in place.

However, the project page says, "Wait list functionality for the signup module with optional auto-transition to "Registered" status." -- I feel like that should have a note that says that this feature exists in D5, and link to this issue for D6.

adraskoy’s picture

subscribe