WordPress.org

Ready to get started?Download WordPress

Forums

WP 3.0 Network problems (6 posts)

  1. nspringer
    Member
    Posted 4 years ago #

    I have been working with 3.0 beta 1 on my localhost and a Network of sites with subdirectories is working fine.

    When I try using the Network feature on my production server on run into problems. I set up things the same way and got the Network features added, and created a second site. But when I try to go to the backend or the frontend of the second site in the sub directory I get an "Oops! This link appears to be broken." message.

    Any one else have this problem?

  2. pubwvj
    Member
    Posted 4 years ago #

    Yes. I'm having this problem on one web site set up but not another. I've not yet figured out why.

    The one that works was an installation of WP3.0b1 with MU then enabled. Later I upgraded it to WP3.0b2 manually. That one works.

    The one that does not work I created on a different installation of WP3.0b2 from scratch using the same files I used to upgrade the one that works above.

    I went through the same exact process of configuration very carefully - I had taken notes the first time. Two differences:

    1) The second non-working install is in a subdirectory /blog/ vs the first working install is in the main public_html directory.

    2) The first working install was done as WP3.0b1 and then upgraded whereas the 2nd non-working install was done as WP3.0b2 from scratch.

    I can't see anything else that I did differently.

  3. The second non-working install is in a subdirectory /blog/

    And that is the problem. you can't install it in a folder called /blog/.

  4. pubwvj
    Member
    Posted 4 years ago #

    Well, that makes it easy. I'll reinstall. Thanks.

  5. nspringer
    Member
    Posted 4 years ago #

    I just cleared everything out, reinstalled using 3.0b2, resetup my multisites, and still I get a broken link when I try to visit the backend of a subsite. Any ideas?

  6. nspringer
    Member
    Posted 4 years ago #

    Nevermind, I solved it. It was not a WP 3.0 issue. It was a httpd.conf problem.

Topic Closed

This topic has been closed to new replies.

About this Topic