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
Removed Events, Attendees not Removed | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Removed Events, Attendees not Removed

Removed Events, Attendees not Removed

Posted: April 16, 2014 at 10:15 am

Viewing 1 reply thread


andrea k

April 16, 2014 at 10:15 am

I ran a bunch of test attendees through some test events. I removed those events and added new events that have gone live. When I go to export attendees that are now signing up, those original test attendees are in the database still. I went into the wp_events_attendee table to remove them manually…is this a glitch? I can’t imagine why it wouldn’t purge attendees automatically from an event that has been removed.

Thanks


Dean

  • Support Staff

    •

April 17, 2014 at 2:00 am

Hi Andrea,

No it is not a glitch, it is a precaution. If you accidentally remove the wrong event, the attendees will not be lost. In fact the event is still accessible as well.

To completely purge attendees, hover over the event name, click the attendee link. Then select all and delete. These will be removed from the database. Then remove the event.
Viewing 1 reply thread

The support post ‘Removed Events, Attendees not Removed’ 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.

The original Forum description...

Status: closed

Updated by Dean 10 years, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server