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 Incomplete registrations: can these disappear? | Event Espresso - Staging Server
Thank you for your help in assisting us so incomplete registrations are not held spots. I have a request from the person handling these on the back end of Ev. Esp.
We have our default payment status set to “Incomplete”.
We have this for each event in the event editor: Under “Default Payment Status for Event” we have checked “No Change.”
1. Are incomplete people still receiving an email about their incomplete registration? We don’t want them to: how can we change this?
2. Is there a way to have Event Espresso ignore incomplete transactions and not report them on the back end? Or does this mess up ALL transactions because they are at some point incomplete?
Registration emails are sent before payment is received by default. In the General Settings you can set it so thee emails are not sent until payment is received by changing “Send registration confirmation emails before payment is received?” to No.
That way the registration email will only go out once payment is complete and the status is “Completed”.
2) You can filter the attendees by status, to show only completed or whichever status you prefer. There is no automated way to do this. http://d.pr/i/pjLY
Viewing 1 reply thread
The support post ‘Incomplete registrations: can these disappear?’ 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.