• Sorry to add more to the forum and I have read a lot about this – but I’m still scared to take any action without having my questions specifically addressed.

    I presently have a blog on my web site at https://www.domain.com/blog.

    It’s mostly a “private” blog (not advertised) for my friends and family. I upgraded to 3.0 without any problems.

    I would now like to extend to a multisite blog and have a “public” blog for my business.

    Am I correct in my understanding that the old one would then be https://www.domain.com/blog/private
    and the new one https://www.domain.com/blog/public
    or do I need to move this somewhere else?

    What happens to all my posts and content associated with my old blog? Do I just tell it what blog it should be associated with?

    What if someone visits https://www.domain.com/blog. What do they see?

    How easy will it be to keep my “private” blog semi-hidden from my public blog?

    I’m not super technical, but have been able to figure out most everything I’ve needed to do. I set up a multisite at work, but it was a fresh install. I’m just not sure about doing this over my exisiting site.

    Thanks in advance for someone walking me thru this and putting my fears to rest! I’ve had some bad luck and sleepless nights in the past, so I want to make sure all my ducks are nice and lined up before diving in!

Viewing 6 replies - 1 through 6 (of 6 total)
  • When you enable the network, the blog you have become the main blog in the network. the address stays the same.

    (exception: the main blog gets a /blog/ stuffed in the permalink if you pick subfolders. since your blog is old, this choice is removed, but you can force it, as well as force it to remove the /blog/)

    It’s mostly a “private” blog (not advertised) for my friends and family.

    Are you keeping search engines out? then it’s not private. ?? There are privacy plugins though, and a built-in option to tell the search engines to go away.

    Stuff to consider:

    – since you have an install at /blog/ already, what’s in the root?
    – if you go with what you have now, the blogs will be /blog/newblog/
    – if you lock out search engines in the main blog via the privacy settings, they will stay away from the other blogs too. cuz it’s the main site and the blogs are “under” it.

    I had an install of my own at /blog/ and converted it to a network. But instead of messing aroudn with settings and stuff, I tore down my install in the /blog? folder and put it in the root, taking advantage of the internal /blog/ permalink for my main blog. Now the other blogs in the network are mydomain.com/otherblog/

    Oh heck, it’s right here:
    atypicalife.net
    See?

    Ignore the messed up /blog/ permalinks showing the same info as the home page. that’s my doing, I need to wrangle the theme. And change it.

    Tho if I wanted to have a public are and a private one, I wudl move my private one to not be the main blog.

    And to calm your nerves, remember as long as you have backups of every single thing, you can restore it to where it was.

    Thread Starter kalana1338

    (@kalana1338)

    I don’t really want to move it to the root because I do have other things there. I really want the Web site home page to be one thing and the blog to be seperate.

    Assuming I leave it as is and my current “private” blog becomes the main blog, and I create a second “public” blog, how difficult would it be to switch those around. Could it be done and what would it entail? Did I understand correctly that if the “private” blog was switch to not be the main one I could still block search engines to it, but not to my new main public one?

    And yes, I do have the search engines blocked. It’s not that I want it “locked down and no you can’t get in!” but just don’t care to have it out there easily accessible to the world.

    If I did this and decided that I didn’t like it, does reverting back to a single instance just involve removing the code or would be a hard process?

    Thanks so much for your help!!!

    Assuming I leave it as is and my current “private” blog becomes the main blog, and I create a second “public” blog, how difficult would it be to switch those around.

    More difficult that turning off the network, actually. well, depending on the blog and/or how comfortable you are mucking around in databases. At the simplest form, you could just use the internal Export/Import to move the content.

    then verify the second blog now how all your main blog content, and delete the content of the main blog. *whew*. then you can fiddle with privacy.

    Thread Starter kalana1338

    (@kalana1338)

    Yeah I’m not comfortable at all in the database. Export/Import seems ok I think.

    One last question then I’ll make a decision. ?? Could I not just install a second single instance of WordPress on my site and just run two installations and not mess around with the multisite network? So I leave my current site alone and then install a second database (my host allows multiple databaes) and second instance of WordPress? Better or worse (or equal) option?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Could I not just install a second single instance of WordPress on my site and just run two installations and not mess around with the multisite network?

    Sure, you can do that.

    I would say … equal to worse, since then you have to upgrade everything, every plugin etc, twice, and you have two IDs on separate blogs.

    If you’re only ever going to add just the second site, and you’re not comfortable with doing all this mucking around then yeah – do a separate install.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Single to MultiSite Questions’ is closed to new replies.