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
Ticket Type Per Attendee | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Ticket Type Per Attendee

Ticket Type Per Attendee

Posted: July 6, 2012 at 2:34 pm

Viewing 3 reply threads


sboisvert

July 6, 2012 at 2:34 pm

Good day,

I was wondering if having a different ticket type per attendee was something that was schedualed as a feature in 3.2, if not could I suggest it as a wishlist item? It would be greatly useful for us to have users the ability to buy different types of tickets for different attendees.

Thank you,


Josh

July 6, 2012 at 3:04 pm

The registration process in 3.2 has been overhauled to include this feature. You can already get this type of functionality with the Multi Event Registration add-on in 3.1.


sboisvert

July 6, 2012 at 3:22 pm

How much of a change is 3.2 over 3.1? Regarding the translation of events and if we were to add a bunch of actions and filters to events based on the 3.1 code, would we have to redo alot of the work for 3.2? If so, can we get access to the 3.2 code to start working off that codebase with the understanding that it is in Alpha mode?


Josh

July 6, 2012 at 3:44 pm

Big change. We haven’t written the conversion script to convert events created in 3.1 to work with 3.2. Once that is finished + a few other front-facing features are working, we will be releasing a beta.

Viewing 3 reply threads

The support post ‘Ticket Type Per Attendee’ 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