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 EE not sending attendee correct quantity of tickets purchased in receipt | Event Espresso - Staging Server
MY SETUP: Event Espresso – 3.1.28.3.P Add-On Ticketing – 2.0.8 When an attendee buys more than one ticket, the receipt/ticket they are sent only shows that they bought one ticket (only the cost of one ticket shows up in dollar amount). I am not sure whether this is an EE or a Ticketing Plug-In bug, but I am getting a lot of emails from confused attendees and have to do a lot of damage control over this.. please advise…
This sort of helps but not really. I can foresee people still being confused because even though an attendee purchased 2+ tickets, it still only shows the cost of one ticket at the top. Here is an example:
$23 is the cost of one ticket but the attendee bought 2. I hope you can see that your fix doesn’t really help me. Not sure why the [ticket_qty] is not being generated. Also, it’s not in that prominent a place, easy to miss.
You can place the ticket qty shortcode anywhere in the ticket template. Please note that you need to place it in the template, not the editor. The default ticket template is located in the ticketing add-on’s templates directory and its file name is index.php. The above linked documentation will show you how to copy the templates to another location so they do not get overwritten on an update.
The support post ‘EE not sending attendee correct quantity of tickets purchased in receipt’ 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.