1.2.1 error: can’t log in

  • I have installed 1.2.1 in parallel with the current 1.2 version on my site, so that I could check it and customize it first, before switching for good.
    I changed what needed to be changed, and got the main page to display properly; I then tried to log in and could not: I kept getting an error message “Error: Incorrect password.” I tried to get the system to email me the password, and got two messages; one saying:
    Login:
    Password: 34f929
    Login at: https://xxxxx/wordpress-1.2.1/wp-login.php
    (note the empty “Login”)
    the other message arrived a few seconds later and contained only this line:
    Password Lost and Changed for user:
    (again, no user name; I assume I’m getting this one because I’m the system administrator)
    I tried the password (and repeated the attempt several times) to no avail.
    I then tried to log in to the 1.2 installation, which had been working fine, and it now was broken as well: not only I could not log in and got the same defective emails when I tried to get the password, but I also noticed that version 1.2 was now under the impression that it was 1.2.1 and used URLs associated with the 1.2.1 directory.
    Investigation of the database with phpMyAdmin showed that the filed “siteurl” in table “wp_options” had been changed to what it would become under 1.2.1, i.e. https://xxxxx/wordpress-1.2.1
    I changed it back manually to 1.2 but that made no difference, I still cannot log in and whenever I try to log in through 1.2.1 it changes siteurl to point to itself.
    What do I do now?
    Pierre

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

  • Hm. I updated, then tried to log in just for kicks, and was emailed some Base 64 code.
    Luckily, I took full notes on my install:
    => Password email bug in 1.2:
    wp-login.php
    https://www.ads-software.com/support/6/6486

    Hm. It looks like the fixed code is already in wp-login.php, but that does not help you. Sorry. I’ll have a look around to see if I can come up with anything.

    Hm. It looks like the fixed code is already in wp-login.php, but that does not help you. Sorry. I’ll have a look around to see if I can come up with anything.
    Okay: this should help:
    https://www.ads-software.com/support/3/14234

    Hm. I’ve now restored my backup, and then uploaded only the pages specified on the linked-to page, and can’t log in. I think I’ll wait.

    Thread Starter araneo

    (@araneo)

    I am in the process of walking through wp-login.php.
    So far, everything looks OK, and I have ascertained that the passwords stored in the database are the correct md5 hashes of the original passwords for all the users and the admin. Whatever the problem is, it’s not that.

    You installed ‘in parallel’ – does each install share the same table ?

    Thread Starter araneo

    (@araneo)

    > You installed ‘in parallel’ – does each install share the same table?
    Yes, they do. Or they should. Obviously something isn’t right, since the login script for 1.2.1 writes in its base directory in “siteurl”.
    But even after I fixed that back to 1.2, the login from the original 1.2 installation (nothing changed, worked perfectly less than an hour before the 1.2.1 test) is still not working.
    I have walked through the entire wp-login.php and found that the problem is NOT there: the script authenticates the login properly and hands off the followup to the normal redirect …./wp-admin/post.php via the header function at line 132: header(“Location: $location”);
    Then, something inside /wp-admin/post.php bumps me right back to wp-login.php with the following URL (broken for clarity):
    …./Blog/wordpress-1.2/wp-login.php?redirect_to=%2F
    Blog%2Fwordpress-1.2%2Fwp-admin%2Fpost.php
    I am now tracing post.php …

    Thread Starter araneo

    (@araneo)

    > I am now tracing post.php …
    And the error seems to take place in auth.php.
    Somehow, the authentication cookie is stored with one path information (which turns out to be a logical link to the actual directory) while the script that uses auth.php appears to attempt to retrieve it using the path stored in “siteurl”, which is different until I commit the upgrade. The result is that it is impossible to test a new installation in parallel with an existing one. That’s not good for something so highly customizable.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘1.2.1 error: can’t log in’ is closed to new replies.