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 event confrimation emails | Event Espresso - Staging Server
I have the multiple bookings extension installed on my site along with the ability to add time slots to the times.
The user selects a time slot and how many ‘tickets’ they want to purchase. e.g. x2 adult and x3 child on Monday and x1 adult, x2 children on Tuesday.
Once I select ‘confirm booking’ I am asked to complete all information (Fname, Sname and email) for each attendee.
Once payment a has been received, the customer is sent 8 (example above) confirmation emails (created in email manager section) of the booking (payment confirmation has been disabled).
Is there a way to collate this data into one email? Ideally displaying all the event dates, times etc?
It is not ideal getting confirmation emails for each event the customer has registered for especially if they need to print out and use as proof of purchase on the day of the event.
The system is set up in this way so that users can be added to the database individually and receive their own tickets.
Currently the only way to stop multiple emails is to not request the data from the additional attendees, collating emails at this time is not possible.
Viewing 1 reply thread
The support post ‘Multiple event confrimation 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.