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 Event with individual tickets and table tickets with X amount of slots | Event Espresso - Staging Server
Here goes: My non-profit is hosting an even where people can buy three different classes of tickets: singles for $150 (up to 5 at a time), tables for $1200 (which come with 8 tickets), and sponsorships (price varies) (which get a few complementary tickets). I am able to create all the different ticket types, but don’t quite know how to get the table and sponsorship tickets working like I want. Basically, if someone were to buy a table, how could I go about getting information for the 8 attendees that the table holds? I realize that an individual could just buy multiple tickets, but selling tables is something the higher ups want to do. Also, how would I handle a sponsorship that gets X amount of free tickets given their level of sponsorship. Any thoughts?
Currently this isnt possible without some custom development. We are planning on adding this sort of functionality (bundled tickets) into future versions but it hasn’t been coded up yet.
Thanks for the info. While it would be nice to have this function now, it’s not super critical for our event to happen, so we can wait. It’s nice to know that this function is on the docket for future versions. I look forward to it.
Viewing 2 reply threads
The support post ‘Event with individual tickets and table tickets with X amount of slots’ 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.