[Plugin: Networks for WordPress] Reassigning sites creates redirect errors

I was able to correct the redirect issue. Thanks to another post in here I learned which database table to review, and noticed, in wp_blogs, the site domain was chamberofcommons.chamberofcommons.com , rather than the original chamberofcommons.com. So it had adopted a subdomain when I re-assigned it. removing the sub resolved that site.

So, does this mean that one simply should not attempt to re-assign a primary domain under a network? Or is there a workaround?

Are you using subdomain or subdirectories for your sites? I’m concerned about the subdomain prepending issue, but more info on your setup would be helpful for troubleshooting. Any domain mapping involved? Are you using a plugin for multiple BP sites?

Moving a root site (the “primary site” at ‘/’ or without a subdomain) to another network can render that site temporarily inaccessible if the destination network already has a root site. It’s still useful for quickly moving sites around, though.

If you want to move the root site to a new network for production use, you should create the destination network without a root site.

Thanks, David.
Using subdomain. no domain mapping plugin.
All current versions.
I fully get the point of root sites. but do think it would be helpful for the plugin to disallow it. Or warn.

I think I found the issue with prepending the domain name. There was nothing to account for a subdomain site having no hostname component. This will be addressed in the next release, and an updated development release should be out in a day or two.

I’ll also work on some kind of warning for moving sites when the path on the new network would block access and maybe for root sites too. It’s unfortunate that the “Network Admin” metaphor makes the root site so critical to management.