I have upgraded to 2.3 and cannot login.
I am stuck with the:
ERROR; WordPress requires Cookies but your browser does not support them or they are blocked
message in the login box. I have tried:
1. Assuming it was a bad password and phpMyAdmin edited the Amin account using an MD5 generator to change my password.
3. Emptied my browsers satchel, brief case, lunch box, cache, settings
4. Tried two other browsers, also reset them
5. Tried a download of the .ZIP instead of the UX flavour-compress in case one was snapped.
6. Followed the instructions for deleting all my WP (NOT just over-writing as per the initial install), then re-uploaded all fresh shiny 2.3
8. Swearing at my keyboard
All stubbornly leave me with:
ERROR; WordPress requires Cookies but your browser does not support them or they are blocked.
This is VERY soon after 2.3 went live so I know I may not get a reply right away, but, if there is some kind soul who knows that this is, pretty plesase, can you reply?
I am 100% stuck.
PS, this support request is like this thread:
but that one says it’s not a support request, which is why I posted this.
THANK you in advance whoever you turn out to be =:-)
alanfluff, this patch might help. Can you try adding that line to a fresh version of wp-login.php?
Here, try this copy of wp-login.php that includes the patch.
Ryan, the patched file didn’t work for me. Firefox is giving me this error message: “Firefox has detected that the server is redirecting the request for this address in a way that will never complete.” I never get to see the live WP page, though the Admin stuff works fine.
+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.
Ryan – at first I thought it was my new security software, but that patch has sorted this problem a treat!
+ryan – just read the bugtrac – yes my install IS in a sub dir not the root of my domain.
The patched file did not work for me either. I have Zone Alarm for my firewall, but I’m quite sure (at least, I think) this isn’t the problem, since it’s never caused me problems with previous versions of WordPress, and I’ve ensured that cookies are accepted by my site. Everything was working fine until I upgraded this morning.
I also tried commenting out lines 24, 313 and 314 for my original wp-login.php file. That didn’t work either.
My db name does not use the “wp” prefix … would that cause any problems? Any other suggestions?
Scratch my previous post. Seems to be working now. If I encounter more errors I will let you know.
So we’re still with the commenting out of 24, 313, and 314? Because that works. I have no idea of any ill effect.
nope… patch did not worked for me either 🙁 … I don’t know what to do…
Ryan thank you. using the patched copy of wp-login.php you supplied above has fixed the problem.
I have the same problem to report.
I am also installed in a sub-directory.
Upgraded to 2.3 was fine until I logged out and deleted all my cookies on my main machine, then was not able to login in FF or IE
My laptop, which still has older cookies could always login to my blog!
I am gutted that wordpress team have issued such a buggy upgrade – 2.3 has been a nightmare for me so far. 🙁 I think there are issues with being installed in a subdirectory.
+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.
I’m having the exact same problem. Cleared cache, cookies, etc. Using IE7 and latest FireFox. I also have it installed in it’s own directory.
I’m not as tech savvy as everyone else….do I just upload the patch to my server, or do I have to do anything else with it?
- The topic ‘Can’t login after upgrade to 2.3 ERROR; WordPress requires Cookies but …’ is closed to new replies.