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 count incorrect | Event Espresso - Staging Server
I have an event that is showing as full ( i.e. 9/9 attending). My concern is that there are only 7 attendees registered and paid or with pending payment for this event. I use this program to book small workshops and because of the high overhead costs of these workshops, really need to fill these events which is a problem when workshops that are only partially full show up as at capacity to people wanting to register.
After reading some of the other support forums I did double to check that my default payment status for events was set to “incomplete” which it was. Can you suggest an other reason why the attendee count would be off?
In addition to the general setting default payment setting, there is a default payment setting on the right side in the event editor for each event: “Default Payment Status for Event: “. Do you allow group registrations with no info required for the additional attendees? This allows the primary attendee to buy multiple tickets, so you could have 7 attendees, but one has 3 tickets, so 9 slots are taken up.
In another forum thread I advised you to update your Event Espresso version to resolve that issue. It could be that the update will also resolve this, but if not we can look at it again after the update.
Viewing 3 reply threads
The support post ‘Attendee count incorrect’ 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.