agrajagco

I would move your request over to the github for this, report it as an issue there, this forum seems to be devoid of any monitoring/input from the team.

https://github.com/stuttter/wp-multi-network/issues

Check if there is already discussion on the issues and conversations areas perhaps?

I’m not a developer but we are successfully using (and importing via wp All-in-one Migration w. the multi-site extension) with WP 4.9.1 and the 1.8.1 version of the plugin.

How are you bringin the sites in? The error you are describing sounds like your “import” is not properly handling the blog/site ID, or there is a flaw in your networks.

Verify wp-config multi-site is enabled based on the multi-site docs (wordpress coda) and then how your htaccess is set up. Some of my previus posts go deep into what the mechanisims are (based on the blogs by the wordpress developers who created this).

The thing to realize this plugin enables GUI for functionality coded inherently into wordpress that drives wordpress.com and other sites in parallel (based on the www.ads-software.com developers video presentation I shared in my historical posts).

The github project is here: https://github.com/stuttter/wp-multi-network

I am however, along with the users probably who have this in production, worried about the fact there is no version support on this to be cuirrent with 4.9.1 (actually I’m hopeing this just becomes a feature somewhere in the 5.x chain of releases of WP and not a plugin)

Perhaps reach out to the servmask team on their help site?

https://help.servmask.com/

Yes, and depends, we were taking one completely different domain as a template and generating new sites as dev templates over and over for a common branded set of companies.

I worked a bit with the WP All in one migration team with their multi-site extension to get it working properly for multi-network between hosting, and same host multi network import as well. All working very well.

Search/replace worked ok as well but only for when we were dealing with dev domain switch to prod domain.

There are a few other important settings to have in your wp-config.php, i’m assuming you have done that already but lets double check:

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);  (You probably need true here)
$base = '/';
define('DOMAIN_CURRENT_SITE', 'example.com');
define('PATH_CURRENT_SITE', '/');
...
...
define('WP_ALLOW_MULTISITE', true);

One more good read, again this is for understanding how things work, you might not exactly make the same changes, based on what you figure out as you enable debug and the troubleshoot from there. https://codex.www.ads-software.com/Changing_The_Site_URL

You can enable wordpress debugging to get more detailed error messages. Start here:

https://codex.www.ads-software.com/Debugging_in_WordPress

The two arguments can be added near the top of the file and commented out when you are done troubleshooting, for future use.

For example from my wp_config.php (I just use the edit file in my hosting’s file manager to change this).

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 *
 * For information on other constants that can be used for debugging,
 * visit the Codex.
 *
 * @link https://codex.www.ads-software.com/Debugging_in_WordPress
 */
define('WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

If you need to correct something at the configuration or database layer related to the import, after looking at what the debugging is telling you, the following can help.

(1) Are you importing into a multi-site or multi-network configured wordpress (which plugin are you using)?

(2) Is only the newly imported site failing, your statement of “different site on the same host”… is the site you were working on “yesterday” still working (can you access wp-admin/ on the site from yesterday)

(3) Do you have access to your underlying DB with phpDBadmin or something like that?

Back the DB up before starting, make sure you understand how to recover the DB if you need. Make changes one at a time and verify impact so you can go back and undo if necessary.

First a primer on the “first site” DB. The additional “sites” end up with a number in front of these table names. This is a good quick reference to the overall DB layout

https://codex.www.ads-software.com/Database_Description

There is a good database writeup of what the running wordpress instance uses to map the sites and their information in the DB.

YOU WILL NOT FOLLOW THIS EXACTLY, this is more for education on how things are laid out. You will need to verify what the wp_site, wp_options, wp_blog, etc. and then understand which ##_wp_blogs the site is mapping too.

https://wpengine.com/support/how-to-change-a-multi-site-primary-domain/

MAKE A BACKUP BEFORE CHANGING ANYTHING IN THE DB (yep I repeated it, here comes the rest…). Make changes one at a time and test so you understand the change and impact… back out before doing a bunch of stuff experimenting.

In the past I’ve had to update in the DB to correct URL changes that might have come in from the import… or if importing but multi-site/multi-network as a plugin is not enabled…

If you are importing plugins… perhaps version issue?

Make sure you are backing up before each import attempt…

One thing I’ve found that helped sort out the relationship between the base install blog and the network/multi-site blogs was the database structure that is created.

The following site has a good writeup, on multi-site, and teh multi-network is very close to this.

https://wpengine.com/support/how-to-change-a-multi-site-primary-domain/

I dont suggest doing this (changing primary domain) unless you are prepared to troubleshoot redirection (have more that the 2 domains you are working with configured already so you can fall back to connecting to the wp-admin/network on that site to start working on recovering.
MAKE DATABASE BACKUP NOW
Basically the default tables created with the base install blog are
NO REALLY, GO MAKE A DATABASE BACKUP NOW
wp_[tablename]

The important ones for domain to site to blog are

wp_options
wp_site
wp_blogs

Once you create additional Multi-Site blogs (or multi-network child site) you will see the same table structure, but with a number in front of it.

##_wp_options
##_wp_site
etc. etc.

You can resolve what blog-id/site-id is to which domain from looking at wp_blogs

Ed,

Download the plugin manually and install, it will not upgrade the plugin before you upgrade, and you need to manually install the plugin to get the upgraded word-press to run.

To restore things working I unzipped the download of the current version of the plugin to

~/public_html/wp-content/plugins/wp-multi-network

I moved the old path out to a safe place and replaced with the new zip file path unpacked.

Also worthy content going through WP Multi-Network in a developer presentation by John James Jacoby.

Good news was able to fix, it appears that we set the base url of the site (too many cooks in the kitchen) before switching over the DNS

Great article on Changing a MultiSite Primary Domain, gave walk through of the significant database tables to be paying attention to.

Note that:
Your base install tables will be named like wp_options, wp_posts, etc. Our fix was in adjusting the wp_options siteurl value back (which probably had been mis-set in UI before cutting over to the new erz.net.

Your “networks” tables will have table sets that have naming like 4_wp_posts or whatever incremental network/site you are up to.

Changing that wp_options siteurl value back to the original example.com fixed things.

An update to this, we proved it is not redirecting in the hosting, the site actually works, ONLY wp-admin calls are redirecting!!!!

<mindblown>

not working (redirected when calling / or wp-admin)
174.XX.XX.XX – – [21/Sep/2016:20:48:28 -0700] “GET / HTTP/1.1” 301 – “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36”
174.XX.XX.XX – – [21/Sep/2016:20:48:40 -0700] “GET /wp-admin/ HTTP/1.1” 302 – “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36”

working (actual call to site content!!!)
174.34.135.242 – – [22/Sep/2016:20:52:33 -0700] “GET /about/ HTTP/1.0” 200 16591 “-” “Mozilla/5.0 (compatible; MJ12bot/v1.4.5; https://www.majestic12.co.uk/bot.php?+)”

I’m assuming this is in the wp DB at this point? is there a database primer on the wp multi-network and its relationship to inbound request handling?

It would make sense on the “edit” page of the network, where you name it, to be the landing place for configuring that IMHO. The quick nav contexts for setting it… groupvote:

I’ve not mixed multi-site with multi-network but here are a few things to check;

Navigate to Networks > All Networks > (mydomain.net or whatever)
“Edit” your “network” that is the top level of the sites you are working with.

You will see a UI that lets you name the network, provide the details and path, and then has a “Site Assignment” section at the bottom. Are the sites you are talking about appearing in the “available sites” list and not the “network sites” list? Move them over and “update” and then re-test?

<jazz hands> This is AWESOME!!! </jazz hands>