|
ARAGATO
|
June 6, 2019 at 12:57 am
We are using the waitlist plugin.
Right now, people can add themselves to the waitlist of one event in an indefinite amount. We have events where people have registered themselves like 10x to the waitlist with the exact same data. It does not matter if that person is logged in or not.
That leads to another, and the main issue.
Right now, we have several events that are set to “sold out”, because the eventdata limit has been reached. EE apparently bases the limit on the total number of sold tickets + registrations (incl. waitlist). That leads to many courses being status “sold out” although they are not really sold out but just many people on the waitlist.
Event details:
https://i.imgur.com/6LGEmWp.png
Waitlist:
https://i.imgur.com/7zUN7SA.png
|
|
Josh
|
June 6, 2019 at 8:45 am
EE apparently bases the limit on the total number of sold tickets + registrations (incl. waitlist).
That’s incorrect. Event Espresso checks the number of approved registrations for a specific datetime. If the registration status is either pending payment or waitlist, then it’s not counted toward the limit.
|
|
ARAGATO
|
June 6, 2019 at 9:37 am
Then why is that although the limit is set to 9 and there is only 8 approved registrations for that datetime the event is still set to sold-out?
Did you look at the screenshots I provided?
|
|
Josh
|
June 6, 2019 at 9:45 am
I did look at the screenshots but the screenshots don’t answer that question.
|
|
ARAGATO
|
June 6, 2019 at 10:11 am
Which question?
The screenshot shows that there are 8 tickets sold (status approved).
Also, there are 4 people registered with status wait list.
You can see it here https://i.imgur.com/6LGEmWp.png on the right hand side.
On the bottom you see the event date which has a limit of 9 and also the tickets for that event date have a limit of 9. The event is set to sold-out by EE and I cannot set it to active manually.
According to your answer … Event Espresso checks the number of approved registrations for a specific datetime. If the registration status is either pending payment or waitlist, then it’s not counted toward the limit… the event should still be active with one last remaining slot. However it is not. And that is the issue at hand.
Or am I missing something?
|
|
Josh
|
June 6, 2019 at 10:15 am
Which question?
This question:
Then why is that although the limit is set to 9 and there is only 8 approved registrations for that datetime the event is still set to sold-out?
You might check in the database for the ticket sold count to see if that somehow got set to 9 when it should be 8.
|
|
ARAGATO
|
June 6, 2019 at 10:28 am
I just checked and there are only 8 registrations.
Also I check the numnbers.
I set the limit of the datetime and ticket to 12 (8 approved regs + 4 waitlist) and it still did not let me set it to active.
https://i.imgur.com/LhCcdT2.png
Once I set the limit to 13 it worked.
Then I set it back to 12, and it did not work again.
I deleted one of the waitlist regs making it only 3 on the waitlist.
Now the limit of 12 works, too.
https://i.imgur.com/SZyOjK0.png
I looks like there is some data corrupted or something. Why does it show 12 regs?
You might check in the database for the ticket sold count to see if that somehow got set to 9 when it should be 8.
Where do I find that ticket sold count and can I manually set it to 8?
|
|
Josh
|
June 6, 2019 at 11:01 am
you’ll find that in the _esp_ticket table (TKT_sold column) for the ticket. You could also check the _esp_datetime table (DTT_sold) too.
|
|
ARAGATO
|
June 11, 2019 at 4:04 am
I just checked the values in the DB and everything seems in order.
Ticket:
https://i.imgur.com/smeKcft.png
Datetime:
https://i.imgur.com/rsRIYdf.png
Also, in the registrations table there are 8 RAPs and 4 RWL regs.
https://i.imgur.com/Ad0nLJ2.png
Event still sold out without being able to set it to active.
|
|
Tony
|
June 11, 2019 at 7:12 am
Can you add a screenshot of your ‘Event Wait list’ section for the above event, please?
The sold out status will not switch if you have waitlist registrations to be approved/switched to another status, simply because those waitlist registrations would be considered the ‘next’ registrations to be in the queue as it’s the whole point of the waitlist registrations.
To explain, when an event has a single space remaining and a user selects a ticket to register onto that space, that space will be ‘reserved’, if ‘sold’ + ‘reserved’ == ‘qty’ the event will show as sold out if a sold out check is called on it whilst that last ticket is in reserve.
If that happens, the waitlist form will show if you have them setup as the event has a status of sold out. If users then add waitlist registrations to the event then EE will NOT switch back to upcoming/available, even if that ‘reserved’ ticket expires with no approved registration on it.
The reason for that is those additional waitlist registrations would be considered the ‘next’ registrations to possibly be Approved. If we switched the event to upcoming and allowed another registration, those waitlist registrations account for nothing as you’ve just opened the event back up for registrations from anyone.
The ‘space’ you are trying to open, has already essentially been reserved by a waitlist registration, so promote the next waitlist registration in the list to pending payment and see if that user wants to take the place, if not, the next and so on.
|
