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
Registration Report as Attendees Stopped | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Registration Report as Attendees Stopped

Registration Report as Attendees Stopped

Posted: July 16, 2013 at 11:46 am

Viewing 1 reply thread


RICHARD BENNETT

July 16, 2013 at 11:46 am

I’ve searched and searched and no one seems to have asked this precise question / gotten an answer:

Since the most recent update, registrations stopped counting as “attendees”, as reported on the Event Overview screen (internal) and “Available Spaces” (displayed to the world).

How can we put it back to the old way — i.e. a registration is all that’s needed to be counted for a reservation. This is because we use this for reservation purposes only, taking payment at the door and not pre-payment.

Please help!


Josh

July 16, 2013 at 2:12 pm

Hi there,

You can set the default payment status to pending in Event Espresso>General settings. This will make each registration count against the attendee limit.

Viewing 1 reply thread

The support post ‘Registration Report as Attendees Stopped’ 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.

Event Espresso - Staging Server