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
Mixing paying and non-paying attendees | Event Espresso - Staging Server

Support

Home › Forums › Calendar › Mixing paying and non-paying attendees

Mixing paying and non-paying attendees

Posted: December 17, 2012 at 8:29 am

Viewing 1 reply thread


Bjørn Tore Stig

December 17, 2012 at 8:29 am

Hi,

We have a client that has a rather intriguing request. They need a solution where one can make group-registrations, but where the person that registers as the prime attendant does not necessarily take part in the event and thus should not pay.
Is it possible to mark/tag in any way that the person who makes the booking should not be billed?
I’d hate to hack into the code myself, it makes upgrading a rather intense experience :-)

Regards


Josh

December 17, 2012 at 2:08 pm

Hi Bjørn,

There isn’t a feature that handles registrations in the way you’re describing. Have you considered labeling the registration form fields as “Attendees” instead of “Registrants” to help clarify that the people that plan on attending will need to pay for the registration?
Viewing 1 reply thread

The support post ‘Mixing paying and non-paying attendees’ 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.

Status: closed

Updated by Josh 12 years, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server