WordPress 3.0: Multisite Domain Mapping Tutorial. As an extension of the excellent walk through of the multisite functionality of WordPress 3.0 by our very own Klint Finley, Otto has put together a domain mapping tutorial that is receiving rave reviews. Follow the steps to map multiple domain blogs from within the same WordPress 3.0 install.
I was wondering why my website’s traffic spiked all of a sudden… 🙂
If anybody is interested, I got over 1000 unique views from this post alone. I might make charts. 🙂
Its actually never that clear because a large percentage of our readership is via newsreaders and those never count as referrers. 🙂
Checked the link and I can say that it is a really nice step-by-step tutorial. Bookmarked it and will refer back to it when the need arises.
I’d like a tutorial on how to move a single WP site to a site in a network, so that no data is changed.
By changed data, I mean don’t filter content text during export and import, don’t change IDs, don’t reset any plugin option.
Even better: I’d like a tutorial explaining what changes when a site is upgraded to a network, what changes are done in the network’s main site’s tables. It would be great if we chould just export all wp_ tables from a WP database, rename them all to wp_2_, and import to a network database that already has a site with ID 2, and have our site fully working as before!
It’s never that simple. When I moved ottopress from a standalone site to being part of my “network”, lots of manual changes were required for the content. Multi-site just works differently. Especially linked files/images.
The Search Regex plugin helped *a lot*.
After trying wordpress MU and the maping plugin I decided to you a single wordpress for every domain. When you have a hosting with simple scripts it turns to be a very easy process. But sure, MU is a great thing for somebody who knows how to use it.