|
Bogdan Sindile
|
November 4, 2014 at 7:12 pm
We have a staging and production environments, both using EE4 (4.4.3). In staging we’ve done some changes and we would like to test those with all registrants that registered to various events on the production site (in the last couple of weeks while we were working on staging). Is there a way to copy one or more tables from the production database to staging database so that only Registrants are updated in staging without affecting any other developments we’ve done? Events on staging were not affected by any new developments, they are the same as those in production.
Also, same applies the other way around: how can we move the changes done from staging to production without affecting / losing existing Registrants for live events in production.
|
|
Josh
|
November 4, 2014 at 8:21 pm
Hi Bogdan,
On the latter part of your question: Are you asking about moving code changes from staging to production, or changes to the database? Merging changes from one database to another is tricky and I wouldn’t recommend it.
The tool I can recommend for moving data back and forth between staging and live is the WP Migrate DB Pro. It allows for pulling in data from production to staging.
|
|
Bogdan Sindile
|
November 5, 2014 at 5:25 am
Hi Josh,
Production has now 158 registrants in one event and 85 registrants in another event. Staging has an earlier number of registrants for those 2 events (68 and 43) plus additional changes (we implemented your advice from a different post to give access to employees in our company only to events, no WP platform, we added several new events that we would like to push live, we have more info on our News section – that is WP – and in several other parts of our website like partners, F.A.Q, … etc – WP again). What is my best option here to move all changes from staging to production and keeping production registrants untouched? I looked at your recommendation (WP Migrate DB Pro) and it seems there are moments when the same question of what tables should I backup or migrate is still there. I don’t mind getting the WP migrate DB Pro but I prefer doing that after I understand how exactly it will help me achieve my goal.
|
|
Josh
|
November 5, 2014 at 6:44 am
Hi Bogdan,
The only reliable readymade solution to sync data bases as you’ve described, that I’m aware of, is manually add your changes (like new posts) to production. part of the reason for this is EE4 writes a lot of its event data to the same WP table that posts are written to.
Then, once everything from staging is on production, you use wpmigratedb pro to sync everything on production back to staging.
Another potential solution would be to build a custom system on top of Ramp.
http://crowdfavorite.com/ramp/
|
|
Bogdan Sindile
|
November 5, 2014 at 9:54 am
Hi Josh,
Many thanks. Purchased WP Migrate DB but after a few tests we are not any further than before. I also contacted crowdfavorite for RAMP and waiting a response from them.
Before we move forward and perhaps look for a completely different solution or approach for our problem, I just wanted to make sure there is no way (using any tools or means) to export only Registrants from production to staging without affecting any other settings in staging. To make sure we are on the same page, please consider the following scenario: staging and production are 100% similar at one point in time (let’s say this morning at 9 am) with exact same number of registrants for one event (e.g. 68); in 3 hours we have another 32 Registrants on Production for a total of 100 registrants; at this point we would like to export all Registrans from production (and only Registrants) and import them to staging; the self imposed constrains here are no copying of entire databases. Is this possible?
|
|
Josh
|
November 5, 2014 at 10:26 am
Hi Bogdan,
You are going to encounter problems with syncing any ecommerce type data using this approach. This is because of the relationships that get set up between things like posts, events, registrations, transactions, contacts, and answers to registration form questions.
There are ways to avoid making database conflicts discussed in this article:
https://deliciousbrains.com/avoiding-wordpress-database-merging/
|
