|
kdaily
|
January 16, 2018 at 1:51 pm
I am using the staging environment within WPE to push updates to the live environment. I need to know what tables I need to exclude so as not to delete registrations that occurred after I copied from live to staging.
Also, is there a way to temporarily stop registrations (other than the obvious removing access to the events pages).
|
|
Josh
|
January 16, 2018 at 2:25 pm
Hi there,
I’m afraid there isn’t an easy way to exclude tables to make this possible. While much of the data resides within the tables prefixed with _esp_, Event Espresso also uses the _posts, _postmeta, and _options tables for events and registration data. You might have a look at a solution like Mergebot to handle pushing staging data to production:
https://mergebot.com/
You can temporarily stop registrations by putting Event Espresso into maintenance mode. You set maintenance mode on the Event Espresso > Maintenance page.
|
|
kdaily
|
January 16, 2018 at 2:29 pm
How does mergebot know what tables to exclude?
|
|
Josh
|
January 16, 2018 at 2:51 pm
Mergebot doesn’t exclude tables. Instead, when you start working on the site, you can set up Mergebot and have it save the changes you make to your dev site and deploy those changes without affecting events, registrations, tickets, and so on.
|
