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 Additional Attendee Receipt - Restricting info | Event Espresso - Staging Server
Currently if I register for my event, and add an additional attendee, I receive a confirmation email with the total amount charged, which is great. My problem is the attendee(s) also receive this grand total. Is there a way to only show the additional attendees the amount paid for their registration rather than the group total?
Not currently no. We are changing the way that emails and messages are done in version 4.0 so that emails to the Primary attendee and to Additional Attendees can be different, thus allowing one to have the total and not the other.
Thanks for your response Dean. Just to confirm, if the ‘Payment Confirmation Email’ and the ‘Default Registration Confirmation Email’s’ are turned on, the primary registrant, and the attendees will receive both emails? I can’t specify to have the payment confirmation only be sent to the primary registrant?
Thanks for your reply Dean. In testing, currently the person who pays, and the additional attendee receive the payment confirmation email. Both receive both emails. I have test transaction turned on and my registration for can be found here:
My apologies, it seems I was incorrect, the payment email goes out to all attendees.
While it isn’t possible to change this currently (at least not without modifications) 4.0 has an improved messaging system coming.
Viewing 5 reply threads
The support post ‘Additional Attendee Receipt – Restricting info’ 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.