Issues with sites within networks (404s and redirect loops)
There are a couple issues that I keep running into trying to get this working on my install. First, when serving the whole instance from a subdirectory, networks within the multisite don’t work: domain.com/main-network/sub-network/site always returns a 404 even though I can get to the sub-network network admin page.
I decided to try to serve wordpress from root instead. This seemed to work better, but there are still blocker issues. With the main network at domain.com/ and the subnetworks in subdirectories (domain.com/sub-network), subnetwork sites (domain.com/sub-network/site) do exist and I can navigate to pages on them, but all static resource requests return 404. This means no js and no css at all. This is the case on both the front and back end. WordPress is requesting assets from domain.com/sub-network/site/wp-includes and domain.com/sub-network/site/wp-content. This is obviously a blocker for me.
Another issue with the plugin is that domain.com/sub-network/site/wp-admin/ and domain.com/sub-network/site/login both have redirect loops. Only going straight to wp-admin.php can I get to the site dashboard on subnetwork sites.
Anyone have any experience with these issues? How might I go about solving them?
- The topic ‘Issues with sites within networks (404s and redirect loops)’ is closed to new replies.