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
Restricting Attendee Reigstration at Different Price Levels | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Restricting Attendee Reigstration at Different Price Levels

Restricting Attendee Reigstration at Different Price Levels

Posted: July 20, 2013 at 11:55 am

Viewing 1 reply thread


Scott Moore

July 20, 2013 at 11:55 am

We currently have the personal license of Espresso, and I am trying to restrict the number of tickets sold at different price points.

We currently have four prices points:
MR – $50 w/ 2,250 Tickets to be sold
ZB – $40 w/ 450 Tickets to be Sold
ZW – $30 w/ 150 Tickets to be Sold
ZL – $25 w/ 150 Tickets to be Sold

If we cannot find an affordable solution and workaround, then I would like to take the next steps for a refund.

Thanks,

SB


Sidney Harrell

  • Support Staff

    •

July 21, 2013 at 6:52 pm

You could use the seating-chart add-on, but it may be cumbersome with the number of tickets that you have for each price point. I think your better alternative is to create separate events for each price point and use the MER add-on. You can create a category to group the four together, and use the category attribute on the EVENT_LIST shortcode to make a nice display.
Viewing 1 reply thread

The support post ‘Restricting Attendee Reigstration at Different Price Levels’ 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 Sidney Harrell 11 years, 6 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server