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
Limiting attendee numbers at different levels with s2member integration | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Limiting attendee numbers at different levels with s2member integration

Limiting attendee numbers at different levels with s2member integration

Posted: March 23, 2014 at 8:50 am

Viewing 2 reply threads


Jason Lee

March 23, 2014 at 8:50 am

Hi there,

I am wondering if there is a way to limit the amount of tickets/attendees for different levels with EE3 and the s2member pro addon.

I need level 1 users to be able to reserve 1 ticket
level 2 users to be able to reserve 1 or 2 tickets
level 3 users to be able to reserve 1,2,3 or 4 tickets

Any help would be greatly appreciated as this is a must have for me even if I need to pay for additional coding but was hoping there might be an easier way.


Dean

  • Support Staff

    •

March 24, 2014 at 1:05 am

Hi,

Unfortunately there isn’t a way to limit ticket purchases like that, it would need to be custom developed.


Jason Lee

March 24, 2014 at 3:49 pm

Ahh, thanks for your help Dean. I’ll reach out to someone for the custom dev
Viewing 2 reply threads

The support post ‘Limiting attendee numbers at different levels with s2member integration’ 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 Jason Lee 10 years, 10 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server