“WordPress Requires Cookies”, “Username Field Empty”, “Password Field Empty” on

Hi everyone. It is still not happening for me. I have tried removing plug-ins, code out the login errors, commenting out the lines, no joy

Someone posted that it may be CHMOD issue on one of the many files. Has any one had this expereince ?

Why is this so hard, and why me!?

I am concerned that if I get my host provider to clean out my database files (which they seem to not be doing despite me submitting many tickets) that I will lose my no. 1 Google rank for blog “photo restoration blog”.

I so badly want to get this fixed….any suggestions would be most welcome, anything, anyone…

May I join the club? Thank you.
Just got this problem with v2.3.2 on Bluehost (PHP 4.whatever). First it was only one WP installation in subdirectory, others kept working. Then, on trying again, the other installations, including the one in the root directory, got infected as well.
I tried commenting out lines in wp-settings, looked out for whitespace, tried logging in while standing on my left foot and all the other stuff I found googling about.
Nothing worked. HEEEELP!!!

I was getting this same error- but it stemmed from changing where I wanted the index page to live.

I was given a tip to hack into the admin this way:

https://www.village-idiot.org/archives/2007/07/04/wp-emergency-url/

It helped me…

That was a good hint, shakemyday. Although I didn’t employ that script, going into the subdirectory solved it.

My WP installations live in subdirectories/subdomains where they appear under their own top level URL. Why the login all of a sudden doesn’t want to respond to that URL any longer, is a problem, the coding cracks might want to ponder.

I had the same problem. In my case I hadn’t disabled all the plugins first. I renamed the plugins directory, copied the default plugins directory to my server and managed to get in. Now I need to add each plugin back and see which one broke my website.

https://www.nashie.info

What’s really disturbing me about this is the fact that I didn’t shift directories or install funny plugins before the error occurred.

I am now working with an admin area that’s called from a subdirectory. Of course, nice things like the post preview don’t work that way.

Brilliant. Got the cookie error again. This time, the workaround with the subdirectory doesn’t work.

I would also like some help.

URL: https://mukc.leddyonline.com/wp-login.php

Tried various solutions provided so far, the blog was recently cracked but I have upgraded to 2.3.3

I can pretty much guarantee this a plugin issue. I have the same thing happening with the Cookie issue as everyone has described. I am working off a Macbook as my test machine. It was easy to remove the plugins from the directory. As soon as I did I can login just fine.

The plugin was one I am working on. If I find out what causes it I will post back.

I doubt it, husar. On my site the problem appeared out of the blue. I hadn’t changed directories, didn’t install new plugins. The really weird thing is, that the issue frequently pops up and then disappears again.

Had this same problem, and I found the cause, at least for me…

Working on a blog called ‘Worst Of’ for people to write complaints about various local businesses etc, that’s not really important, but I’m currently developing it locally (localhost).

In wp-login.php, the variable COOKIEPATH returns ‘/WorstOf’. But when i go to view the site, if I type in ‘localhost/worstof’ (all lowercase), I get the ‘Cookies not supported error’. If I type in ‘localhost/WorstOf’, it all works perfectly. So, the cookie checks are case sensitive. I would suggest putting a lowercase() around all paths that set cookies, and lowercase() around all checks.

In wp-setting.php, I put a strtolower() around the defines for COOKIEPATH and SITECOOKIEPATH… problem disappeared.

if(!defined(‘COOKIEPATH’))
define(‘COOKIEPATH’, strtolower(preg_replace(‘|https?://[^/]+|i’, ”, get_option(‘home’) . ‘/’ ) ));

if(!defined(‘SITECOOKIEPATH’))
define(‘SITECOOKIEPATH’, strtolower(preg_replace(‘|https?://[^/]+|i’, ”, get_option(‘siteurl’) . ‘/’ ) ));

I’ve hade this error before, and now it turned up again. And I realized why. It’s the WP-ContactForm that causes it in my case. see: https://www.ads-software.com/support/topic/140640

I used a patched version, but I had forgotten about it an just recently updated the plugin. Unfortunately I don’t have a backup of the patched version.

Perhaps this could be the cause for someone else here too.

Hmm, I didn’t see the post referring to this ticket before I posted.
https://trac.www.ads-software.com/ticket/5365

I’m not using the contact form plugin, but the error just occured again after two trouble free weeks.

Perhaps its eddies in the space-time continuum.