Support » Plugin: Networks for WordPress » [Plugin: Networks for WordPress] Pre Install questions

  • Kathy_Goss


    We’ve developed a multi-site, multi-db with custom plugins for user-generated sites, whereby the user sites are using a default preconfigured blog template.

    We want to create a sister site using the same basic plugins (capabilities) but with a different theme, categories and blog template. There would be an overlap with user base; some users may want a site in both networks and content sharing between sites.

    I’ve looked into using a combination of a multi-domain plugin plus domain mapping to establish this but I’ve run into some issues. Now I’m trying to determine if Networks-for_Wordpress would be a better alternative.

    Reading through the documentation and forum, I still have questions:
    1. In the documentation it state: “Each Network can have its own set of plugins, themes, administrators, permissions, and policies, but all will share a database of user accounts.” Does this mean that plugins and themes are installed separately into each network? In other words, if you wanted to use the same plugin in both networks, is there a duplicate installation or a single installation but separate network activations? If I have the same basic plugin for both sites, but each have custom variation, how would this work?
    2. Global tables. Our current multisite has a support system and global indexing that uses global tables. Does the issue related to global tables mean a. that only the sites in the first network will be included in the support system? or b. All network sites will be included in the support system?
    3. Are the networks hierarchical? Would our original site be a parent to other networks in any way or are all the networks equal/independent?
    4. Would there be a problem signing up for both networks with the same user name and email?
    5. Does my use case seem like a good fit?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author David Dean


    1. It just means that plugins and themes can be enabled / disabled per network. So, single installation but multiple network activations.

    If you want to use a plugin that has been modified separately for two different sites, you would have to either:
    A) Merge those changes into one plugin and use this site ID to run the appropriate code for the respective network, or
    B) Rename the modified plugins so they can both be activated by the same install. You can then activate one on each network.

    2. b – All sites on all networks will be included. However, be aware of any implications this might have for links in your support system, since it may assume that paths are unique.

    3. No. All networks are equal.

    4. Since the user tables are shared, it would be the same as the user trying to re-register with the same credentials. He/she would probably get an auto-generated username, unless your system prevents duplicate email addresses.

    5. That’s hard to say! This would certainly facilitate data sharing by keeping everything within one $wpdb instance and, if you expect a significant overlap in users, it’s always nice to let people use their existing credentials.

    The only caveat is that you should test any plugin you plan to run on multiple networks, to make sure it doesn’t generate and store URLs for your main network only, or something like that.

    Let me know if you have any further questions.



    Thank you for your in-depth answer; there is much to sort through and implications and trade-offs regarding each alternative. Do you have consulting services?

    Plugin Author David Dean


    Sure! But I want to be up front and tell you that I may not be the best person to help you sort out the alternatives, as I have never used domain-mapping.

    You can email me at david at generalthreat dot com if you’d like to discuss a consulting arrangement.

    Always happy to help!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: Networks for WordPress] Pre Install questions’ is closed to new replies.