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 Event Registrants is First Payment Fails | Event Espresso - Staging Server
I have found that when attendees have finished registering their details, when paying the fee, if card payment fails at the first attempt and then goes through after their second attempt I get the name of the individual twice on the list. The first one is the completed payment and the other is incomplete. Is there a way to get only the completed registrations on the list rather than having to delete the incomplete one?
And advice would be appreciated.
Regards,
Brook
Version: Version 3.1.29.1.
Add-ons: Multi Event & Calendar
Have you gotten any feedback from your users regarding this? Are they having to go through the registration process again? Are there any errors appearing when they get returned to your site from Eway?
There has been no feedback from users.
The issue is just that if a failed the successful payment occurs, their name appears twice on the list. One for complete and another for incomplete.
The thing is, it is highly dependant on how it is failing and the actions of the user afterwards. Right now when I test he payment gateway and the account fails it goes back to the thankyou page from where I can retry the payment. So no duplicate attendee is created.
If however there is an error or some other issue that is forcing the client to start again, it could explain the duplication.
We need more information on this, as even with a test gateway I dont think we can get to the root of the problem easily.
What is the timestamp difference between the complete and incomplete attendee? Which comes first or are they at the same time? (you can see this in the Attendee Overview for the events).
Viewing 8 reply threads
The support post ‘Duplicate Event Registrants is First Payment Fails’ 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.