Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By amariotti on
We recently launched our new website on Drupal just over a month ago. I'm already working on a Phase II upgrade of the site. To make sure that I didn't screw up anything that we already had on the live site I duplicated the mysql database and created another subdomain that points to it. This was the only way that I felt safe with making the upgrades. That part was easy... but once I get the Phase II instance up to where I want it—then what? Our site has users posting jobs to the job board on a daily basis, as well as events to the calendar.
Has anyone else gone through something like this? What's the best way to take my development instance and merge it with new data in the old "phase 1" database? My first thought was to finish phase 2 and then take the node table and insert it into my new phase 2 database. Anyone have any ideas or advice?
Comments
Does the jump from phase 1
Does the jump from phase 1 to phase 2 involve a parallel jump from drupal 5.x to drupal 6.x? Can you tell us more about what the upgrade involves? The node table idea sounds like a good one, but you may have to import the sequences table as well, and a few others to boot. This is rarely an easy process.
Note: Just found this: http://drupal.org/node/232155
----------------------------------------------------------------------
http://classicvinyl.biz
http://music.bwv810.com
http://davidhertzberg.com
http://association.drupal.org/user/1207
I am a writer, researcher and solo drupal freelancer
My upgrades for phase 2 are
My upgrades for phase 2 are both additions (i.e. new dynamic blocks, updated content types, etc.) and bug fixes. Just looking at this I'm thinking that I will have to track the things that I'm doing and duplicate them on the live site. This is kind of frustrating, but I'm not sure if there's a better way to do it. The only other way would be if I took and locked down the site so nothing could be added or removed to it until Phase II is released. Anyone else been faced with this? I can see the database merging as a good solution, but am unaware of how to do it.
Please have a look at the
Please have a look at the link I provided above for database merging. FYI, speaking for myself, I generally do development work on live sites without worrying about risking any interruption is regular functionality; this, in order to sidestep the very problem you are grappling with. Not sure what others do, but I suspect that upgrading a site in the manner you described could be done without affecting other of the sites' operations.
----------------------------------------------------------------------
http://classicvinyl.biz
http://music.bwv810.com
http://davidhertzberg.com
http://association.drupal.org/user/1207
I am a writer, researcher and solo drupal freelancer