Releases for Multisite Manager

First go at a 6.x release. Standard stuff works great.
TODO:
support multi-task profiles
better documentation
maybe try abstracting out the higher DB functions (create db, etc.) a la DB apis in 6.x

please try it out, and give feedback

small bugfix for mysqli_error()

Added some documentation, and cleaned an anticipated bug up for the admin script.
We'll try to improve documentation for initial setup further, but see the INSTALL.txt for more details until then.

This release is recommended for only 5.7+ or you will need this patch

adding help

First go at a 6.x migration. Complex profiles with multiple 'tasks' are not supported, and this does NOT have an upgrade path for an 5.x install (yet). Please try it out (on non-production after backing up database, etc).

fix for http://drupal.org/node/205603

add feature: http://drupal.org/node/196601
fixed some cache variables which carried over to main site from node install

Added silfreed's cron feature.

After doing some more advanced things with profiles, I came across a bug in db_set_active() in core. If you have any profile which calls watchdog() (e.g. taxonomy, and menu), then you should apply this patch for Multisite_manager to work.

The other issue is that even with the patch the db_prefix does not change as db_set_active() context is switched causing some (mostly harmless) error messages when it can't find the new site's prefix in the old database. To fix this, we first install in a new database with the current prefix and then rename the tables to the old.

Another small bug fixed is that get_variable() requests within profiles could be getting wrong information from the current site, instead of the variables for the new site. This is now fixed, too.

fixed some bugs in hook_delete
also made it possible to actually update the values as an admin, after an original save--this should only be useful when moving around dbs manually, and then updating the record

Allows creation of new drupal sites from a central drupal site without the creator having access to database info. The new site is installed either in the same database with a different prefix or if the drupal db_user has access to create a database and grant privileges, then possibly there.

If you are looking for inter-related sites, this module will not achieve this alone (see ogsite). This simply makes it possible for users to skip the typical drupal installation process (entering the db user/password), making it possible for non-admins to do this step.

This project was sponsored by the Columbia Center for New Media Teaching and Learning: http://ccnmtl.columbia.edu

First release, which should be stable, but I'd like to hear back from others who've installed it, first. Particularly, this is untested with Postgres (though, theoretically supported)