|
ARAGATO
|
December 10, 2019 at 8:02 am
I would like to have the status of an event only be decided upon based on the number of approved registrations “RAP” instead of taking all registrations (e.g. RAP, RWL etc.) into consideration.
For example (https://i.imgur.com/wiLlyVu.png), Event A has a datetime with a limit of 3 registrations. Currently there are 2 approved registrations and 1 registration is on the wait list. Wait list settings are always set to manual approval through the admin. Event A is status “sold out”, because the limit is exceeded with 2 RAP and 1 RWL registration.
How to change the default EE behavior that it changes the event status only based on the RAPs of the event so that in this case Event A would be active instead of sold out.
|
|
Tony
|
December 10, 2019 at 1:46 pm
Hi there,
EE doesn’t take all registrations into account for calculating the sold out status, it uses RAP + reserved, with the exception of wait list registrations after the fact.
What looks like has happened above is you have had 1 space remaining and a user has started a registration, making a reserved ticket, then…. another user has registered onto the wait list whilst that reserved ticket was in place (because at that point your event would have shown as sold out due to RAP + Reserved == limit).
Now you have a wait list registration that would normally be given the opportunity to register next in place of just another random visitor so the wait list add on prevents the status from changing back and if you change that behaviour your basically setting yourself up for annoyed users asking why they signed up to the wait list and were then ignored.
I can check with our developers to see if it’s possible to override this behaviour (I don’t think it is currently) with the wait list add on but are you sure that’s the direction you want to go with this?
|
|
ARAGATO
|
December 11, 2019 at 9:16 am
Hi Tony,
that would be great if you check with your developers how to overwrite this behavior. I tried to argue with my client that the current solution makes more sense, but they insist of having that particular behavior where only RAPs are used for settings the corresponding status.
|
|
Tony
|
December 11, 2019 at 12:49 pm
Approved registrations are the registrations that count by default.
If we don’t set the event to sold out with RAP + Reserved your going to end up with race conditions and possibly over selling as 2 (or more) or more registrants race to take the final spot. That isn’t going to change even if we can prevent the wait list add on from holding the last place in the above situation with a wait list registration.
We had that situation before we introduced reserved tickets and users ran into multiple over selling situations on popular events, we aren’t going remove that functionality.
We we may be able to remove the wait list preventing the above event from switching back from sold out because it has the wait list registration waiting for approval, not the RAP + reserved setup.
|
|
ARAGATO
|
December 12, 2019 at 11:33 pm
We we may be able to remove the wait list preventing the above event from switching back from sold out because it has the wait list registration waiting for approval, not the RAP + reserved setup
That would be a good compromise, Tony.
|
|
Tony
|
December 13, 2019 at 4:42 am
Unfortunately, as suspected this is something that can not be done at this time.
You would need to disable the Waitlist feature on the event and then manually enabled it once the event is sold out to prevent the above.
|
|
ARAGATO
|
December 13, 2019 at 11:27 pm
How to disable the waitlist feature? Set it to 0?
I really like to avoid modify event espresso files directly, but if there is no hook etc. currently available to do this, I pretty much have to. Could your developers give me a lead where in the wait list addon I can find the lines that change the status?
|
|
Tony
|
December 16, 2019 at 6:48 am
How to disable the waitlist feature? Set it to 0?
Correct.
I really like to avoid modify event espresso files directly…
Unfortunately, as we don’t support modifying core I can’t give you further details on this.
|
|
ARAGATO
|
December 16, 2019 at 7:46 am
Ok, thanks anyway.
|
