Posted: September 9, 2014 at 2:36 pm
|
Hello, We’re having issue with the count of registrant in our events, which make the event getting sold out before it’s full. Here are 3 screenshot where you can see : 1. in the event, the top right corner says 23 approved registration 2. still in the event, the total sold for the datetime is : 36 , which causes the event to be sold out 3. in the list of registrations, filtered by this event, it confirms we only have 23 registrations note : the trash bin is empty (because EE includes the registrations in the bin, which is a bug) Please help us with this ๐ Vincent |
Hi Vincent, The registration approved value comes from the Regs column. That event still has room for additional registrations: 42-36 = 6 more spaces Was the datetime limit originally lower and was recently increased? — |
|
|
Yes, we increased the limit in order to accept more registrant, also, in the registration views, we can see that there is only 23 registrant, and not 36. I guess we don’t get the difference between the ticket sold and the registrations column. At first, we thought it was due to the fact that 1 registration = few tickets , but after checking in the “Event checkin” filtered by this event (http://tractr.net/EE4.png), we can see that there is only 23 peoples coming to the event, and not 36. Thank you |
Hi, Can you change the event status from sold out to published and save changes? http://cl.ly/image/2T0e06440644 This is done through the event editor. — |
|
|
September 10, 2014 at 11:06 am It is already published as you can see in the screenshot EE2.png but when the count of ticket sold reach the limit, the event is shown as sold out in the front end. I think the problem comes from the wrong count of ticket sold, I suppose it should be a high priority bug since it blocks event registrations, Thank you ๐ |
September 10, 2014 at 11:22 am Hi Oliver, It looks like you are using a default Registration Status of Approved, is that correct? Which version of Event Espresso 4 are you currently running? |
|
|
September 10, 2014 at 12:38 pm yes it is correct, all new registrant are set as Approved. version is : 4.2.7 , we’ve upgraded our staging environment to 4.3.1, but we still need to adjust the translations (french) and we’re waiting for this issue to be resolved : https://eventespresso.com/topic/dompdf-encoding/ thanks |
Hi, Could you go ahead and update your site to the current software? We troubleshoot with the current software, not older versions. This may create some confusion if we mention something and you are seeing something else (due to older software). Thanks. — |
|
|
Ok I just updated our staging site, imported data from live, and ran the EE migration. The problem is still here. I will give you access to the staging environment so you can see the problem by yourself. Thanks |
|
I just sent you the access for the staging environment. The event I showed you in the screenshots is this one : “INITIATION ร L’ENTRETIEN MOTIVATIONNEL” is the title Thank you |
Hi, This event ran out of space which would have set it to sold out. You then raised the datetime limit to increase the available space. What is the current issue with this event? — |
|
|
Lorenzo, I can’t explain this better than I did in my first message : the event has 23 registrations, BUT in the event edit screen, we can see that the count of ticket sold is 36, this is causing the event to be sold out, so we raised the limit. My question : Thanks |
September 11, 2014 at 11:33 am Hi Oliver, The issue here is due to a bug introduced when using a default registration status of Approved when using EE4.2.X Basically when the user selected the tickets and confirmed on the ticket selector (before entering any details) with the default registration set to approved it would trigger the function to add the ticket values to those columns in the db. So this will continue to happen whilst you are using version 4.2.X Version 4.3.0+ fixes this issues, however the values are already stored within the database so simply updating will not fix those values. I can guide you through where to fix the values for that event, but whilst the live site is still on 4.2.X those values will continue to be calculated incorrectly and the values within the database incorrect once again whilst you are using ‘Approved’ as the default registration status. Do you need the registration status to be Approved? |
|
The support post ‘wrong number of registrant’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.