The MU forums have moved to WordPress.org

Fatal Error and Mod_rewrite problem (8 posts)

  1. macgruder
    Member
    Posted 18 years ago #

    Running Apache 2, PHP5, MySQL4.1. Non-Virtual hosts.

    1. When I try to logout, I get this error:
    Fatal Error
    Could Not Find Blog!
    Searched for mu/ in wordpress_mu::wp_blogs table. Is that right?

    2.
    A link to
    http://foobar.com/bob
    redirects to
    http://foobar.com//bob
    and then gives an error such as the above. The mod_rewrite rule seems to be slightly wrong for catchalls.

    Otherwise it seems great.

  2. TomK32
    Member
    Posted 18 years ago #

    blog creation for subdirs is kind of buggy i had to recognize. a patch is pending at donncha but you can edit the database directy if you want to get the created blog working now.

    for the htaccess, maybe you want to look at mine http://tomk32.de/tmp/wpmu-htaccess

  3. macgruder
    Member
    Posted 18 years ago #

    I tried your htaccess, and moved the files from wp-install to the root directory (this is also required I assume). I made a couple of changes to your htaccess file above:

    This line seems to be missing a slash:
    RewriteRule ^([_0-9a-zA-Z-]+)/wp-admin(.*) /wp-admin/$2 [L]

    and although I didn't get an error the logout didn't seem to actually do anything. Also, in both layouts the import button just redirects you somewhere.

    I can tell though that you're working hard to get this really great system working perfectly :-)

    I'm wondering too why there is the requirement to log in at a particular page. I'm thinking that it would be much more intuitive for members to be able to log in on any login link, and for the system to be able to detect what your 'permissions' are for a particular blog, and display a logout link or admin link accordingly.

    At the moment for bob to login to his page 'bob', he may go to
    http://mu/bob/wp-login.php
    whereas
    http://mu/wp-login.php

    Is this a 'bug' with subdirs or the intended behaviour? I'm thinking that if it is the intended behaviour then it may be very confusing for users. Most people would expect to be able to click any login button wherever it is and just login.

  4. macgruder
    Member
    Posted 18 years ago #

    "whereas
    http://mu/wp-login.php"
    should read
    "whereas
    http://mu/wp-login.php
    gives a login error"

  5. TomK32
    Member
    Posted 18 years ago #

    about the non-working logout, try a forced reload. maybe cache is playing tricks on you.

    single login for the whole community is definitly on my whishlist. but I don't know what's already there and what donncha is working at.
    I'm only into it for a few days now and try to spam donncha with my patches as good as I can ;-)

  6. macgruder
    Member
    Posted 18 years ago #

    Cool!

    "single login for the whole community is definitly on my wishlist"

    Frankly, I think this is essential. There is no way that many users will be aware of this constraint. After, signing up admins will be inundated with emails saying, "Why is my password rejected", or they'll simply have people give up and sign up to another site. Logging in must be transparent and simple.

  7. TomK32
    Member
    Posted 18 years ago #

    not only single login for a community but for serveral communities. can't remember it's name but sites like blogger.de are already coperating with others.

    Maybe someone is willing to write plugins for that?

  8. kahless
    Member
    Posted 18 years ago #

    I am still having the logout problem with the 2005-9-28 nightly. I am running Apache 1.3.33, PHP 5.0.4, and MySQL 4.1.14 with non Virtual Hosts. When I try to access the htaccess file above I am prompted for a user name and password which is not my login for the forums. What steps do I need to take to fix this problem? Thanks for the help.

About this Topic

  • Started 18 years ago by macgruder
  • Latest reply from kahless