How am I triggering the spam filter?

Sorry you ran afoul of the spam filter. I haven't had any problems with it here so I have no clue what might have set it off.

I don't have any special scripts or tools for updating/migrating multi-site installations because we don't do mass updates. With 30+ sites and a single core codebase the downtime associated with updating everything simultaneously is simply unacceptable. Upgrades (and especially migrations) are performed on a site-by-site basis.It avoids the potential creeping nightmare of having three or four sites simultaneously b0rked by a module upgrade.

As far as migrations go, while I've migrated some of our simplest sites (think single user blog, no custom code, fewer than 10 contrib modules installed) at the same time a lot of our sites have quite a bit of custom code that has to be ported over & tested so we generally treat migrations as an opportunity to "refactor", so these are definitely done one at a time as well.

Generally what I end up doing is creating a separate migration installation that uses a copy of a site's database. Once I've gotten the kinks worked out so update.php runs cleanly and all of the site's custom code is ported to the next version of Drupal I'll drop the live site into maintenance mode, take a final snapshop of the database, port it over to the dev site, run update.php, then change the site's virtual host settings to point to the dev site. Once that goes live I delete the original and go on with my day. Kinda wonky but it works well.

I don't know if this helps or not. Let me know if you have any specific questions. :)

-Allen

That helps a lot. I can't change the virtual host settings for my sites. I have a test site and check things out there, but then have to do all the real sites at once. There aren't many, and they are very small and not very active.

I feel the same way about mass updates: it's just not worth the trouble.

Every time you do an update, even a simple one, the "right way" is some variation of: copy to development, run the update, make sure it worked, take live down for maintenance, run update on live. You can't make sure the update didn't break your sites in bulk, not really.

Also, I strongly recommend against using Drupal multisite unless you actually need to share data. Having all those sites be reliant on each other will be painful at some point down the line. A better approach is to use SVN externals to have a central code repository (Drupal core in on repo, shared modules in another, each site having all/default in one of its own). Then, you can update each individual site easily, but you aren't forced to do them all at once.

We don't mess with virtual hosts for consistency reasons but that may be acceptable for you if your maintenance periods absolutely have to be as small as possible.

Spam filter is often set by the sites admin to accept quality debate in comments and so that only quality comments gets publish. But I have one question as one of my friend asked you above also that, how we can use multi-site to facilitate data sharing? Engineering Jobs