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
Complex Event Scenario | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Complex Event Scenario

Complex Event Scenario

Posted: November 21, 2012 at 12:59 pm

Viewing 1 reply thread


Verdon Vaillancourt

November 21, 2012 at 12:59 pm

Hi,

I have an event scenario that if eventespresso can manage, we will purchase.

In a nutshell, the event is a one day event with 3 sessions. Registrants must choose from one of three activities for each session. There are limited seats available for each choice, so there needs to be some form of inventory control on those activities. Ideally, we will also be able to collect some meta data from registrants, and there would be some mechanism to prevent registrants from registering multiple times. We do not need to collect fees for the registration.

Any thoughts would be welcome.


Garth

  • Support Staff

    •

November 26, 2012 at 9:32 pm

Hi Verdon,

How are you today? Sorry for the delay in responding, we’ve been swamped the past few weeks….

We don’t have a system to require/prohibit attendees from registering. We will create dependent events in the future, but we don’t have it yet. Have you test driven Event Espresso (http://staging.eventespresso.com/download/test-drive-event-espresso/) for free to look at ways it might work for you?
Viewing 1 reply thread

The support post ‘Complex Event Scenario’ 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.

Status: closed

Updated by Garth 12 years, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server