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
Best Practice: Multiple ticket types for single event | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Best Practice: Multiple ticket types for single event

Best Practice: Multiple ticket types for single event

Posted: February 25, 2014 at 2:00 pm

Viewing 3 reply threads


josh g

February 25, 2014 at 2:00 pm

What is the best practice to accomplish the following:

– Members pay annual dues which includes tickets to all events. The annual dues process is outside of EE. Members must still register for events to specify their meal preference, the cost of the ticket to them is $0.
– Guests can attend but must pay the full ticket price.
– Members can register for themselves and their guests, obtaining $0 tickets for themselves and paid tickets for their guests.

I set up the member add-on and allowed multiple attendees, but it will only allow one ticket type per registration. So if there is 1 member and 2 guests, the system will only allow for 3 of the same type of tickets.

Thank you in advance.

WP Version: 3.8.1
EE Version: 3.1.36.4.P
Plugins: Business license plugins available as needed


Garth

  • Support Staff

    •

February 25, 2014 at 4:15 pm

Hi Josh,

How are you today?

With the Multiple Event Registration addon (http://staging.eventespresso.com/product/espresso-multiple/) you can set a member price that is correlated to the non-member price, e.g. $200 (non-menbers) and $0 (members). The restriction will be based on whether they are logged-in to your website and have access to your event pages.

If members are purchasing tickets for guests, you’ll probably have to create a guests ticket but the ticket will have to be full priced for members.

You’ll use the Multiple Event Registration addon (http://staging.eventespresso.com/product/espresso-multiple/) to offer registrants the option for different tickets.


josh g

February 26, 2014 at 12:30 pm

Thank you Garth. That worked out very well.

I used the MER to allow for multiple tickets and simple created two types of tickets, guests and members with different prices.

I used the members to restrict registration to site members.


Josh

February 26, 2014 at 2:23 pm

Glad to hear that worked out for you Josh.
Viewing 3 reply threads

The support post ‘Best Practice: Multiple ticket types for single event’ 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.

The original Forum description...

Status: closed

Updated by Josh 10 years, 10 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server