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 Registration Logged Before Confirmation | Event Espresso - Staging Server
We’ve since updated our software to the most recent version. Under GENERAL SETTINGS, I have the “Default Payment Status” set to “Incomplete”. Also, under the individual events, I have the “Default Payment Status For Event” field set to “Incomplete”.
This doesn’t seem to address my question/issue. To clarify, our events have multiple payment options some of which are a “$0.00” cost. The registration is a two-step process. It seems as though only when a visitor selects a payment option of $0.00, Event Espresso is immediately counting them as a “confirmed” body in the class even though they haven’t yet clicked the CONFIRM REGISTRATION button on step 2 of the registration process.
Is there any way around this? Ideally, we don’t want their registration to “count” toward the head count until they click CONFIRM.
It turns out that the confirmation buttons are there to allow for confirming their registration information. If they’ve misspelled something they can go back and edit from that screen.
The registration form gets logged when they submit the registration form. Since a 0.00 price option selection doesn’t require to be completed, Event Espresso automatically changes the status to complete when it’s a free ticket.
Viewing 1 reply thread
The support post ‘Registration Logged Before Confirmation’ 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.