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
EE 4 / WP user compatibility | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › EE 4 / WP user compatibility

EE 4 / WP user compatibility

Posted: March 21, 2014 at 10:03 am

Viewing 1 reply thread


Patrick Henry

March 21, 2014 at 10:03 am

I have a functions for which is access is managed by WP users based on paid “members” and non paid “subscribers”. Members get discounted pricing. We currently manage that function in EE3 via a promotion codes that we give to all members… Not ideal, as it eventually is given out to the public and we have to change it. (Our members typically sign up for multiple courses (events) over a year).
Does EE4 have the ability to automatically apply a discount to ticket prices when a “member” is logged in and not apply it when a “subscriber” is logged in?


Josh

March 21, 2014 at 1:16 pm

Hi Patrick,

It doesn’t at this time, but we are planning on making a similar add-on to Event Espresso 3’s WP user integration for Event Espresso 4. In the meantime you might want to have a look at the S2 member integration add-on that allows different prices based on the user level.

http://staging.eventespresso.com/wiki/s2member-integration/
Viewing 1 reply thread

The support post ‘EE 4 / WP user compatibility’ 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