|
Tam
|
August 17, 2016 at 11:43 pm
So, I found this thread.
https://eventespresso.com/topic/need-to-migrate-just-event-espresso-content-to-new-site/
Wish I would have saw that before but I am wondering if anything has progressed in this area? I do see “purchaser” details exist in wp_posts tables and one unique thing to those columns is they have a “no biography provided” label in post content. I also see events themselves are in wp_posts.
And of course no issues with moving all _esp_ tables.
Can i ask if there is any unique identifiers in the wp_options tables?
We are launching a new site and for various reasons we needed to start the content clean but we have sold event tickets well into the fall. Recreating all events, settings and then the issue of not being able to scan tickets without a second site and a way to denote old and new is not ideal. Please let me know if this is documented or if there is a way.
Thank you
|
|
Josh
|
August 18, 2016 at 8:57 am
Hi there,
There has been some progress in that Mergebot is available now. This plugin allows for making changes to one site then applying those changes to another site without losing changes to the other site.
Can i ask if there is any unique identifiers in the wp_options tables?
The option names are prefixed with ee_
|
|
Tam
|
August 22, 2016 at 11:59 am
Unfortunately Mergebot is no longer available until it is out of beta. You can get the plugin but you can register or get the API key until they release it.
So…
wp_options tables have an ee_ prefix.
wp_post tables for people have “no biography provided”
wp_posts tables for events I am not sure of yet
anything else I need to manually move?
|
|
Josh
|
August 23, 2016 at 8:01 am
Event Espresso adds posts to the wp_posts table that have the following post_type‘s:
espresso_events
espresso_attendees
espresso_venues
If you use the People add-on, it adds espresso_people post_type posts to the posts table as well.
If you use the WP Users Integration add-on, then there will be entries in the _usermeta table that are related to the _users table, and will have meta_keys that consist of {wpdb-prefix}_EE_Attendee_ID.
|
