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 multiple registrants | Event Espresso - Staging Server
1) Can there be individual receipts each person who is registered on a group registration. I want each to have their own, not a combined invoice.
2) Is there any way that this info can go to each of the peoples WP Members account if one person signs up many people? Is there a better option for this?
I’ve done some testing on this and the email notification will go to the primary attendee/registration.
I believe on your second question, you are asking if this information could be sent to each attendees account. Could you confirm so I can check with a team member?
Unfortunately this is not something Event Espresso currently supports.
Whilst it is possible to modify the email function to email all the attendees a copy of the invoice, this would be a copy of combined invoice.
Breaking down a combined invoice will depend on if the registration was created using MER or simply multiple tickets requiring information for additional attendees and would require significant customization’s to the registration process.
If each attendee requires a single invoice Event Espresso would required each attendee to run through their own registration.
Viewing 4 reply threads
The support post ‘multiple registrants’ 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.