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
Attendee limit base on Membership level | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Attendee limit base on Membership level

Attendee limit base on Membership level

Posted: March 19, 2014 at 6:14 am

Viewing 1 reply thread


Brian Coogan

March 19, 2014 at 6:14 am

WP Version : 3.8.1
EE Version : 3.1.30
New Installation.
I have purchase EE4 but for add-on issue i have install EE3.
In my website 3 type of membership level. 1. Org A, 2. Org B, and 3. Org C.
Org A can register up to 2 people per event at member rate
Org B can register up to 3 people per event at member rate
Org C can register up to 4 people per event at member rate
member Price different from Standard Pricing.


Josh

March 19, 2014 at 3:32 pm

Hi Brian,

Event Espresso doesn’t have a feature that allows for limiting a number of tickets per user account based on a membership level. This may be something that one of the developers on this list may be able to give you a quote for:

http://staging.eventespresso.com/developers/event-espresso-pros/

I know that IvyCat has done some work with integrating different S2member-level ticket pricing, so they may be a good one to check with first.
Viewing 1 reply thread

The support post ‘Attendee limit base on Membership level’ 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

Notifications

This topic is: not resolved
Event Espresso - Staging Server