Upgraded to WP 2.6 and can’t access wp-admin area

The duplication could be a problem.

See these?
NAME = wordpress_d676ec21cf050e966685794aa715694f
PATH = /sitename/wp-admin

NAME = wordpress_d676ec21cf050e966685794aa715694f
PATH = /sitename/

Same cookie name, different values, different paths. Which one gets sent when I access /sitename/wp-admin? Both? If so, which one gets actually used?

I think one of them is the old cookie and the other one is the new cookie. It’s “looping” because the old cookie is still there and not getting erased, but it is getting read.

Clearing cookies fixes that issue, obviously.

to re-use the old cookie name as the admin cookie and then create a new one for the common login is just a bit whacky

I agree, I would have deprecated the old name entirely and used wordpress_admin_hash for the new cookie.

I am suspecting that another release is going to be pending on WP as well for this one. This and the index.php thing… ??

Yeah I had initially posted about the duplication and wondered how the browser could even store two cookies with the same name but then realized they had different paths.

The question is, does the browser send both cookies when at the deepest path? That’s a weird situation.

The upgrade process should have set some kind of flag to nuke the admin cookie on the first login by any admin. Tricky but doable.

ps. my subtitle for this thread is “WP 2.6: I made you a cookie, but I eated it” ??

Otto:

Adding a single line of code to a file is not hard at all, once you finally said that that was what needed to be done. Of course, you didn’t actually say that for, what, a dozen comments, and then told me to do it in a fairly boorish and condescending tone. Real classy.

Plus, what you told me to do didn’t give any information.

I took out the workaround that gave you a tizzy on the blog I upgraded, and I can still log in there.

So I upgraded another blog, and duplicated the problem. Can’t log in. And added echo ADMIN_COOKIE_PATH; to the theme’s functions.php file. And what shows up on my site after adding that is… exactly the same main page that was there before. Nothing different. Nothing at all.

Any more help?

Ok, deleted pretty much the entire wordpress folder, re-uploded everything and tried the upgrade.php again. Told me database was OK and that was the last page I’ve seen. Every page I try to load now returns a blank page, no errors.

If I replace my 2.5.1 will the database still be compatible after the upgrade?

I took out the workaround that gave you a tizzy on the blog I upgraded, and I can still log in there.

Then you can’t help any, because you don’t actually have the problem that the workaround claimed to fix. If you did, then it wouldn’t work anymore.

Also, the reason that line of code didn’t give you any information is because you didn’t do it right or otherwise don’t know what you’re doing. And that’s okay, I understand and accept that. But that was sort of my whole point, I needed somebody *with knowledge* to assist with information.

Basically, there’s more to it than adding a single line of code, but I don’t have the time nor the inclination to teach you PHP so that you can assist. You need to know how to debug a PHP Webpage, basically, and I can’t teach that skill to you via text messages on a forum.

Then you can’t help any, because you don’t actually have the problem that the workaround claimed to fix. If you did, then it wouldn’t work anymore.

Hello, Genius, I replicated the problem on a different blog. As I said, if you’d bothered to read the rest of what I wrote.

Hello, Genius, I replicated the problem on a different blog. As I said, if you’d bothered to read the rest of what I wrote.

No, you didn’t. I really, really do understand what I’m talking about here. I’m not ignoring you, and I’m not just making this shit up as I go along.

There’s two different problems being discussed here. One of which is known and solved by clearing your cookies. The other of which is still unproven and unknown and involves the ADMIN_COOKIE_PATH thing.

The outward results of the two issues will be identical. The cookie path one will probably be more rare.

Oh, and the suggestion to set the ADMIN_COOKIE_PATH to / or /blog or some such thing will, in fact, have the same effect as simply clearing your cookies. Which is why I’m doubting that the ADMIN_COOKIE_PATH thing is a real issue.

Okay, here’s the underlying problem:

1. Upgrading from WordPress 2.5.1 to 2.6 will change the admin cookie path. Instead of being, say, /blog, it will now want to be /blog/wp-admin.
2. When you login for the first time, and it sets the /blog/wp-admin cookie, your older /blog cookie with the same name is still there.
3. This makes the browser send both of them, and WordPress has some kind of chance of picking up the old one instead of the new one.

Most of the time, this won’t matter as they’ll have been the same. In some cases, they’ll be different, and you can’t login because of it, and WordPress can’t reset the old one because it’s using the new path.

Obvious and correct solution: clear the browser cookies. Problem solved instantly.

Less obvious solution: If you set the ADMIN_COOKIE_PATH to the old path, then logging in will overwrite the old cookie with the new one, making them identical again. For a couple weeks, anyway, until your other cookie expires too. Then you might have the same issue.

That’s why I’m dubious about the whole ADMIN_COOKIE_PATH thing. I can’t see any way for it to actually get set incorrectly like _ck_ says he’s experiencing. But I don’t discount the possibility, I just don’t see how it’s possible yet.

Nice of you to edit your response to make it look like you were more helpful than you actually were.

I never said I was a coder. I said I had a problem and I needed it fixed, and instead of helping you were a condescending jerk the whole way through. You told add a line of code and tell you what shows up on the site, and were snotty about how easy it was. I did that. Then you tell me I’m ignorant for not knowing that that wasn’t what you meant. If that wasn’t what you meant, you shouldn’t have said that.

I didn’t ask you to teach me anything, and believe me, you’re such a charming rogue that I’ll never ask you, in particular, for any kind of help again.

Nice of you to edit your response to make it look like you were more helpful than you actually were.

I don’t know what you’re talking about. I think I added a response at the same time you did, but I did not edit anything.

If that wasn’t what you meant, you shouldn’t have said that.

Fair enough, but at the same time, you were and are being awfully snotty yourself.

Here’s the thing. If you could help me, then you would already know how you could do it. Since you don’t, you can’t. Sorry. The line I gave you is, in fact, the only line you need to know. However, you might need to know what it means in order to understand it properly. Like, where the result of it would show up (hint: view source) or where you need to add it (inside the PHP tags) and so forth.

The point is that these are obvious thing for somebody who knows PHP. If you don’t, then I’m sorry, but you can’t help me. I’m trying to debug issues here, not to assist you or make you feel better.

Whoa. Everyone take a deep breath, it’s just blog software.
People contribute in different ways.

Sooo….

Bitching and bickering aside, any word from the
coders/developers of WordPress as to how they
plan on fixing the second issue that the Moderator
above was talking about?

When can we expect a resolution to this issue?
Both technical people and non-technical people
(like myself)

I cleared my cookies and still cannot log into my blog.

Kaufmannn, you can try my workaround. It really won’t harm anything.
The security issue is trivial and debatable.
(in fact it makes it no less secure than 2.5.1)

There will be no resolution until:
a) The fact that it’s actually an issue is verified.
b) The cause is determined.
c) A patch is created for it.

None of these has occurred yet.