Home ›
Migrating a Shared-user Multisite installMigrating a Shared-user Multisite install
Submitted by Benjamin Melançon on June 5, 2007 - 11:37am
Things to watch out for when moving a shared-user multisite install.
The biggest thing is that when moving a site to a different userbase, all the attribution will be screwed up, so you just can't do it. However, assuming that your moving a test site onto a live user install, but you want to migrate all that content you put up and configuration, and will reassign authorship in the database or manually, be sure to:
- The subsite_ prefixed parts of the sequences table must be moved over. Export the table and copy that half the inserts for instance.
- Be very careful when running a database update. At least on 4.7, the multisite setup seems to confuse Drupal, and on the subsite anyway, make it think that the system has to be updated from update 110 (way back in the dark ages) when in fact you should be able to vouch that it doesn't have to be updated at all. Manually select 'no updates' and that should take care of that.
To match content to the proper users, you can run queries like this:
UPDATE subsiteprefix_node SET uid = '4834' WHERE uid = '4307'
But if you have userreference fields also, and who knows what else... that'll be wrong and in need of fixing too, of course.
Things to watch out for when moving a shared-user multisite install.
The biggest thing is that when moving a site to a different userbase, all the attribution will be screwed up, so you just can't do it. However, assuming that your moving a test site onto a live user install, but you want to migrate all that content you put up and configuration, and will reassign authorship in the database or manually, be sure to:
- The subsite_ prefixed parts of the sequences table must be moved over. Export the table and copy that half the inserts for instance.
- Be very careful when running a database update. At least on 4.7, the multisite setup seems to confuse Drupal, and on the subsite anyway, make it think that the system has to be updated from update 110 (way back in the dark ages) when in fact you should be able to vouch that it doesn't have to be updated at all. Manually select 'no updates' and that should take care of that.
To match content to the proper users, you can run queries like this:
UPDATE subsiteprefix_node SET uid = '4834' WHERE uid = '4307'
But if you have userreference fields also, and who knows what else... that'll be wrong and in need of fixing too, of course.
Comments
Post new comment