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
Single Ticket Email | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Single Ticket Email

Single Ticket Email

Posted: January 23, 2014 at 4:03 pm

Viewing 1 reply thread


Tom Allen

January 23, 2014 at 4:03 pm

We are running EE with the Ticketing Plugin and the Seating Chart Plugin.

An email comes for each ticket. Is there a way to modify the scripting so that one email can come with an email to all tickets purchased. So the customer only gets one email?


Dean

  • Support Staff

    •

January 28, 2014 at 4:06 am

Hi Tom,

Not easily. The way it’s set up is that it fires off an email each time the attendee gets added to the database. I suppose the best you could do would be to stop those email from going out and then grab the data from the database based on that session ID and generate a new email containing all the data.

As I say, not easy and you would likely need a developers help. Here’s a list of recommended developers http://staging.eventespresso.com/developers/event-espresso-pros/

Looking to the future we have made EE4’s messaging system much more robust and flexible, hopefully allowing things like this to be done easily.
Viewing 1 reply thread

The support post ‘Single Ticket Email’ 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.

The original Forum description...

Status: closed

Updated by Dean 11 years ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server