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 Duplicate registration confirmation email | Event Espresso - Staging Server
After the customer makes a payment using paypal, we are receiving two (duplicate) registration confirmation email with the same date/time stamp and content. Is this a bug? How do we fix this, if it’s not a expected behavior.
FYI
– Testing using paypal sandbox
– Have seen a similar topic (duplicate confirmation email) in the forum where it was mentioned that this was fixed
Just to add to this, the people who register are also getting duplicate emails (2 of everything):
– Automated response email with the transaction ID in the body
– An email simply thanking the user for registration
These duplicate emails will be pretty annoying for the customer.
I tried to register for an event just to see what I got but not sure if you have emails going out only after payment.
There should be no reason why a user would get duplicate emails, unless they registered for more than one person and used the same email address, in which case they will get details for both attendees.
Viewing 2 reply threads
The support post ‘Duplicate registration confirmation 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.