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
Overview of waiting list functionality / workflow | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Overview of waiting list functionality / workflow

Overview of waiting list functionality / workflow

Posted: July 4, 2012 at 5:07 pm

Viewing 4 reply threads


sheathe

July 4, 2012 at 5:07 pm

Hi,

Can you please clarify the purpose and functionality of waiting list / overflow events?

My impression was that the system would work something like this:

  1. Main event is full
  2. Join Waiting List button is now enabled
  3. Join waiting list allows people to register for the overflow event (and optionally to pre-pay using the payment gateways)
  4. If a registrant in the main event is deleted, first person on the overflow event is automatically moved to the main event (?)
  5. Confirmation email from thew main event is sent to the person who is no longer on the waiting list

I’ve followed the instructions on the documentation page for setting up a waiting list: http://staging.eventespresso.com/wiki/create-a-waiting-list-for-your-event/

This did help me to set one up, but when I tested deleting an attendee from the main event, nothing happened.

Well, actually, what did happen was that the person on the waiting list stayed there, and the main event was re-activated in the Event List. This means that a new site visitor can jump the queue and get a spot that was supposed to be reserved for someone on the waiting list.

Once it is configured correctly, how does the event administrator use the waiting list? (e.g. Can I manually move the first attendee from the overflow event to the main event and send them a confirmation email?)

Ideally it would be great to have a usage overview on the documentation page.

Thanks for your help.


Josh

July 5, 2012 at 9:29 am

It’s up to the admin to contact people on the waiting list to verify whether they would still be interested in attending. So it’s a manual process. If you have an event that is full, but you do get openings that can be filled by waitlist signups, I’d recommend manually closing the event for registration. Then contact the people on the waitlist and sign them up through the back-end of the site.


sheathe

July 5, 2012 at 5:54 pm

Thank you for the explanation & suggestion. You can mark this one resolved.


Jeff Wright

September 24, 2012 at 10:08 pm

I wanted to ask how it looks to an attendee if the event is full and they sign up. Is the waitlist automatically activated once the event is full?
Do they register, pay and then find out the event is full & they are on the waitlist? Do they see before hand that it is full & see the option to add themselves to the waitlist. Can the join the waitlist without paying?


Dean

  • Support Staff

September 25, 2012 at 3:10 am

Hi Jeff.

This may help you out http://staging.eventespresso.com/wiki/create-a-waiting-list-for-your-event/

This thread has been marked as resolved. As such I will be closing it for future answers. If you need to, feel free to create a new thread with your questions.

Viewing 4 reply threads

The support post ‘Overview of waiting list functionality / workflow’ 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