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 Invoice is not being emailed to the person that registers for an event | Event Espresso - Staging Server
the main issue is that an invoice is not automatically sent to the person booking the event once they register and pay for an event.
The following is a breakdown of the emails sent/received
Admin receives: 2 email notices: 1) Payment receipt from paypal and 2) Registration confirmation – which has a link to download the invoice as a pdf
A guest or registrant receives 1) FW: Payment Received for 2) FW: Booking Confirmation
And the person who makes the booking receives the following: 1) Payment Received notice with transaction id and the amount 2) Booking Confirmation 3) Your payment to .. receipt from paypal …. but no actual invoice or am email with a download link the same as the invoice sent to centre support admin email.
Is there some other place this needs to be switched on ? it seems logical that the person paying for the event would actually be receiving the invoice.
Invoices are not sent out by default by the person who paid because if they have already paid isn’t always desired to send them an invoice. This can reduce confusion eg “I already paid, why was I just send and invoice?”
If you prefer to send an link to an invoice to the person that registers, you can add the [invoice_link] tag to the payment confirmation email template in Event Espresso>General Settings.
Viewing 1 reply thread
The support post ‘Invoice is not being emailed to the person that registers for an event’ 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.