Support » Fixing WordPress » Upgraded to WP 2.6 and can’t access wp-admin area

Viewing 15 replies - 76 through 90 (of 191 total)
  • Thanks Otto, and I’ve verified that the siteurl is the same as the url I’m using when trying to log in.

    Well there’s your problem (best mythbusters voice).
    WP tries to set it as /wp-admin when there’s no define.
    (had to hack wp-settings.php to show me what it was doing)

    I now think this is because of legacy installs that have
    $wp->sitecookiepath
    stored in the db.

    So essentially SOME legacy WP installs may HAVE to insert a define.

    WordPress is essentially failing to check for a valid path when calculating the new constant introduced in 2.6 – it’s an oversight I can easily forgive as I might easily make such a mistake myself.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Well there’s your problem (best mythbusters voice).
    WP tries to set it as /wp-admin when there’s no define.
    (had to hack wp-settings.php to show me what it was doing)

    That doesn’t make any sense. What does the SITECOOKIEPATH get set to?

    Look at the code right there:

    define('SITECOOKIEPATH', preg_replace('|https?://[^/]+|i', '', get_option('siteurl') . '/' ) );
    define( 'ADMIN_COOKIE_PATH', SITECOOKIEPATH . 'wp-admin' );

    If your siteurl is http://example.com/blog , then your SITECOOKIEPATH will be /blog and your ADMIN_COOKIE_PATH will be /blog/wp-admin .

    Do you have two entries in the options table for your siteurl or something weird like that?

    I now think this is because of legacy installs that have $wp->sitecookiepath stored in the db.

    What? There is no such thing as $wp->sitecookiepath, and nothing to read anything of the sort out of the database. Those words make no sense.

    WordPress is essentially failing to check for a valid path when calculating the new constant introduced in 2.6 – it’s an oversight I can easily forgive as I might easily make such a mistake myself.

    Again, you’re just stringing random words together in a nonsensical order. If the siteurl is not set correctly, then yes, it will break. But so will the entire rest of the site. The siteurl is critical to everything in the whole of WordPress.

    otto – clearing the browser worked on all my blogs after upgrade.

    thank you.

    I think one solution is that wordpress admin login needs to see that the cookie info being provided is invalid, and null out the cookie.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    otto – clearing the browser worked on all my blogs after upgrade.

    thank you.

    You’re welcome.

    And this is sounding more and more like the REAL problem here. I can see where conflicting cookies would come into play because of differing paths, but if your ADMIN_COOKIE_PATH is getting set wrong, then you have the wrong values somewhere else.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    I think one solution is that wordpress admin login needs to see that the cookie info being provided is invalid, and null out the cookie.

    If the cookie provided is invalid, then it redirects to the wp-login, which doesn’t check cookies before setting them, effectively overwriting them.

    Hi Otto42. Can I help at all?

    I have upgraded to WP 2.6. I can login using IE7 but I can’t login using Firefox 2.0. I have not made any fixes or workarounds.

    I’m not as tech savvy as you guys but I do know how to change code using dreamweaver and upload it to my hosting account.

    Tell me where to look and I’ll tell you what I see. Otherwise, I’ll keep my eyes open for a resolution once you guys are on the same page.

    Thanks.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    I have upgraded to WP 2.6. I can login using IE7 but I can’t login using Firefox 2.0. I have not made any fixes or workarounds.

    I’ll bet a dollar that if you cleared the FF cookies, you could login using it again.

    I think there’s two problems at work here. One is a cookie conflict with previous cookies, which I understand because the admin cookie changed paths but not names.

    The other seems to be some kind of weird siteurl issue, which if true, would prevent logging in to the wp-admin screen no matter what browser you used.

    Otto, the potential is that if the cookiepath doesn’t end up being right, you could end up in a loop where the cookie it is reading isn’t valid, and wp-login clears a different one, with a different path, example. If the code works as you suggest, a single attempt to login would resolve the issue and clear the cookie, no?

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    @rawalex: Yes, but then the fix is easy: clear the cookies manually. Problem solved, no?

    That doesn’t bother me all that much. The problem I’m concerned about is the one ck is talking about, where it’s setting the wrong path to begin with. I can’t quite see how that could happen given the code.

    Thank you Otto42,

    For others who need this in layman’s terms, in Firefox, I went to
    Tools/Options/Privacy/Show Cookies. Then I searched for my blog name and deleted that folder.

    I was then able to get access to my admin panel via Firefox. I also had no problem re-accessing the admin panel after closing Firefox and rebooting my PC.

    If this is any interest to those who want to figure out why the cookies caused problems, I did notice that I had no problem accessing my admin panel via Firefox on a separate PC. My blog’s cookie folder for that PC did not include a utmb nor a utmc cookie. Both of these cookies were in the file I deleted on the computer where I did have problems.

    otto, the “fix is easy” might be for you and me, but for non-technical people for whom running a blog is already a MAJOR technical challege, expecting them to know how to clear cookies (or to know about them beyond chocolate chip or oreos) isn’t right.

    the issue ck is seeing may have to do with different parts of the code using different values, it isn’t just how wp-login treats the cookie, but how other functions read that cookie and how they treat it, because if they don’t do it right, you end up looped back to the login page, no?

    This post is great for all of you technical users, but what about guys who aren’t as technical who are just looking to upgrade to a more secure version of WordPress?

    I have no idea what is going on in this post and all I want to do is be able to log into my wordpress blog.

    I still can’t log in and to make matters worse, there is no “plain english” post or FAQ on how to resolve this issue.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    rawalex: I find it difficult to believe that somebody would not know how to clear their browser’s cookies. It’s a basic operation and there’s detailed instructions online in many places:
    http://www.google.com/search?q=Clear+your+browser+cookies

    The documentation covers it as the very first step in solving this problem:
    http://codex.wordpress.org/Login_Trouble

    And quite frankly, if telling somebody “clear your browser cookies” is not clear enough for them, then they should not be running their own website to start with. If they want a blog, but can’t run a browser (much less a website), then they should farm it out to some other administrative system like http://wordpress.com , to let somebody else handle the actual work and to let them just post on their blog.

    Now, the issue ck is seeing is what I’m trying to work out. However, it has little to do with the cookies if his definitions are getting set incorrectly. It would have more to do with his database or settings in the database.

Viewing 15 replies - 76 through 90 (of 191 total)
  • The topic ‘Upgraded to WP 2.6 and can’t access wp-admin area’ is closed to new replies.