Support » Plugin: WP Multi Network » [Plugin: WP Multi Network] Can someone explain how this works?

  • Resolved LanceGrigsby

    (@lancegrigsby)


    I’m fiddling with the plugin as we speak, and I’m baffled by the lack of documentation for this. Sorry to complain! From what I can glean from the UI in the dashboard and the code, this plugin basically allows you to assign sites to domains you map to the installation–in other words, the mapped domains become the root site of another multisite instance using the same set of core files. Is this a correct description? Just trying to get my head around it. If this is right, then each blog is only one of many in the usual DB configuration, only it gets associated with one network or another.

    Andrea, can you draw some pictures for me? 🙂

Viewing 15 replies - 1 through 15 (of 17 total)
  • Thanks, Kyle. I had already found that, though. I think the only solution is to struggle through this thing until I figure it out–which I’m doing now. Be happy to contribute some documentation … I’ll report back.

    Lance-
    I’ll put it on my to-dos for tomorrow to test this out. I’ll let you know if I glean anything from my experiments.

    ~Kyle~

    Lance-

    Neither the documentation or anything I’ve read indicates in what order things need to be setup. So I’ve tried a few different approaches locally:

    Approach 1
    1) Setup parent MS with Multi Network plugin (wordpress.dev/test/parent)
    2) Setup 3 children sites (wordpress.dev/test/child#)
    3) Add 3 children sites in the Multi Network plugin

    I tried a few site installs on each child install to see if the parent would pick up on them – but it didn’t.

    Approach 2
    1) Setup parent MS with Multi Network plugin (wordpress.dev/test/parent)
    2) Create empty directory (somenetwork.dev)
    3) Added network in Multi Network admin to “map” (?) to this domain

    Nothing happened.

    From some of the banter back and forth (and andrea_r’s comments), this is more of a mapping plugin than anything else – it doesn’t physically create anything.

    I understand the theory behind it – and can see a few uses where I need it – but documentation is just so limited (as is my background with mapping) that I’m up a creek at the moment.

    Kyle,

    Nice work–thanks for the info. This is the kind of stuff that’s useful to read. I’m still waiting for some domains to propogate to my new sandbox, and then I’ll be off and running. To be continued …

    Kyle,

    I think I’ve figured this out–and it took some doing. What I’ve discoverd, both with the WordPress MU Domain Mapping plugin and the WP Multi Network plugin, is that half of the work required to set EITHER up successfully will depend on how familiar you are with how your registrar and host talk to each other (assuming your domains are not registered with your host). Also, my assumption from the beginning was that you had to have domain mapping in place prior to using the WP Multi Network–but that’s not the case. From the looks of it, you can use WP Multi Network without WordPress MU Domain Mapping.

    A couple of pre-requisites prior to configuring WP Multi Network:

    • All the domains you plan to use in your network need to be pointing to your host’s name servers. This is pretty obvious.
    • Once you’ve done that and given DNS enough time to propogate, you’ll then have to go to your host’s cpanel, add the new domains, and either park them or do some sort of the equivalent. If you use Site5, you’ll have to park them (see this thread); if you use Dreamhost, you’ll have to “mirror” them (see this thread). These threads apply to domain mapping; but as you’ve discovered, Kyle, the WP Multi Network is just another mapping plugin, so the prerequisites for using it are similar to setting up WordPress MU Domain Mapping.

    In a nutshell, if it ain’t working for you, then it’s probably an issue with your registrar/host’s domain settings. But once your domains have propogated and are properly parked or whatever, adding them to your network is pretty easy through the plugin GUI.

    Where I’m stuck now is figuring out why blog registrations key off of the mother blog and not their own admin options settings. For example, if you allow blog registrations for one domain in your network but not in the original parent network, it won’t work; seems you have to enable them in the parent network in order to be able to enable registrations in the child networks.

    And to further underscore your point …

    … this is more of a mapping plugin than anything else – it doesn’t physically create anything.

    That’s exactly right. When blogs get registered, they also seem to only get registered against the parent network, even if a user is attempting to register through a child network. And then it will be up to the admin to assign that site to whichever domain in the network it needs to be associated with. It would be nice if the plugin could allow users to login to whichever network they wanted and have their sites automatically assigned to that network simply based on the domain through which they logged in through–or maybe this is already possible through some option I missed?

    But, still playing and learning …

    Forgot to say something about CNAMES and A Records. In my test instance where I’ve sucessfully gotten WP Multi Network up and running, Dreamhost automatically created an A Record for the domains I mapped from GKG.net–don’t know if all hosts do this. However, when testing domain mapping, I’ve used a domain at GoDaddy before and mapped it to a hosted space at Site5, and I had to manually create either an A Record or CNAME (can’t remember which) in the GoDaddy cpanel for it to work. So again, whether you’re using the domain mapping plugin or WP Multi Network, registrar/host config is probably going to differ on a case-by-case basis. BTW, Dreamhost support had no idea what I was trying to do and couldn’t help … just had to figure it out.

    Wow. That’s an excellent breakdown. Thanks!

    When I get some time I’ll give it a go again.

    ~kyle~

    Lance –

    Did you ever figure out the registration issue?

    Thanks!

    Where I’m stuck now is figuring out why blog registrations key off of the mother blog and not their own admin options settings. For example, if you allow blog registrations for one domain in your network but not in the original parent network, it won’t work; seems you have to enable them in the parent network in order to be able to enable registrations in the child networks.

    Memitch08, is this what you’re referring to? If so, I think that problem still exists. Been a while since I messed with this, though …

    Yes – I’m stuck there too.

    I have the multi-network plugin – and registrations all go to the mother site.

    I’ve tried the domain-mapping plugin in conjunction with this – and I can’t get it to work either.

    The domain-mapping plugin alone allows blog registrations on the sub-sites, but then they are not visible because I haven’t been able to figure out how to map them correctly.

    When I don’t use the domain-mapping plugin though – and let the multi-network plugin assign the domains, then registration doesn’t work properly?

    I’d really like to get this resolved where the multi-network plugin corrects the regisrtation issue – and the domain-mapping plugin isn’t needed.

    Thanks for the follow-up! :))

    Hey both-

    I thought I’d point you to a premium resource for Multisite Domain Mapping and Networks. The two resources below bundle the plugin with an e-book and support. Both packages cost money but I’d bet my future first-born that the support and content of the e-books are stellar as they’re published by the famous Andrear here in the forums:

    Multisite Domain Mapping:
    http://wpebooks.com/professional-domain-mapping/

    Networks+:
    http://wpebooks.com/networks/

    Memitch08,

    I’d really like to get this resolved where the multi-network plugin corrects the regisrtation issue – and the domain-mapping plugin isn’t needed.

    … As for the registration issue, I contacted the developer directly, and he said he would look into writing that functionality into the plugin–but that’s where it stands as far as I know. But about using WP Multi Network WITHOUT the domain-mapping plugin, as both thecorkboard and I discovered:

    From some of the banter back and forth (and andrea_r’s comments), this is more of a mapping plugin than anything else – it doesn’t physically create anything.

    Once you install WP Multi Network and add your domain names, it’s just a matter of assigning the blogs to whichever URL in the network you want them to belong to. You don’t need the domain mapping plugin installed to use WP Multi Network.

    thecorkboard, thanks for the information!

    Lance & thecorkboard –

    Thanks for the information. I may look into the plugin suggestion more, but for the time being – I’ve corrected the registration issue I was having with the multi-network plugin thanks to this info here.

    removed :

    define( 'DOMAIN_CURRENT_SITE', 'memoirsite.com' );
    define( 'PATH_CURRENT_SITE', '/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );

    from the wp-config.php file.

    Note – my wp-config file did not have SITE_ID_CURRENT_SITE for some reason – so that was not removed.

    Now everything is working!

    Very cool… I will look into this myself! Thanks for the tip.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘[Plugin: WP Multi Network] Can someone explain how this works?’ is closed to new replies.