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 Custom gateway & ticket module : not sending additional registrants email | Event Espresso - Staging Server
I had to develop a custom payment gateway to interact with our institutions Cashnet by HigherOne payment system. I followed examples and documentation on the website, and it works fine as far as receiving payments, however because of the way the response from Cashnet comes through, it only sends the primary user’s registration ID back to the processor. In doing so, only the primary user receives and email with a link to their ticket purchased through the installed ticket module. The other users are marked as paid, but don’t receive a confirmation email. Any ideas how to send either A) all ticket links in the confirmation email/display on confirmation page or B) send an email to the additional attendees.
The payment confirmation email only goes out to the primary attendee. However, the registration confirmation email should go out to all attendees. I would suggest setting “Send registration confirmation emails before payment is received?” to No in EE->general settings->email settings and putting the ticket link in the registration confirmation email.
Viewing 1 reply thread
The support post ‘Custom gateway & ticket module : not sending additional registrants 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.