WordPress.org

Ready to get started?Download WordPress

Forums

Splitting Blogs into two subdomains easily (5 posts)

  1. fleetadmiralj
    Member
    Posted 3 years ago #

    I think I might have the answer to this, but I didn't see a post about the specific setup that I was looking for, so I just wanted to make sure.

    We are setting up a WordPress 3 blog installation with a Network at a domain, say, http://www.example.com.

    We would prefer that the blogs on this installation be split up into two (and maybe more in the future, but for now two) subdomains, say:

    group1.example.com and group2.example.com, where the address in the URL should be at group1.example.com/myblog and other blogs should be at group2.example.com/anotherblog

    We could install two instances, but keeping once instance would be ideal

    My next thought was to see if we could create the blogs at an address like http://www.example.com/group1/myblog and then we could just map any address that's at group1.example.com to the blog located at http://www.example.com/group1, but it doesn't look like it will let me add an additional directly like that when creating a new blog.

    Then I ran across a couple posts using the WP Multi Network plugin, but unfortunately there doesn't seem to be a lot of documentation about the plugin online.

    So I guess what I'm wondering is, could we do something like this:

    Create 1 network called "group1" and another network called "group2," create multiple blogs under each network, and have it set up so that it can pretty easily forward addresses from group1.example.com to the blogs in the group 1 network, etc. without having to do mapping for EVERY blog individually?

    We can handle the domain mapping ourselves here, but we just don't want to have to do it for each blog individually.

  2. Yeah, you want the multi network plugin. Set up the original install as a subfolder install. Map the subDOMAINS to it. blogs off the subdomains will automagically be subfolder ones.

    So that was kinda what you said. :)

  3. fleetadmiralj
    Member
    Posted 3 years ago #

    OK, so far so good...sort of lol.

    We got the WP Multi-Network plugin, and are able to create multiple networks, and multiple blogs (and the links to those blogs actually work...we had a hiccup where AllowOverride was turned off so none of the sub-blogs actually worked, heh).

    However, we've now run into this problem:

    The original domain is, say http://www.domain.com. We've created another network at http://www.example.com, and we've created a second blog under each (say, http://www.domain.com/blog1 and http://www.example.com/blog1).

    everything under http://www.domain.com appears to work OK. However, when I click on the blog post title (or archive link or category link) at http://www.example.com, it just redirects to http://www.domain.com. And if we click on those at http://www.example.com/blog1, we get a WordPress not found error (though we can access the blog index and blog admin just fine)

    So there appears to be some problem with it recognizing anything under http://www.example.com that isn't a blog index or blog admin. We might be able to figure this out tomorrow on our own, but I just wanted to see if anyone had any ideas in the meantime. Do people think this is some domain mapping issue? I had seen some people suggesting using a domain mapping plug-in, but I'm not sure if this is what it was for or not.

    (I think the problem we're running into is that, there are two of us working on this...me, who is pretty much the WordPress expert, but has close to 0 server experience, and the server expert, who has 0 wordpress experience, so sometimes trying to figure stuff out is a matter of whether we can successfully connect our two areas of expertise correctly lol)

  4. You don't need the domain mapping plugin, but you DO still need to do some of the server-side steps. ;)

    For http://www.example.com, did you park it on top of domain.com? You have to tell the server where it shoudl go when the request hits the box.

    (Server admin guy: create a ServerAlias so that domain.com and example.com live in the same doc root.)

  5. fleetadmiralj
    Member
    Posted 3 years ago #

    Well, we already had the ServerAlias assigned. However, what we did to is try the suggestion here:

    http://wordpress.org/support/topic/404711

    That seemed to work. The one site (www.example.com/blog1) still didn't work, but any blogs we created after we made the change did.

    Sooo...unless we run into another problem, it looks like we're on the right track again for now.

Topic Closed

This topic has been closed to new replies.

About this Topic