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
Event Registration Not Reflected on Back End | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Event Registration Not Reflected on Back End

Event Registration Not Reflected on Back End

Posted: November 12, 2013 at 11:04 pm

Viewing 2 reply threads


Andrew Randazzo

November 12, 2013 at 11:04 pm

I’ve done some test registrations and I get the confirmation emails, but I’ve capped the event for 6 people but when I look at the event in the Event Overview it still shows as 0/6 attendees. Why is this? The only part of the registration I haven’t done is pay, but I want people to register with payment as optional.


Dean

  • Support Staff

    •

November 12, 2013 at 11:16 pm

Hi Andrew,

If the attendee is marked as incomplete (a red no entry symbol) then the event capacity is not affected. If you need people to register even without paying and still affect the capacity, you need to change the “Default Payment Status for Event:” to Pending.

This can be done either in the event itself (just affects the event) or the General Settings (affects all events).


Andrew Randazzo

November 12, 2013 at 11:18 pm

Got it, thank you so much.
Viewing 2 reply threads

The support post ‘Event Registration Not Reflected on Back End’ 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 Andrew Randazzo 11 years, 2 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server