Networks for WordPress
[resolved] Getting Started on localhost - Network admin access problems (4 posts)

  1. cereus
    Posted 3 years ago #

    Hello! And first a big thanks to the developers for such great tools!

    I am working at a small institution and as a side project am trying to set up wordpress/buddypress/network system.

    I can install wordpress, get multisite enabled, install buddypress. All works fine. Now I want to make independent buddypress setups for each group in the institute. So I start fresh - wordpress installed, enable multisite and then install Networks for WordPress.

    I can install the Networks for WordPress Plugin, and can create networks but it appears that I can only access Network Admin for the first site that I created. ie institute.intranet is from the fresh installation of wordpress, and group1.institute.intranet, group2.institute.intranet are Networks that I create after installing Networks for WordPress.

    After this, I install BP Multi Network Plugin (in a created mu-plugins directory and copy php file - took me a bit to figure that out). Then I install buddypress and I'm supposed to activate buddypress on each network (group1.institute.intranet, group2.institute.intranet). However, as mentioned above, I can only access Network Admin for my first site (Network Admin:institute.intranet but I can never get Network Admin: group1.institute.intranet).

    Since my background is not in server setups, I wonder if I am missing something straightforward.

    For example, I running on the local server machine, I have altered the local hosts file to point my sites (institute.intranet, group1.institute.intranet,) to the server IP (and once I have things running will focus on dns resolving for the institute later) but perhaps this has messed things up?

    Or is there just some simple menu item somewhere that I am missing.


    Thanks in advance for any tips, suggestions or links to something I should read.

  2. cereus
    Posted 3 years ago #

    Hmmm. Appears that
    Comment out DOMAIN_CURRENT_SITE in your wp-config.php file.
    How I missed that...

  3. will_c
    Posted 3 years ago #

    @cereus, thanks for the tip! This got us up and working as well. It seems to only be a problem when using sub-directories. I followed the advice in the following post in an effort to provide a more robust solution than simply commenting the line out, but it didn't help.


    define( 'DOMAIN_CURRENT_SITE', 'yoursite.com' );
    $site_domain = 'yoursite.com';
    if ( $_SERVER['HTTP_HOST'] != $site_domain ) {
        $site_domain = $_SERVER['HTTP_HOST'];
    define( 'DOMAIN_CURRENT_SITE', $site_domain );

    I was still directed to the main network admin rather than the sub-network admin. I think that's probably because $site_domain will still be yoursite.com even for sub directories. I tried hardcoding $site_domain to 'yoursite.com/subdir', but I received a redirect loop error. Commenting out the DOMAIN_CURRENT_SITE got it back working.

    Have you run into any problems after simply commenting that line out?

  4. cereus
    Posted 3 years ago #

    Well, I haven't had any problems with domains, yet, but I don't have a system up and running.

    The next big problem is I don't get separation of my buddypress networks. When buddypress is installed on a network, it adds all the blogs to the network (which can be deleted in the table manually). The same thing happens with all users. New blogs created on different networks aren't added. I can remove the extra blogs from the tables, but I don't know which tables contain the information about which user belongs to which network.

    And I can't figure out a good way to make the networks private.

    So I keep working.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Networks for WordPress
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic