Spoke too soon.
jeffbaier, this leaves a huge error message at the top of the page if no one is logged in.
Oh well... starting from scratch again...
Spoke too soon.
jeffbaier, this leaves a huge error message at the top of the page if no one is logged in.
Oh well... starting from scratch again...
Please help me I am totally new to all this downloaded and installed wordpress 2.3.1 followed all instrcutions everything working fine. I try to login and it tells me this cookie error. I check my broser settings tell it to accept all cookies and restart IE 7, I cannot login. Period everytime same error. tried looking for white space after the ?> there is none. I am stuck new installation and just cant login at all.
:(
I meant to follow up to my last post, jeffbaier solution worked perfectly. It wasn't his solution that was causing the error on my site.
Sorry. *sheepish grin*
I recently create several new blogs, with GoDaddy as the host and WP installer. About 2wks ago I upgraded to 2.3.2 and things have been fine. I use the Revolution themes from Brian Gardner for one (JoeMusic.net) and CoffeeSpot for another (www.starbucksters.com). As is usually the case, everything was fine until it wasn't.
I started getting the "ERROR: WordPress requires Cookies but your browser does not support them or they are blocked." for no apparent reason and from reading the posts I'm not sure what to do. The fact that it is happening across several (but not all) of my blogs is odd, as they are all subdomains with their own database and varying themes.
Any help would be appreciated. Thanks
P.S. Additionally, what would cause the presentation to revert back to Classic on its own?! I just went to one of my blogs and it had magically reverted to classic from Revolution.
I just updated to 2.3.3 and I'm still have the same cookie error problem. I've tried many things, but none of them have worked. Many suggestions involve deleting blank lines. I see a lot of blank lines in all my files. I'm sure I don't understand what is meant by a "blank line"
I've tried commenting out the three lines people suggest.
I've tried using Opera, a different computer, and so on.
In addition I have no problem logging in during the daytime, usually, but just no luck early morning or late night. The times seem rather standard (10AM to 10PM I can log in without the error), which makes me think it's related to something on my system, or related to my hosting service (fatcow).
What gives? I'm a bit at the end of my rope.
~alex
akirtland: Give us the URL of your login page and we can tell if you're having the blank line issue.
The general blank line issue is when you have a plugin or theme file or wp-config or some file that is creating a blank line or other whitespace on the output of your webpage.
See, these files are not supposed to produce any output. Due to the way PHP works, if you have a blank line at the end or beginning of a PHP file, it can produce that blank line on the output. The upshot of this is that it will disable the ability for it to send headers to the client, causing cookies and other such stuff to not work. Thus this problem.
Okay, I think I get it now (I am not very technical, so please, forgive.)
The site is www.usablemarkets.com.
Thanks for any help you can offer!
~alex
akirtland,
I see nothing wrong but then I cant go through the entire login process since you have registrations turned off.
I have opened up the registration if you're interested in trying it out.
Again, any help is appreciated.
~alex
alex: No need to open up registration to test this issue.
You do have the blank line problem on the main pages, but not on the wp-login.php page where you login to the system at.
However, you also don't have the cookie problem at all. When I go to wp-login.php and put in fake login information, I don't get the cookie error. I should, if you had a cookie problem. Also, when I go to your site, I can see the Wordpress Test Cookie in my browser. It's working correctly. Any cookie issues you have are in your browser alone.
First, thanks for your help. I appreciate your time.
My issue is that I sometimes see the cookie error, and sometimes do not. Specifically, between 10AM and 10PM (or thereabouts) I have no problem logging in. Outside of that time slot, I get the error.
Obviously this is very strange, and, one would think, specific to my computer. But it sometimes happens to me on other computers. Which leads me to conclude, it must somehow be related to my hosting service.
Anyway, I'm not sure there's an easy resolution.
Again, thanks for any time you spent on this issue.
~alex
Having a problem like that be time related doesn't make any sense. There's something else that must be the differentiating factor.
Unless you have a plugin that does something different between 10am and 10pm, of course. That's possible, I guess.
I have read this post with interest. I have tired everything here also. I installed to 2.3.2 uploaded a blog and everything was fine for a few days. I copied over the security patch file only of 2.3.3 and again everything fine, then BAM! cookie trouble as everyone here is posting. I have tried the commenting out, removing excess space/blank lines etc. and no joy. I am with UK2.Net and am completely prepared to set up again from scratch to get round this problem but I haven't much of a clue about MySQL and they don't have Cpanel to remove/delete my database files. Which seems to be what I have to do to get a complete bug free install ?? Any help would be good. http://www.image-restore.co.uk/blog/ Many thanks
I can't find it, but I read somewhere that deactivating the WP-ContactForm plugin from Ryan Duff will resolve this problem.
Not sure if people still have this problem, but it happened to me and I removed ALL my plugins and it went away.
So now I'm uploading my backed up plugins to see if it will work now.
Hi, mikeo75. How do you remove all the plugins when you cannot log in? Through the back door (File Manager or FTP)?
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:
http://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.
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: http://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: http://wordpress.org/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.
http://trac.wordpress.org/ticket/5365
« Previous 1 2 3 Next »
This topic has been closed to new replies.