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 Price Modifier not working when question only applied to additional registrant | Event Espresso - Staging Server
My client wants to offer discounted pricing when 2 people register for an event. Single applicant price is $686 but when 2 people book together the price is $1200 for both ($600 each).
I’m using a Price Modifier question only for the additional registrant but it’s not applying the discounted price. Note: I can’t apply the Price Modifier question to the primary attendee because the discount could be given to a single applicant without meeting the 2-attendee requirement. Similarly, client is reluctant to use coupons to avoid giving discount when the 2-attendee requirement is not met.
I’ve already applied volume discount to another event (btw: it’s a shame volume discounts can’t be created for multiple events with discrete discounts – add this option to the EE dev wish list, please?)
Details:
WP: 3.7.1
EE: 3.1.34.1.P
EE Price Modifier: 0.0.3.1.B
Site: In Dev
Sorted! We weren’t using MER but we had the plugin activated, so I deactivated it (and updated to latest version of EE) and Price Modifier is now working on 2nd registrant.
Would be good if it reduced the ticket price for each applicant, instead of current functionality which is to reduce the total price. But no bother, it does the job.
Thanks again for the great support.
Viewing 2 reply threads
The support post ‘Price Modifier not working when question only applied to additional registrant’ 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.