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 Attendees does not remove from the DB and Exported Excel Sheet | Event Espresso - Staging Server
I’ve been doing a lot of testing and will continue to do so. I know I could manually remove the records from the DB if needed but was wondering if “deleting attendee” was meant to remove them from the DB or not and not just change their visibility in the admin?
It should delete them from the DB, but here’s what I recommend for testing on a site that will eventually go live:
Create a ‘test’ event for testing. When you’re done testing, delete the event. Then use the filter feature to view all the deleted events. Then there will be a button to permanently delete these events. That will permanently delete the event from the db.
That was it Josh!,
didn’t even realize there was a “deleted” status on the events. I was “deleting attendees” but my reports kept showing them (because they were still tethered to my deleted events which weren’t “permanently deleted”).
once, I permanently deleted the events, all that test data and older entries cleared up along with it :)
thanks for the tip!
Viewing 2 reply threads
The support post ‘Deleting Attendees does not remove from the DB and Exported Excel Sheet’ 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.