I saw a post at http://drupal.org/node/62394 which was similar, but a little different from my case so I'll try a new post.
I have several Drupal sites like this :
http://site1.com
http://site2.com
..
http://siteN.com
They all separate MySQL databases (no "prefixes"), but they all share a common Drupal code base.
I have a couple contrib modules (Gsite and AdSense), and Democratica themes.
I don't think I have "primary and secondary" sites which are referred to in http://drupal.org/node/62394. I'd say all my sites are equal peers.
All the sites have their own settings.php file like this :
drupal-4.6/sites/site1.com/settings.php
drupal-4.6/sites/site2.com/settings.php
..
drupal-4.6/sites/siteN.com/settings.php
Each settings.php looks like this :
$db_url = 'mysql://drupal_site1:PASSWORD@localhost/drupal_site1_databasename';
$db_prefix = '';
$base_url = 'http://site1.com';
I read the upgrade instructions and video, but I didn't see much on mutliple site upgrades. Like the users in http://drupal.org/node/62394 I saw a blank screen after upgrade in most cases. A couple upgrades were successful, however.
It seems like you need to run update.php while logged in as user #1. This seemed impossible for multiple sites since once
you switch the code base to Drupal 4.7 you won't be able to log into other sites.
I did try running update.php with "$access" set to FALSE (forget exact variable name). This at least let me upgrade a
couple sites with apparent success.
I'll try it again with the tip from http://drupal.org/node/62394. I'm thinking it might just be easier for me to start with
a fresh 4.7 install and then do (possibly editted) SQL imports of my content as these sites have pretty straight-forward
content.
Would be nice if there were some tools to help with multiple site upgrades (ex. en masse turning off of non-core modules
and themes). If I cook up some tools like this which may be useful I'll post.
David
Comments
access
The variable you are referring within "update.php" is:
// Enforce access checking?
$access_check = TRUE;
Changing it to FALSE allows you to run the script without logging in.
You would have to toggle this for each site before running the update... then toggle it back for security.
It would be be great if we had a "book" section within the documentation that highly detailed MULTISITE management.
Sections should include,
* Initial setup
* overriding core modules and adding contrib modules under each site.
* upgrading
* Overcoming conflicts and problems with contrib modules that are hard coded.
* Differences between UNIX and WINDOWS installs
* Tricks to upgrade multisites all at once... I would love a central update that updated all site databases at once.
MULTISITE is an awesome feature within DRUPAL.
David McIntosh
neofactor.com