agrajagco

Issue Resolved;

2 issues were preventing things from working

1) the network title field was not being filled in properly
2) bad .htaccess from old multi-network instructions (pre 3.6 version)

The above example for the wp-config.php from my previous post was correct, and worked without modification.

WP Multi-Network appears to be working with the older “Networks for WordPress” sites as well at this point. I’ll continue setup and testing, thanks for publishing this plugin.

To make responding easier; This is an example of what I have, obviously modifying my domain to example.com. I noted that the brief “installation instructions” for the plugin just note to comment out “DOMAIN_CURRENT_SITE”… but doing this does not appear to modify the behavior. Should I be droppping more from the config to be compatible with “WP Multi Network”?

define('WP_DEBUG', true);
define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
#define('DOMAIN_CURRENT_SITE', 'example.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

I’ve removed the Networks For WordPress plugin and added the WP Multi-Network… but as Justin stated I can not add a network (but justin for the life of me I can’t follow how you got things working?)

Whats hard to understand is when adding network, there is no error message or anything to indicate why its failing, just a statement of “Network not created. Back to Networks.”

I’m wondering if my wp-config.php is overloaded… or not compatible with between the two. Does anyone who has a successful config have any more detail on what should NOT be retained?

Are we scorched earth trying to run our old sites and new over a DB that had both versions of the Networks in place?

Why is WordPress not standardizing networks management within their offering ? This is a difficult migration path to maintain as plugin projects lose their teams…