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 | Event Espresso - Staging Server
I have a problem – I set limit for attendees to 15. However, the system did not close the registration when it reached that limit and actually let 16th person register. I think the problem is that it only accounts for those who paid. This was not an issue with the previous versions. Any ideas?
I think the problem is that it only accounts for those who paid.
This is by design. If you have an unpaid registrant, most times you do not want that person taking up a space that could be filled by a paying registrant. However, if you want to override this default behavior, you can change the default payment status to Pending. Pending attendees have not paid, but they do take up a space in the available spaces (this is how Event Espresso worked in very old versions in the past). http://staging.eventespresso.com/wiki/attendee-management/#payment-status
It worked like a charm! Thanks. We’re giving people the option of paying within 2 weeks of registration so that’s why I had to solve this issue. Thanks again!
This is very helpful indeed. However, I’d like to give my customers the option to pay online, using a pay link in the confirmation e-mail. I figured, when the status is set to pending, no online payment options show. Is there a way to work around this?
Regards, Edwin!
Viewing 3 reply threads
The support post ‘Attendee Limit’ 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.