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 Non-attending booker | Event Espresso - Staging Server
Is there a way for someone (primary booker) to book on behalf of a group but not attend the event themselves (i.e. we can still capture their data but it doesn’t subtract from the total allowed attendees figure)?
Maybe by some checkbox or dropdown “Are you attending this event” Y/N?
The only way I can think of for this to work is to create a question group only for the person booking the event so you can capture that information without charging them. Once you have create question group, you can assign it to the event.
There are no conditional questions currently. You could just add a required question that asks if they are attending and if so to fill out X questions below.
You could create a faux conditional situation by using javascript to hide X questions if the checkbox isn’t ticked and then show them if it is and add a required class to them.
Thanks for fast response Dean and the suggestion – that’s do-able but what controls whether the main booker is taken through the payment and attendee list system or not?
I think you would need a message, saying if they are attending to fill in their details as the primary or additional attendee, as they would have to fill in those questions to get registered.
Viewing 7 reply threads
The support post ‘Non-attending booker’ 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.