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 Reduced Registration Rate for Couples | Event Espresso - Staging Server
I’m building a convention registration site. We want to offer an individual registration rate ($149), and a couple registration rate ($290) that offers a savings/better deal over buying 2 individual registrations.
I have it set up now as 2 separate ticket prices for Couple vs. Individual. However, if someone chooses the “Couple” price, it only allows them to input info for themselves (and not the additional person.) If I click “allow group registrations,” then it will add prompts/fields for them to register for 2 people, BUT it will charge them for 2 tickets at the Couple rate rather than one.
Is there a workaround for this?
Site is here: http://qconvention.com/register/
I’m running EE 3.1.33.2 Personal license with no add-ons on WordPress 3.5.2.
2) You could continue like you’ve done, but add the attendee information as questions in the registration form. You’d want to make sure those additional questions for the second attendee are optional in the case that someone only purchases a second ticket. Doing it this way will also mean that the second attendee is not registered as its own attendee. They wouldn’t get their own ticket and such, but they would be associated with primary registrant in the registration questions.
I’d recommend #1.
Viewing 1 reply thread
The support post ‘Reduced Registration Rate for Couples’ 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.