'Network Admin' link doesn't work in v3.2.1

  • Hi, I was given the task to run a network of blogs under a domain. I didn’t create this network, and unfortunately I do not have any contact of the original developer. I was able to create new blogs, but ever since I upgraded to the latest wordpress version (v3.2.1), I am not able to connect to the ‘Network Admin’ panel. The link is visible under “Howdy…”, but it redirects to nothing.

    For my situation, I have my main domain mapped to 5 blogs. Typing the main domain’s url (“maindomain.com”) in the address bar will come up with a blank page as it doesn’t have its own blog or any content in the ftp directory. We merely used that domain to host the files of the blogs.

    I can access the WP backend of each blog via “mappeddomain1.com/wp-admin/”, “mappeddomain2.com/wp-admin/”, etc.

    In the old wordpress, I was able to access the network admin page via the “Super Admin” modules in the left hand corner.

    Then in the latest version, I have to click “Network Admin” underneath the “Howdy..” link. Unfortunately, instead of the page going to “mappeddomain1.com/wp-admin/network/” it redirects to “maindomain.com/wp-admin/network”.

    This is the point where I have been looking for solutions in the forums to no avail. A ‘maindomain.com/wp-admin’ doesn’t exist—just the mapped domains.

    Can someone help me or point me towards the right direction on getting this solved?

    I’m linking an image of how the blogs are set up in the directory.

    https://f.cl.ly/items/2b1T0P1q2T2P3C3A1s0c/wordpress-folder-structure.png

    Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)

  • The network admin area was created in 3.1. So you must have skipped that.

    And no – you cannot get to network admin under mapped domains or subdomains. basically the sub sites. you *must* go to the main site and access network admin.

    Typing the main domain’s url (“maindomain.com”) in the address bar will come up with a blank page as it doesn’t have its own blog or any content in the ftp directory. We merely used that domain to host the files of the blogs.

    a blank white page is a php error. if you’ve done something to disable the main blog, you’ll need to undo it. at least so you can access the backend of it and this, network admin.

    Thread Starter magnetmedia

    (@magnetmedia)

    Yes, Andrea, I was running wordpress 2.9.# before I upgraded it to v3.

    My main domain is: https://zoominonlinedev.com/ and there isn’t anything set up (no blog or a index.html page). It’s not blank, but it has the default contents of an unused domain. We just used that main domain to map the sub sites.

    How should I go about creating a blog on the main domain?

    Where did you install wordpress?

    Thread Starter magnetmedia

    (@magnetmedia)

    It was installed it in the zoominonlinedev directory.

    What’s weird though, I don’t have ftp access to the zoominonlinedev.com, but I can access the ftp through each of the sub site’s domains. Each ftp links to the same wordpress files and directories.

    I’ll see if I can find a way to get the main domain’s ftp info and reinstall wordpress. I won’t be able to do this until tomorrow. I’ll follow up when I get into work tomorrow. Thanks!!

    I don;t think reinstalling is a good idea. Maybe hook up the dns info for your domain to your webhosting.

    sounds like whomever installed it for you used a hosts file edit on his computer to install it to that domain on that server.

    I can access the ftp through each of the sub site’s domains. Each ftp links to the same wordpress files and directories.

    Correct. Because there’s only one set of files for all those domains.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘'Network Admin' link doesn't work in v3.2.1’ is closed to new replies.