WordPress.org

Support

Support » Multisite » [Resolved] MS Conversion Requires Deleting Sub-domain?

[Resolved] MS Conversion Requires Deleting Sub-domain?

  • I’ve been reading and watching WP developers give presentations on WP v3, but have a lingering question…

    Currently I’ve got WP installed into a sub-domain:
    http://travelogue.travelvice.com

    It’s my intention to install WP3 w/ MS enabled into the root of that domain — http://travelvice.com — and fold (export/import) that sub-domain installation into it.

    It’s my understanding that in CPanel (as I’m on a shared HostGator server), I’d have to make a sub-domain named “*” (wildcard).

    I’m under the impression that it’s required for me to delete the ‘travelogue’ sub-domain that I’ve already established in CPanel… but if this is so, but what do you normally do about the custom directory I’ve been using (http://travelogue.travelvice.com/postfiles/) to store media in?

    Note: I have not used the WP upload mechanism for any of those files — images aren’t maintained by WP. But there is another sub-domain that I wish to fold into the install where they have been.

    Thoughts?

    //craig

Viewing 15 replies - 1 through 15 (of 16 total)
  • Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    But there is another sub-domain that I wish to fold into the install where they have been.

    That’s the only reason why you would delete the existing subdomain in cpanel. Two different things can’t exist in the same spot at the same time. the physical one will override the one in multisite.

    The media you’ll have to either move to the corresponding folder off the root, or plunk it elsewhere and redirect the old links.

    The media you’ll have to either move to the corresponding folder off the root, or plunk it elsewhere and redirect the old links.

    What would be the result of moving that folder over to the root and inside of the blogs.dir directory for that specific site?
    /wp-content/blogs.dir/2/postfiles/

    Would WP generate the virtual sub-domain and still keep existing media link URIs intact?
    http://travelogue.travelvice.com/postfiles/

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    Would WP generate the virtual sub-domain and still keep existing media link URIs intact?

    no. you’d have to fix them.

    like I said “or plunk it elsewhere and redirect the old links. ” which can be done via htaccess.

    I see. Thanks for the insights Andrea.

    It sounds like I won’t be able to create any reference to a file or folder under http://travelogue.travelvice.com/ that isn’t generated by WP itself.

    So what happens when Google needs to have files hosted at the root of the sub-domain to prove that you have control over the site (such as required in Webmaster Tools) or to have custom AdSense adverts displayed instead of Public Service Announcements, which also requires the html file(s) to be hosted at the root of the sub-domain?

    for Google Webmaster verification, make TXT record on your DNS which can be done in most of hosting or domreg provider.

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    It sounds like I won’t be able to create any reference to a file or folder under http://travelogue.travelvice.com/ that isn’t generated by WP itself.

    Yes, actually, you can. I’ve done it by placing the folders I need off the *root* domain.

    Down side is it shows on all sites… but I think you can block that via htacess.

    And as pointed above, there are alternative ways to verify Google Webmasters tools. (also done it) There’s probably a workaround for the Adsense too, like placing the file in the theme folder maybe.

    I’ve done it by placing the folders I need off the *root* domain.

    Wacky! So… unless blocked by .htaccess, any file or folder placed off the root will be available under all virtual sub-domains? I must be misreading you.

    http://travelvice.com/examplefolder/
    http://virtualsite1.travelvice.com/examplefolder/
    http://virtualsite2.travelvice.com/examplefolder/
    http://travelvice.com/specialfile.txt
    http://virtualsite1.travelvice.com/specialfile.txt
    http://virtualsite2.travelvice.com/specialfile.txt

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    Yes sir. 🙂

    Cool, huh? 😀

    So… wouldn’t that mean that in my original question about directory placement and redirects, moving the postfiles folder to the root domain would allow for http://travelogue.travelvice.com/postfiles/, retaining existing URL links?

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    And just for fun! I went and did this on my test install.

    main site:
    http://mommieblogs.com/test-folder/
    http://canada.mommieblogs.com/test-folder/
    http://another.mommieblogs.com/test-folder/

    It even works on mapped domains:
    http://quilti.com/test-folder/

    Brain broke yet? 😉

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    And my original answer:
    The media you’ll have to either move to the corresponding folder off the root,

    travelvice.com/postfiles/ is what you’ll do.

    Wow — wacky, wacky stuff.

    Isn’t it thought of as an issue that you can’t create physical directories at your root domain without interfering with possible pages/posts (if /%category%/ or whatnot is the base) in all virtual sub-domains or mapped domains?

    Side note: I think concern is warranted regarding the performance requirements to have each and every image in a post load via redirect. As you suggested above as an alternate solution, I imagine it would be advisable to place the folder elsewhere off the root (and use a SQL Update in the database to modify all instances of the files path, leaving a 301 redirect in place for stragglers or external links not under your control). Note to others: code examples of that can be found here.

    No, it’s not an issue of interfering. At least, it’s not word press’s fault. You can do the subdomain trick with a lot of other apps, and they all have this ‘flaw’ (which isn’t a flaw, it’s just how things work). This is how web servers work. We use it to our advantage at work, by having shared files there. The ‘problem’ is that WordPress doesn’t have a built in way to share all the files in the media tool, because the concept behind multisite doesn’t include any site sharing tools.

    This’ll hurt your head even more.

    I have a subblog named code.domain.com AND a folder named code. Works just fine. 🙂

    Basically, wordPress or not, this has always been an issue for websites. And no, the htaccess redirect won’t affect your site performance noticeably. I mean, we’re already redirecting images as is 🙂

    Howdy Ipstenu, was hoping to see you in this thread. Thanks for your thoughts.

    I will mark this thread resolved, as the original question has certainly been clarified.

    If there’s enough for an entry, I’d very much enjoy seeing a post on your site regarding the folder/subblog both being titled ‘code’ — or perhaps right here if there isn’t. ;D

    Cheers.

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    The sort version for code.ipstenu.org and ipstenu.org.code/ working is the subdomain is *virtual* so there’s no folder on the server to interfere with lookup.

    Tag team strikes again. 😉

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘[Resolved] MS Conversion Requires Deleting Sub-domain?’ is closed to new replies.
Skip to toolbar