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 Confirmation e-mail from backend | Event Espresso - Staging Server
I am using EE3 and WP 3.8.1 for a client. It is a new installation.
We provide payment by iDeal (Mollie) only.
When a user registers, but doesn’t pay with Mollie his record is still saved, but he doesn’t receive a confirmation e-mail (because we configured it like that: send confirmation after payment), so that is the expected behaviour.
But now we have the situation that our client wants to change the payment-status to paid in WP when they had contact with the registrant. But the registrant won’t receive an e-mail. Even if we tick “Yes” to the e-mail question. Why is that? Is there any way we can force this confirmation e-mail to be sent?
The emails are sent by default when either payment is complete and successful or if the registrant is otherwise marked as complete (such as with free events).
The email notification for registration details will not automatically go out. You can resend this by viewing the attendees for a specific event and clicking on the email icon in the Actions column:
The support post ‘Confirmation e-mail from backend’ 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.