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 Attendee deleted in 1 even after buying 2 events with MER and payment paypal | Event Espresso - Staging Server
a user has selected 2 events with MER, and as soon as I saw were selected in the event attendee overview its 2 events with pending payment.
The user wrote to me to have problems with paypal probably because of credit card that had a limit of money. Shortly after I received the confirmation from paypal that one event had been paid. At the same time in the backend-event attendee overview the second event was lost and the status of the payment of the first event has become “complete”.
After a few minutes I received a second email from paypal that confirmed the purchase of the second event, and the first event on the site was lost and the second event has reappeared with the status “completed”.
I do not know what happened, but now I have a payed event that the user no longer has in this member area..
how can I add to him the first event? you can enter it manually?
Have you checked the filters to make sure the attendee is there? Or checked the database?
If the attendee has definitely gone, then I would advise to firstly update event Espresso and the add ons.
After that yes you can add an attendee manually, by going to Event Overview, hovering your mouse over the event name and then clicking Attendees. On that page near the top is an Add New Attendee button.
Viewing 1 reply thread
The support post ‘Attendee deleted in 1 even after buying 2 events with MER and payment paypal’ 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.