alanfluff

Looks like 2.3.1 will permanently fix the login problem (the reason I opened this thread). Yay! – Thanks WP people =:-)

@hellioness – If this patch has not yet been applied to the off-the-shelf WP 2.3, then I am sure there is a good reason, but I get your point and agree, if it has not been applied, then it ought to at least be shown as needed in a way others downloading 2.3 for the first time would see and understand.

@zmirza – Sorry you are stuck – my comment, further up this page, starting “@kkemenczy – My understanding is the patch fixes a test…” explains what this patch/thread is addressing – sorry it’s not fixed your problem.

@miskolino – I believe 2.3 has an extra ‘check-we-have-cookie-support’ test built in (cool), but the test breaks if WP is not installed in the root. The patch fixes this or removes this extra test – not sure which. Sorry if this no help – I don’t know much more myself. Good luck.

@kkemenczy – My understanding is the patch fixes a test for cookie support. If you are logging in, then I am guessing that this patch or the lack of it is not the problem. I think you need cookies to log in at all. Did you run the upgrade.php – don’t ask me how – it’s explained properly on this site and I might make a mistake – guessing you did already, just suggesting in case. Good luck

+stuffwhy – I think the patch (scroll up) is an fix for a bug whereas the ’24, 313, and 314′ just side steps the problem. I believe this cookie-testing-code was there to help everyone by warning if cookies were not working so they would not have problems later when cookies are required. So, if you have cookie support (like most I would hazard to say) then the test while useful, would not matter, whether it was present or not.

+ryan – just read the bugtrac – yes my install IS in a sub dir not the root of my domain.

+ryan – Works a treat with the copy of wp-login.php that includes the patch. Tried on both Firefox and Safari, AOK with both. Excellent.

+miskolino – I get a 100% normal login page, just constantly whines about cookies, perhaps your problem is different to mine? (not that that observation helps any – just wanted to clarify).

+ryan – Happy to:

Mac OS X 10.4.10

Browsers: Firefox 2.0.07, Safari 2.0.4 (419.3) and Camino 2007050909 (1.5)

Firewall (Mac) turned off or on, same.

LittleSnitch, turned off on on, same.

Don’t know how to tell my HTTP server version and a quick Google failed to tell me – if it helps, it’s the same server that I have used for WP for a long time and was AOK wiht WP2.2

Cheers and thanks for opening a ticket.

+Frischkopp – Yeah! Thanks, this solved my login problem too – but this is a hack (no shame in that of course) and so I won’t close this thread since I am hoping there is a solution lurking out there.

+MichaelH – Sorry for being thick: a)Is this directed at me (I should respond to Westi) and b)I am not sure how to do that if it is me. But thanks for the link.

It seems (my low-quality guess) that some Cookie testing code had been added and perhaps it is broken? Incisive eh?

If this can be commented out, for now, then yay!

No. None. It’s a Mac.

I tried turning off the Firewall.

I tried turning off LittleSnitch.

No change.

Thanks for the suggestion tho’.

Phew! Not just me who is getting this then?

I have upgraded from 2.2(I think) to 2.3 full release and I CANNOT login. I get: “WordPress requires Cookies but your browser does not support them or they are blocked”

I have tried following the help for phpMyAdmin hacking the password using an MD5 generator and about anything else I can find in the help / support.

Hoping this thread is going to be posted with a golden nugget that will explain this as right now, I am 100% stuck.

Thanks, I suspected this might be the case but didn’t want miss out if it was written up somewhere and I missed it.