Move sub-site of multisite to its own install- same server

  • Resolved robnalexpress

    (@robnalexpress)


    13 years, 2 months ago

    Current Setup: 2 site multisite with domain mapping on a VPS with 1GB RAM, 75GB disk.

    Objective: Move the sub-site to its own WordPress installation on the server.

    My VPS is managed, so I could have them do it for me, but I’d like to learn how to do it myself. I realize that I can use the WordPress export/import plugin (I’ve done this before) but really don’t want to have to rebuild everything from scratch, so I’m looking for a way to move everything intact. The headway tutorial by A. J. Morris shows how to do it manually and using backup buddy, but indicates that backup buddy is sometimes unreliable.

    I’ve found a lot of guides for this, including the one at Headway, but none of them specifically address moving a sub-site of a multisite and leaving the main site intact. Any how-to links or suggestions will be greatly appreciated.

    Specific questions:

    Once I figure out how to do this, I also need suggestions as to where to put the new install on my server. My current install is at /home/sitename. Would I put the new install in a new directory at /home/newsitename?

    Should I give the new install its own database or use a shared database for both sites?

Viewing 15 replies - 16 through 30 (of 47 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Yeaaah I’m sure the reality won’t be as easy ?? It never is.

    Thread Starter robnalexpress

    (@robnalexpress)

    OK, I’ve taken the first step and have a new account set up on my VPS at liquidweb:

    | Domain: dev.domain.com
    | Ip: 67.227.244.179 (n)
    | HasCgi: y
    | UserName: xxxxxx
    | PassWord: ***HIDDEN***
    | CpanelMod: x3
    | HomeRoot: /home
    | Quota: 0 Meg
    | NameServer1: ns1.primarydomain-otheraccount.com
    | NameServer2: ns2.primarydomain-otheraccount.com
    | NameServer3:
    | NameServer4:
    | Contact Email: xxxxxxxxxxx
    | Package: default
    | Feature List: default
    | Language: en
    +===================================+
    Account was setup by: root (root)

    Still not sure which would be safer:

    1. Having them copy the entire multisite to new account and then convert it to single site.

    2. Use WP export/import.

    In either case, wondering what I’ll need to tweak when I’m ready to point to the “real” domain.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Make sure https://67.xxx.xxx.52/~account/ works – I had to turn off mod_userdir Tweak.

    Apache’s mod_userdir allows users to view their sites by entering a tilde(~) and their username as the uri on a specific host. For example https://test.cpanel.net/~fred/ will bring up the user fred’s domain. The disadvantage of this feature is that any bandwidth usage used by this site will be put on the domain it is accessed under (in this case test.cpanel.net). mod_userdir protection prevents this from happening. You may however want to disable it on specific virtual hosts (generally shared ssl hosts.)

    Thread Starter robnalexpress

    (@robnalexpress)

    Make sure https://67.xxx.xxx.52/~account/ works

    Sorry- I don’t understand…https://www.dev.domain.com/ works. Have not installed WP yet- still trying to figure out how to proceed.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Oh! You did that ??

    I suppose you can log in to the dev.domain.com account via SSH and install WP there, and go forward.

    Safer is … eh, it’s hard to say.

    Thread Starter robnalexpress

    (@robnalexpress)

    I’m inclined to use export/import, but wondering what happens in WordPress when I’m ready to change dev.domain.com to domain.com. IOW, the sub-site domain.com will be imported into dev.domain.com, which will need to be changed to domain.com when it’s ready.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    but wondering what happens in WordPress when I’m ready to change dev.domain.com to domain.com.

    Treat it as moving the site.

    Though that’s why I said to use your IP/~username – That way you’d be installing it all in the final resting place and just have to change the site/home URLs to ‘move’ and point the nameservers to the new place.

    Thread Starter robnalexpress

    (@robnalexpress)

    use your IP/~username

    This is the part I don’t understand. How is this different than dev.domain.com?

    What do I need to do besides installing WP at dev.domain.com before importing?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Other than the fact that it’s an IP and not your domain name?

    You’re not MAPPING a domain to that account yet.

    Unless you ONLY mapped dev.domain.com to the new location, which can work, using the IP lets you not map anything and just build out.

    Thread Starter robnalexpress

    (@robnalexpress)

    You’re not MAPPING a domain to that account yet.

    This part I get.

    But I don’t know how dev.domain.com is mapped and I don’t know how to use an IP/~username. I’m trying to figure out how to do this.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    IP = the IP of your VPS

    username = The username for the account you added.

    Thread Starter robnalexpress

    (@robnalexpress)

    @Ipstenu- I really appreciate your trying to help, but fear we’re talking past each other. You may be presuming I know something I don’t.

    I certainly know what my VPS IP address and username are. What I don’t know is what I’m supposed to DO to change/prepare this new account before I can proceed. When you say “use your IP/~username” I don’t know what you mean. Use it for what?

    When I type https://67.xxx.xxx.xxx/~myusername/ into my browser, I get:
    Index of /~username

    Icon Name Last modified Size Description[DIR] Parent Directory –
    [DIR] cgi-bin/ 10-Oct-2011 18:53 –
    [DIR] images/ 10-Oct-2011 18:53 –
    [TXT] postinfo.html 10-Oct-2011 18:53 2.4K

    Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at 67.xxx.xxx.xxx Port xx

    So, what do I DO now? Thanks for your patience….

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Upload WordPress ??

    https://67.xxx.xxx.xxx/~ipstenu == https://ipstenu.org

    Therefore https://67.xxx.xxx.xxx/~myusername/ == what WILL BE yourdomain.com

    It’s an alias. I swear it’s not complicated. It’s just a different way to go to the same location. Just upload a file and see.

    Thread Starter robnalexpress

    (@robnalexpress)

    I’ll try it. What if I were to install WordPress using fantastico from cpanel of new account? So this is more about where WordPress thinks it lives than where it’s installed (the new account)?

    Can’t figure out how to upload to https://67.xxx.xxx.xxx/~myusername/ in filezilla. Shouldn’t I install to /home/new account/public_html?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    What if I were to install WordPress using fantastico from cpanel of new account?

    I’d never suggest that, for any account. Fantastico isn’t ‘fast enough’ when it comes to releasing upgrades, and if you upgrade yourself, then you get out of sync with Fantastico. Installing it yourself is easier than navigating WHM ??

Viewing 15 replies - 16 through 30 (of 47 total)
  • The topic ‘Move sub-site of multisite to its own install- same server’ is closed to new replies.