Converting / migrating multi-site to single (normal) WP site?
8 views
Skip to first unread message
Art Thompson, Jr.
May 14, 2013, 3:03:31 PM5/14/13
to wordpress-austin
Hi WP'ers,
I've inherited a mess of a site that was initially set up as a multi-site installation with subdomains, for example:
This was done without the client's knowledge, but the client says what they wanted was a site set up like:
I think I know the answer to this already, but I wanted to reach out to some multi-site folks to see if you had any advice on how to approach this. I've got the entire www root dir as well as a .sql file of the entire (multi-site) database. Each subdomain's theme was identical save for some color/bg image tweaking, which I believe I can address thematically. But, did I just step in something, or is there a relatively easy way of achieving the new site structure?
Thanks,
Art Thompson, Jr
Logical Things, Inc
design + technology + strategy
-
Founded 2000. We design, build and host microsites, landing pages, eblasts and whatever comes next.
-
Need to send us large files?
-
Bill Christensen
May 14, 2013, 11:35:05 PM5/14/13
to wordpres...@googlegroups.com
Hi Art,
I've only used the first type of multi-site install, but I suspect that the two are handled in a similar way in the back end.
I would toss up a quick test install of the second variation and see how the db is structured. If my suspicions are correct they'll be handled in a similar way - you'll have a set of wp_2 tables, a set of wp_3 tables, etc for the various blogs, and a handful of others for the 'main' site and for control stuff - wp_sitemeta has subdomain_install = 1 on mine, for instance, and probably has either subdomain_install = 0 for the other or (whatever the other option is called)_install = 1. I suspect that the core code deals with the difference, but I'd be interested in hearing what you find.
Don't forget the redirects in .htaccess.
Or are they really looking for everything to get migrated to a single-site installation? That's not entirely impossible to do, you'd mostly just have to do a bunch of find/replace on your sql files before importing them to dump them into the single site setup. Change wp_2 to wp and let most of the rows get assigned fresh index numbers and stuff like that. Users may get a bit sticky...
Good luck with it. Better you than me ;-)
I've only used the first type of multi-site install, but I suspect that the two are handled in a similar way in the back end.
I would toss up a quick test install of the second variation and see how the db is structured. If my suspicions are correct they'll be handled in a similar way - you'll have a set of wp_2 tables, a set of wp_3 tables, etc for the various blogs, and a handful of others for the 'main' site and for control stuff - wp_sitemeta has subdomain_install = 1 on mine, for instance, and probably has either subdomain_install = 0 for the other or (whatever the other option is called)_install = 1. I suspect that the core code deals with the difference, but I'd be interested in hearing what you find.
Don't forget the redirects in .htaccess.
Or are they really looking for everything to get migrated to a single-site installation? That's not entirely impossible to do, you'd mostly just have to do a bunch of find/replace on your sql files before importing them to dump them into the single site setup. Change wp_2 to wp and let most of the rows get assigned fresh index numbers and stuff like that. Users may get a bit sticky...
Good luck with it. Better you than me ;-)
On 5/14/13 2:03 PM, Art Thompson, Jr. wrote:
Phillip Barnhart
May 15, 2013, 11:32:27 AM5/15/13
to wordpres...@googlegroups.com
A good step-by-step is located here: http://blog.ashfame.com/2010/07/remove-wordpress-multisite-data/
I've had to do this a few times - including your exact example. Big gotchas? Post urls for one.
I would actually export out of multisite ~ import the site content and then fix the URLs directly in the DB. When exporting and importing, make each site content connect with a different (temporary probably) user account to make the SQL easier.
I would actually export out of multisite ~ import the site content and then fix the URLs directly in the DB. When exporting and importing, make each site content connect with a different (temporary probably) user account to make the SQL easier.
Art Thompson, Jr.
May 15, 2013, 1:14:26 PM5/15/13
to wordpress-austin
Thanks Phillip & Bill. What a difference a day makes. My client now wants to swap out the old content with new. Starting from scratch with a clean install — problem solved! ;-)
I'll definitely bookmark that step-by-step in case I "step" in one of these again.
Cheers,
Art
--
--
You received this message because you are subscribed to the Google Groups "WordPress Austin" group.
To post to this group, send email to wordpres...@googlegroups.com
To unsubscribe from this group, send email to wordpress-aust...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/wordpress-austin?hl=en
Our meeting information is available at http://www.meetup.com/austinwordpress/
---
You received this message because you are subscribed to the Google Groups "WordPress Austin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wordpress-aust...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Reply all
Reply to author
Forward
0 new messages