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 paid attendees | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Number of paid attendees

Number of paid attendees

Posted: November 11, 2012 at 9:26 am

Viewing 1 reply thread


Geo Loo

November 11, 2012 at 9:26 am

Event Espresso creates a separate record for these:

  • People who register but don’t pay
  • People who are secondary attendees, and then marks those attendees as unpaid

Who do I know how many people have actually paid?


Josh

November 12, 2012 at 2:38 pm

Hi there,

Do you have the event set up to require additional attendee info?
If so, each of the secondary attendee records will get marked as paid when the primary registrant pays.

If you have the event set up to not require additional info, in Event Espresso 3.1.x, only one unique attendee record is created, and the quantity of tickets is displayed on the Edit Attendee Data screen.

Does that help clarify things?
Viewing 1 reply thread

The support post ‘Number of 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.

The original Forum description...

Status: closed

Updated by Josh 12 years, 2 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server