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 Number of all attendees/attendes/export don't match | Event Espresso - Staging Server
Hi there,
Why is the number of all attendees and the attendees to a single event different? Please see screenshot here: http://www.primetimeinottawa.ca/wp-content/uploads/2014/02/screenshot-no-of-attendees.jpg. The number of attendees that gets exported is yet again different (there are 2 less on the list than what shows up under ‘all attendees’. Can you please explain why there is a difference between these numbers?
Thank you!
Sarolta
Event Espresso version 3.1.36.1.P
WordPress version WP 3.7.1
Event Espresso – Social Coupons by Seth Shoultes version 1.5.3.1,
Event Espresso – MailChimp Integration by version 1.2,
Event Espresso – Multi Event Registration by Seth Shoultes version 1.0.5.p,
Event Espresso – Ticketing by Event Espresso version 2.1.p,
Event Espresso by Event Espresso version 3.1.36.1.P,
The all attendees count is looking at the quantity of tickets for all attendees, whereas the count on the event itself is looking at the quantity of tickets where the attendees payment status is Completed, Pending, or Refund. Do you have any attendees with payment status Incomplete?
Yes, we do – that will account for the difference. Thanks!
Sarolta
Viewing 2 reply threads
The support post ‘Number of all attendees/attendes/export don't match’ 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.