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 Multi event confirmation emails | Event Espresso - Staging Server
Is there a way to combine confirmation emails for multiple event registrations? When someone registers for our event along with the several add-on sub-events that we offer they could be getting 6+ confirmation emails.
The following thread seems to suggest that they should already be combined:
The forum thread you linked to is over a year old and there have been hundreds of changes to the core plugin since then. This particular issue has gone back and forth a number of times with other users complaining that if the confirmations are all in one email, then the individual attendees never get notified. Presently the admin receives a confirmation email with all the events registered for in a single checkout. You can add all the events that a specific attendee has been registered for to the email confirmation by using the [attendee_event_list] email shortcode. I’m not sure how you have your events/sub-events set up, but if you’re taking payment on one event (e.g. event registration) but not on the other events (sub-events/sessions), then you could add that shortcode to the payment confirmation email and not the registration confirmation email and set the registration confirmation to not be sent before payment is received. That should prevent the attendees from getting multiple emails since payment would only be taken once.
Viewing 1 reply thread
The support post ‘Multi event confirmation emails’ 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.