Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 attendee limit issue with paid attendees | Event Espresso - Staging Server
We have an event with the attendee limit set to 6, max group registrations set to 5, two price options and payment by credit card (Auth.net SIM). This morning we had 9 people successfully register and pay for that event, 6 of which were for one price option and 3 for the other. Looking at the time stamps, it appears that there were a total of 6 registrations, with 3 of those including 2 people. (Sounds like a “two trains leave the station..” algebra problem, doesn’t it?)
Any ideas why or how this happened and how we can prevent it from happening again?
The only reason I can see that occurring is due to a timing issue, as in the users registered at the same time. We are looking to put a small fix in future versions to reduce the likelihood of it happening although it is already unlikely to happen often.
What do the timestamps say?
Sounds like a “two trains leave the station..” algebra problem, doesn’t it?
Very much so, I hated those as a kid, still not fond of them now.
Viewing 1 reply thread
The support post ‘attendee limit issue with paid attendees’ 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.