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 Deleting old attendees | Event Espresso - Staging Server
I have deleted all the attendees in the admin section, it say 0/300 but when i export the attendees the old once for last years event appears with the new once of this year.
Can you explain a little more on the steps you are taking please?
I have just deleted some attendees, exported the event data and checked for those attendees but could not find them.
I also checked the DB for the deleted attendees but once deleted they are no longer within the DB so I’m not sure how you are still getting deleted attendees when exporting the events.
So i click on the 0/300 and see the attendees reports. at the moment i just have two attendees under each of the events.
So if i say Export all Attendee data. i would expect to just see the two that im seeing in the admin section. but if i export the data i get 97 Groups and those are the old attendees from last year thats its pulling in.
ahh, I see what’s going on. The extra attendees are from closed or inactive events. If you go to the event list, go up to the status filter and choose “All” and hit filter. Then click on the “all attendees” link and you should see them all in the admin.
The support post ‘Deleting old attendees’ 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.