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 One event, multiple locations... | Event Espresso - Staging Server
My client has a network of doctors with their own landing pages on their website. All of the doctors are on the same event schedule. So, although there may be 6 events listed in a given month, each event is taking place at 10 different locations.
Is there a way for us to display the events but allow the registrant to choose which location they’ll be attending?
This topic was modified 12 years, 4 months ago by Dustin Olenslager.
This topic was modified 10 years, 11 months ago by Josh.
There’s no specific way to do that currently, but here are some workarounds.
Currently you can use the Multiple Event Registration plugin to offer a choice of events to sign up to. This will work, but means duplicating the event in order to get the number of locations.
In 3.2 we will offer an option to add various price levels to an event – you could use this system to create options that your visitors could select. Only issue is currently it is multi select, so a user potentially could select and purchase multiple venues at once.
While Event Espresso 4 doesn’t exactly support displaying multiple locations for one event, Dean’s idea to offer different tickets for each location is solid. Event Espresso 4 beta is officially released:
The support post ‘One event, multiple locations…’ 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.