Mmmm… how to explain best… the change in terminology makes it confusing so I’ll describe what you know first and then “translate” it to the new situation, while casually explaining the difference between the two plugins ??
== WPMU ==
(what you got running now)
Normal install
– one site, many blogs
– one main blog and many sub-blogs either with subdomains or with subdirectories
Example:
domain.tld has sub-blog blogname.domain.tld
With Domain Mapping
– adds the ability to associate a different domain name (top level or other) to ANY blog on the site
Example:
domain.tld has sub-blog blogname.domain.tld which can also be accessed via otherdomain.tld
With Multi-Site Manager
– adds the ability to have multiple main blogs each with their own site domain and with their own sub-blogs
Example:
one site under domain.tld has sub-blog blogname.domain.tld while on the same install there is another site under otherdomain.tld with sub-blog otherblogname.otherdomain.tld
== WPMS ==
(what you should get after upgrade = the above translated to WP3.0 terminology)
Normal install
– one network, many sites
– one main site and many sub-sites either with subdomains or with subdirectories
Example:
domain.tld has sub-site sitename.domain.tld
With Domain Mapping
– adds the ability to associate a different domain name (top level or other) to ANY site on the network
Example:
domain.tld has sub-site sitename.domain.tld which can also be accessed via otherdomain.tld
With Multi-Site Manager
– adds the ability to have multiple main sites each with their own network domain and with their own sub-sites
Example:
one network under domain.tld has sub-site sitename.domain.tld while on the same install there is another network under otherdomain.tld with sub-site othersitename.otherdomain.tld
Hope you see the differences and advantages of both these plugins… Now combine these two and what do we get? ??