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
Remove Espresso Completely (and Start Over) | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Remove Espresso Completely (and Start Over)

Remove Espresso Completely (and Start Over)

Posted: December 17, 2013 at 1:44 pm

Viewing 1 reply thread


Rob Shiflet

December 17, 2013 at 1:44 pm

I’ve used Event Espresso quite a bit on numerous different sites. I have ONE site that no matter what I do, I can’t get it to display properly. I just installed it again on a separate site, just to see if I got different results (possibly a conflict with the new WP 3.8, etc.), and it worked perfectly.

Can you tell me how to remove all references to Event Espresso (and start over)? This is a new EE install, so starting over is not an issue for me.

I’ve tried removing the plug-ins, deleting all EE plug-in files, and removing tables from the MySQL that reference “events”. But this made no difference, and some of my information remained when I re-installed.

Thanks in advance for your help.


Josh

December 17, 2013 at 2:37 pm

Hi Rob,

In addition to what you’ve already removed, the wp-options table has the Event Espresso options stored there. You can do a search on the option_name column there to find all of them.
Viewing 1 reply thread

The support post ‘Remove Espresso Completely (and Start Over)’ 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 Josh 11 years, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server