Network.zero as root domain in dashboard

I’m having the same problem.

I set up Multi-site on my website and then downloaded wp-multi-network with wordpress’s built in installer. I activated it, but for got to comment out DOMAIN_CURRENT_SITE in wp config. I created a second net work called Community off the same domain. I also created a second site called BackPage off the first network.

https://www.powerfuldragonwisdom.com = Primary Network and Only Domain name.
https://www.powerfuldragonwisdom.com/BackPage = second site on Primary network.
https://www.powerfuldragonwisdom.com/Community = Second Network off of primary network.

I then realized I still needed to comment out DOMAIN_CURRENT_SITE in wp config. I did so by using two back slashes; //define(‘DOMAIN_CURRENT_SITE’, ‘www.powerfuldragonwisdom.com’);

This is when I started having the problem with Network.zero. I got:

“The server at?www.powerfuldragonwisdom.comcommunity?can’t be found, because the DNS lookup failed. DNS is the network service that translates a website’s name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing?Google Chrome?from accessing the network.”

AND

Error establishing a database connection

If your site does not display, please contact the owner of this network. If you are the owner of this network please check that MySQL is running properly and all tables are error free.

Could not find site?www.powerfuldragonwisdom.com/backpage.?Searched for table?db_blogs?in databasekennedy_cdfkcd. Is that right?

What do I do now??Read the?bug report?page. Some of the guidelines there may help you figure out what went wrong. If you’re still stuck with this message, then check that your database contains the following tables:
? db_users
? db_usermeta
? db_blogs
? db_signups
? db_site
? db_sitemeta
? db_registration_log
? db_blog_versions

I then deleted the back slashes in wp config that commented it out. I then got:

“This site is using a?new generic top-level domain?(gTLD). If you have used?network.zero?to access an internal site in the past, contact your network administrator.”

I then Deleted the site and the network but they still show up when I hover the mouse pointer over “My Sites” on the top bar and when I go to https://www.powerfuldragonwisdom.com’s Admin Page on the Dashboard tab on “My Sites” they show up.

How do I permanently delete these and make sure everything is working correctly? Also, once this is fixed, do I or do I not need to comment out “(‘DOMAIN_CURRENT_SITE’, ‘www.powerfuldragonwisdom.com’);” for it to work correctly? And how do I make sure Network.zero does not show up in may network again?

Thanks.

I had no luck with this, so I started anew and opted out of using this plugin. ??

I’ve had this happen to me several times recently. It seemed to be correlated to some site movement and network deletions. Anyway, only way I found to repair it was via manual DB manipulation. The network.zero URLs are in the siteurl and home columns of a blog’s respective ‘options’ table. For example, blog ID 9 will have a wp_9_options table(amongst other). Update those 2 columns with the correct URL. You’ll have to do that for each blog that has been orphaned. And be ready to do it again, as I’ve had to fix mine a few times in the last week while trying to figure out the cause. I can tell you that it’s not the forgetting to comment out the line in wp_config.php. Mine had been commented out the whole time.

Hope this helps.

UPDATE:
I can 100% of the time create network.zero (orphaned) sites.

Start out with 1 network.
Add a couple sites to it.
Add another network.
Immediately edit that new network (you don’t need to make any changes, just click update).

The result is that any sites that you have under the first network will be orphaned, and their respective wp_#_options tables will have network.zero for their URLs.

Maybe it’s just something I have going on here…if it is, I have no idea what it might be. Any ideas would be appreciated.
Thanks.

we all have it going on…

Thanks…that’s is good to know. The good news is that I rarely have to edit networks. I sure wish that an update appears for this plugin soon…I would myself feel more comfortable about its long-term stability and availability.

same here – but with the last update not being available on wp.org but on github, this seems not to be a priority with the plugin authors.

agreed…it concerns me too.

I’m experiencing the same issue on my site. Posting here to follow this topic.

I anyone aware of any other plugins or options that do the same thing?

I am not aware of any other current plugins that do this. There was another, however if I remember correctly when I looked at it is was very old and appeared to be essentially discontinued.

Did anyone tried this issue with the current version at github? It seems that this issue is already fixed version 1.8.0 of WP Multi Network: https://github.com/stuttter/wp-multi-network/commit/b87a983d533e04fba1a51c6c7412a1031dd38ee4

If you test this please use a testing environment. Because this version is not released yet.

Kind regards
Robert Windisch

1.8.0 only solve for network zero, but all other sites in other network are detached from any network, making them unavailable. I need to manually fix it by updating wp_blogs table for all sites with site_id=0

Well, I don’t want to go tooooo far out on a limb here…:) but, I think this entire network.zero and its related site IDs of zero has been solved/fixed with 1.8.1.

I went in and messed around quite a bit with updating networks in some strange ways, and it all seemed to perform as expected…i.e., no orphaned sites.

If no one disagrees, go ahead and feel free to ‘solve’ this issue. (I’m not sure how to do that).