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
Seating Chart - Multiple Seat Selection | Event Espresso - Staging Server

Support

Home › Forums › Seating Chart › Seating Chart – Multiple Seat Selection

Seating Chart – Multiple Seat Selection

Posted: January 6, 2013 at 5:51 am

Viewing 1 reply thread


Alessandro Aliakbargolkar

January 6, 2013 at 5:51 am

Hi I would like to follow up this previous topic: http://staging.eventespresso.com/topic/multiple-seat-reservation/ (unfortunately replies are not allowed there at this moment)

I agree with Ivo Mokros’ suggestion that the process flow should be as follows:
1. Present the seating chart to the customer, showing available seats
2. Customer selects multiple seats, these get added to a cart
3. Customer confirms seats, and enters their name and email (as per selected question group)
4. Customer pays

Right now I am unable to select multiple seats from the chart without dismissing it everytime. Likewise, I do not want to have the user input personal data for each seat he wants to purchase…. Can this be fixed soon?

Thanks
Alessandro


Josh

January 7, 2013 at 3:19 pm

Hi Alessandro,

The way that the seating chart add-on ties into the registration form makes it dependent on their being a form for each seat, so this isn’t something that can be changed without completely overhauling its present design.
Viewing 1 reply thread

The support post ‘Seating Chart – Multiple Seat Selection’ 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 Josh 12 years ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server