|
trainadesign
|
February 4, 2019 at 11:59 am
Hey there,
We have an event that had a limit of 300. The event shows 170 registrations total, but said, sold: 300 / sold out. As a temp fix we upped limit to 500, since they did not want to stop at 170 and half fill the event.
Now it says: Sold: 369. Registrations: 170.
I checked the registration list, and it accounts for multiple registrations per event.
Running the Latest version of all plugins.
Please let me know what info you need to assist.
|
|
Josh
|
February 4, 2019 at 1:14 pm
Hi,
Can you post a link to the event in question please? Also, a screenshot of the datetime & ticket editor box will also be helpful.
|
|
trainadesign
|
February 4, 2019 at 1:21 pm
This reply has been marked as private.
|
|
trainadesign
|
February 4, 2019 at 1:21 pm
(sent as a private reply, just making sure you have access to that?)
|
|
Josh
|
February 4, 2019 at 7:12 pm
Hi,
May I ask is the Wait List add-on activated for the site, and if so, is the event’s Wait List setting “Auto Promote Registrants?” set to “Yes”?
|
|
trainadesign
|
February 4, 2019 at 8:01 pm
Hey Josh,
Yes: Event Espresso – Wait Lists (EE4.9+) V 1.0.0.p plugin is active
Yes: Auto promote settings for event:
Wait List Spaces: 100
Auto Promote Registrants: Yes
Manually Controlled Spaces: 0
|
|
Josh
|
February 4, 2019 at 8:06 pm
Thank you. We did find an issue where if “Auto Promote settings for event” was set to Yes for an event, then there was a potential for reserving or releasing registration spaces before actually changing the internal value for the registration status. In other words, ticket and datetime sold values would sky rocket indicating that some recursion was happening somewhere.
This issue is fixed in the next version of Event Espresso 4 which will be available later this week.
|
|
trainadesign
|
February 5, 2019 at 5:22 pm
Ok great, I will look out for the update.
in the meantime, with active events and registrations open and out to 170+ users, capacity at 300, and the limit bumped to 500 to temporarily-patch/avoid this error, is there anything we can do to fix the event(s) currently experiencing this, or will we have to manually monitor these events?
Also, will the update fix existing events that have this issue, or will it only patch new/future events without registrations yet ?
|
|
Tony
|
February 7, 2019 at 7:16 am
Also, will the update fix existing events that have this issue, or will it only patch new/future events without registrations yet ?
It will not fix existing events as the values have already been saved to the DB. The fix will just prevent the recursion from happening in the future.
The values would need to be fixed in the database itself, however, until the fix is released you’ll continue to run into the same problem with ‘Auto Promote Registrants’ set to ‘Yes’, have you switched that to no?
|
|
trainadesign
|
February 7, 2019 at 3:21 pm
Yes, for all existing events we have switched to No, and will keep this as the default moving forward. Do you have an specific instructions/documentation for manually updating the DB?
|
|
Josh
|
February 8, 2019 at 9:00 am
We generally do not recommend making manual updates to the database unless you’re very comfortable with doing so. If you go that route, you do well to make a database backup first. Then you use a tool like phpmyadmin or similar to go in and make edits to the _esp_ticket and _esp_datetime tables. The specific columns are TKT_sold and DTT_sold, respectively.
|
|
trainadesign
|
February 8, 2019 at 10:10 am
This reply has been marked as private.
|
|
Josh
|
February 8, 2019 at 10:23 am
Hi,
The topic will stay open for 14 days, then if no further replies by then, it will automatically close.
|
