Support » Fixing WordPress » Upgraded to 2.6. Now I can’t log in.

Viewing 15 replies - 1 through 15 (of 18 total)
  • Some tips and trick here.

    Thread Starter dioni

    (@dioni)

    I tried that. I’m guessing this has nothing to do with the database. I think there’s a pipeline error somewhere.

    Thread Starter dioni

    (@dioni)

    What does it mean when it says “Please log in again.” ???
    If my password is wrong it will say incorrect password. But it doesn’t say that.
    Argh this is frustrating! What should I do??!

    Thread Starter dioni

    (@dioni)

    Okay I just found out one thing. I CAN log in with IE, but NOT FIREFOX.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Clear your cookies in Firefox. Then close and restart the browser. Then you’ll be able to log in again.

    Tools->Clear Private Data.

    I cannot log into my admin page no matter which browser I use. This just suddenly started happening. Everything was fine then I was suddenly asked to log in again and now just keep getting stuck in a “please log in again” loop. Have cleared cookies repeatedly. Have upgraded. Have tried Firefox, Camino, and IE. Does anybody have any other advice? I am supposed to host a blog carnival tomorrow and can’t even get into my own blog!!

    I’m having the same problem. Firefox and Safari.
    I’m locked out.
    When I request a new password I get an email but the blog says the key is invalid.
    help!

    I add myself to the list. Same issue. No matter what browser I use. I go to the login, I login successfully but get stuck on the login screen. If I browse back to the main site I have the link Site Admin, but when I click on it I end up at the login screen again. No error on login, simply bounces back and acts like I am logged in successfully.
    This started with the upgrade to 2.6.2

    Could really use some help with this guys!

    Just wanted to clarify things. It has NOTHING to do with the browser, cash or cookies. I tried on multiple computers. One with a fresh OS install that was never at the site (first site that was visited with the browser was my site that has the issues). So this is not a browser issue.

    There is a BUG for sure with 2.6.2. Now we need to find out why.

    One thing to try:

    Use the wp-config.php that came with 2.6.2 and just enter your info in it and generate and add your custom keys. wp-config.php has changed with the last few versions of WordPress, so just reusing your old one is not a good idea.

    Thanks for that iridiax. I tried that. But I have complicated things even more now. I now have a second install of WordPress. I just about had a heart attack when I saw the default install and nothing in it.

    Reverting back to the old wp-config.php gave me back the original content.

    Here is how they look like. What else would I need to edit?

    Original pre-upgrade:

    <?php
    /** WordPress’s config file **/
    /** http://wordpress.org/ **/

    // ** MySQL settings ** //
    define(‘DB_NAME’, ‘gofishcch’); // The name of the database
    define(‘DB_USER’, ‘gofishcch’); // Your MySQL username
    define(‘DB_PASSWORD’, ‘**********’); // …and password
    define(‘DB_HOST’, ‘mysql.gofishcch.com’); // …and the server MySQL is running on

    define(‘AUTH_KEY’, ‘put your unique phrase here’); define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’); define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’);
    define(’FORCE_SSL_ADMIN’, true); define(’FORCE_SSL_LOGIN’, true);

    // Change the prefix if you want to have multiple blogs in a single database.

    $table_prefix = ‘wp_4vdwbd_’; // example: ‘wp_’ or ‘b2’ or ‘mylogin_’

    // Change this to localize WordPress. A corresponding MO file for the
    // chosen language must be installed to wp-includes/languages.
    // For example, install de.mo to wp-includes/languages and set WPLANG to ‘de’
    // to enable German language support.
    define (‘WPLANG’, ”);

    /* Stop editing */

    $server = DB_HOST;
    $loginsql = DB_USER;
    $passsql = DB_PASSWORD;
    $base = DB_NAME;

    define(‘ABSPATH’, dirname(__FILE__).’/’);

    // Get everything else
    require_once(ABSPATH.’wp-settings.php’);
    ?>

    New Version:

    <?php
    // ** MySQL settings ** //
    define(‘DB_NAME’, ‘gofishcch’); // The name of the database
    define(‘DB_USER’, ‘gofishcch’); // Your MySQL username
    define(‘DB_PASSWORD’, ‘**********’); // …and password
    define(‘DB_HOST’, ‘mysql.gofishcch.com’); // 99% chance you won’t need to change this value
    define(‘DB_CHARSET’, ‘utf8’);
    define(‘DB_COLLATE’, ”);

    // Change each KEY to a different unique phrase. You won’t have to remember the phrases later,
    // so make them long and complicated. You can visit http://api.wordpress.org/secret-key/1.1/
    // to get keys generated for you, or just make something up. Each key should have a different phrase.
    define(‘AUTH_KEY’, ‘jesus’); // Change this to a unique phrase.
    define(‘SECURE_AUTH_KEY’, ‘jesus’); // Change this to a unique phrase.
    define(‘LOGGED_IN_KEY’, ‘jesus’); // Change this to a unique phrase.

    // You can have multiple installations in one database if you give each a unique prefix
    $table_prefix = ‘wp_’; // Only numbers, letters, and underscores please!

    // Change this to localize WordPress. A corresponding MO file for the
    // chosen language must be installed to wp-content/languages.
    // For example, install de.mo to wp-content/languages and set WPLANG to ‘de’
    // to enable German language support.
    define (‘WPLANG’, ”);

    /* That’s all, stop editing! Happy blogging. */

    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
    require_once(ABSPATH . ‘wp-settings.php’);

    Help would be very much appreciated

    $table_prefix = ‘wp_4vdwbd_‘;
    vs.
    $table_prefix = ‘wp_‘;

    with the second one of course you got a new install. You should have preserved the same table prefix to connect to your old, existing blog!

    Yup, that was the reason I didn’t see the site as it should have been. Thanks for pointing that out.

    The problem persists even after making the change.

    In the worst case, Klaqua (backup first !), you can reset your password with phpmyadmin, that is documented in the WP documentation base…

    Sadly, I find myself in klaqua’s situation, too: after a bit of history 🙁

    I even resorted to using emergency.php to see if I’d screwed up the passwords or whatever but it’s not that. I’ve also checked different browsers on different machines and it’s not that. I’ve also re-installed WordPress in case a file had been corrupted and it’s not that! I really could do with making a post soon…

    sabinou – I don’t think the issue is that the passwords aren’t right; it seems to be that “the system” is simply sending me back to the login page. (If I deliberately enter a wrong password I get told so)

    Simon

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Upgraded to 2.6. Now I can’t log in.’ is closed to new replies.