|
Kelly Cobean
|
July 22, 2013 at 8:36 pm
I have an event that allowed 40 attendees. After about 30 minutes, the event was full and in fact had 42 registrants. I did a search on this and found a reply from Josh in mid-2012 in a thread where someone was having a similar problem. He said that a fix is expected in release 3.2. I’m just wondering if any solution was found or if a date for 3.2 is known.
Thanks.
|
|
Garth
|
July 22, 2013 at 10:23 pm
Hi Kelly,
How are you you toady?
The registration limit check happens when the registration form page is loaded. We talked today about adding a fix that will exclude registrations that are submitted by people who were not initially exclude people from accessing the registration form and submitted their registration. Basically we’d exclude those people from getting officially registered and tell them that the registration was already full.
So, once we release that fix what you’ll want to do is add two messages to your event description pages that 1) shows the number of seats available, and 2) explain that an event may fill up as someone completes the registration form and their registration may be rejected.
This affects only a very few people whose events fill us so quickly (thus the few comments/issues/reports about it) but we’re planning to fix this (no deadline quite yet). In the mean time you’ll have to either reduce the overall number of seats available or watch the registration more closely.
I’m just curious, but are your events free or $0?
|
|
Kelly Cobean
|
July 23, 2013 at 6:26 am
Thanks Garth. No my events aren’t free, but I do a “pay on site” format, so I set the initial payment status for all registrants to Completed.
I’m curious why you check the registrant count on form load rather than on form submit? It would seem the easy way to fix this would be to check the registration count on form POST/Submit and if the max count has been reached while the form was being completed, just return an error to the user that the event filled up while they were completing their registration. Item 1 you mentioned is already taken care of by the software and the error message on form POST could take care of #2. Just a thought.
I have events on certain days that will fill up fifty+ slots in less than 5 minutes. People literally sit at their keyboard hitting the F5 key waiting for the event to open. On those days, it would be possible to go 10+ registrations over because lots of people will have the form loaded but not submitted at the same time. I don’t think I could watch the registration closely enough to close it off before it goes over and there are some times where I’m just not available to watch it when registration opens.
Thanks.
|
|
Garth
|
July 23, 2013 at 8:49 am
Hi Kelly,
We’re planning to do just what you’ve described and I’m glad to hear that’s your suggestion about how to do it.
|
|
Kelly Cobean
|
July 23, 2013 at 9:18 am
That’s great news. Thank you Garth!
|
