• Hello,
    I couldn’t seem to find the answer to this one…

    I wish to develop client sites on my multisite domain, and then either domain map them ongoing (i.e. keep them on the multisite install) OR move them onto their own hosting plan using a separate single install.

    Are there some definitive instructions on how to manage this? Considering that I have to extract the specific db tables for the client’s site and import to the single install…. amongst other things..

    I wish to maintain smaller clients using the domain-mapped option, but allow larger clients to operate independently if they wish.

    If there is a foolproof way to manage this, then I can safely offer either option to my clients moving forward.

    thanks for any help in advance.

    Paul

Viewing 10 replies - 1 through 10 (of 10 total)
  • the easiest way is the internal Export / Import.

    you still have to set up the options, unless you;re willing to export those tables from the multsite db, then rename the tables and put them in the single install.

    Thread Starter closed account

    (@member11)

    Thanks Andrea.

    I guess I’m looking for the cleanest way. I’m prepared to export db tables and rename if that’s going to achieve this.

    Apart from the ‘blogid_’ specific tables from the multisite db, which other tables to I need to export to the single install db?

    https://bavatuesdays.com/importing-a-single-wp-blog-to-a-wpmu-installation/

    explains a lot. but in reverse.

    basically, set up the user FIRST. if it’s the default admin of the blog, that’s fine.

    otherwise, the blog_id tables shoudl be the only ones you need going to a single install.

    Thread Starter closed account

    (@member11)

    Thanks Andrea. I’m working thru it now.
    Can you please advise what changes are required in relation to the blogs.dir folder when copying across to single install wp3…
    apart from deleting folders relating to other blogs

    You only need to snag the numbered folder under blog.dir that correlates to the blog you;re moving. So, if it was blogid13 just get blogs.dir/13/ and under.

    Go deep enough and you’ll see it has a /files/ folder then dated folders within. Just like wp-content/uploads/files/ does on single installs.

    I had a client move from our hosted install to a single WP install. Export worked dandy for her. it pulls attachments.

    Thread Starter closed account

    (@member11)

    Does the blogs.dir need to be renamed to run on the single install?
    i.e. to wp-content/uploads/files/

    thank you

    Thread Starter closed account

    (@member11)

    Also (sorry for the 100 questions), how is the mu plugins folder treated in the single install – or that shouldn’t be copied across? My multisite install has over 70 mu plugins that I’ve been testing.

    Does the blogs.dir need to be renamed to run on the single install?

    Nope. On a single install you don’t need it. The media for that blog will be in wp-content/uploads. because now it will be the “main” blog in a single site network that is disabled.

    how is the mu plugins folder treated in the single install – or that shouldn’t be copied across? My multisite install has over 70 mu plugins that I’ve been testing.

    The mu-plugins folder has worked in single WP since 2.7. only move over the plugins you absolutely NEED for the single install.

    Looking to do something very similar with my clients. Did this work well for you? I’d love to find a checklist of sorts on doing this as painlessly as possible. Or perhaps someone’s run across a plugin that exports everything, not just the content? just brainstorming…

    just move over the theme and the plugins, then Export the content.

    There is no plugin right now that pulls one blog + everything else out of a network.

    Too many picky things to keep track of.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Moving a blog from Multisite to Single Install’ is closed to new replies.