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
Multiple Tickets Purchased Per Event Per Ticket Price - How to | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Multiple Tickets Purchased Per Event Per Ticket Price – How to

Multiple Tickets Purchased Per Event Per Ticket Price – How to

Posted: April 17, 2013 at 4:03 pm

Viewing 4 reply threads


Brian Siddle

April 17, 2013 at 4:03 pm

Hello, I have a brand new installation. I am setting up events that have multiple prices. I would like people to be able to select multiple seats at each price.

I am missing something I am sure. Right now when I set up multiple price options my events are set so that a person can select one price and then add additional attendees at that one price. I would like it so that they can select the number of attendees they want for each price. For example, 2 adults, 2 kids and 1 senior. Now if they select the adult price they can only select to register additional adults. Sorry, what am I missing?

– I have been allowing group registration on these events and “no additional info required”.

Looking at documentation I see the look I am going for here
http://staging.eventespresso.com/wp-content/uploads/2012/10/view_cart_multiple_prices.png

but I’m not sure what I am missing?

 


Josh

April 17, 2013 at 4:18 pm

Hi Brian,

Event Espresso 3.1’s multiple price option feature is limited to one price type per registration processed. There is a work around that involves using the Multi Event Registration add-on, and Chris wrote up a step by step guide on how to set up a single event with multiple price types and move the registration process to the cart here:

http://staging.eventespresso.com/wiki/multiple-events-registration-use-add-to-cart-link-instead-of-default-registration-form/

We’ve just released the beta of Event Espresso 4.0 which does not have this limitation. It will allow for multiple selections without Multi Event Registration.

If you have a site where you’d like to test the new version’s beta out, you can opt-in to the pre-release channel on your account page (there’s a box that you can check that will opt you in) and you can download 4.0. Please note that 3.1.x doesn’t have an update path to 4.0 yet, so 4.0 will have to be installed on a fresh site that doesn’t have Event Espresso database tables on it from a prior version. We’ll be including an update script in a future version.


Brian Siddle

April 17, 2013 at 4:24 pm

Thank you for the response. Can I set up the install of 4.0 on a separate address to test and get set up?

That workaround seems like it would do the trick for now but I am interested in the 4.0 update.


Brian Siddle

April 17, 2013 at 4:27 pm

Just noticed though that the workaround makes it a bit odd when having to enter attendee info. It makes you do it for the primary attendee within each price selection and the naming conventions go a bit “odd”. I will check out 4.0 I think.


Josh

April 17, 2013 at 4:45 pm

Yeah you can set up 4.0 on a different site and test it out there. If you have any questions or comments about 4.0 please start a new topic in the pre-releases forum:

http://staging.eventespresso.com/forum/pre-releases/

Viewing 4 reply threads

The support post ‘Multiple Tickets Purchased Per Event Per Ticket Price – How to’ 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