I have developed several custom themes for WordPress using Mamp, Phpmyadmin and Dreamweaver on a Mac and until now I have never had any problems. I started working on a new site yesterday and noticed the wordpress 3.8 update. I updated the site I was working on and several others at the same time. Everything seemed fine until I went to log in today and I get this error:
Cookies are blocked or not supported by your browser
Cookies are enabled and I have tried it in several different browsers but the same thing happens. I have tried commenting out lines 744 to 746 in the wp-login file containing the if else statement about testcookies but I just get a blank white screen after logging in.
The wierdest thing is that only some of my sites are effected whilst others are fine. I have tried all day to figure this out but I am totally stumped. Any help would be really appreciated.
Update on problem:
I have just uploaded the same theme to a live domain and updated to WordPress 3.8 and the login seems to be working fine there. It just gives me the cookies error when I use exactly the same files on my localhost testing server????
I am not a developer but the same thing happened to me. Did you ever find a way around it? How can I solve this? Please let me know via this thread or email mae.gale [at] gmail.com
I’ve tried clearing my cookies and enabling them and still nothing. PLEASE HELP!
I’m afraid I didn’t find a solution, I have just been developing the sites live and not using MAMP.
Are you using a testing server or can you just not log in to your wordpress site?
I’m experiencing the same problem too – but only on my localhost, on my server i can still login
I just tried using clean version of WP 3.8,
took the wp-login.php file and replaced my sites wp-login.php with it and that did it for me, not sure why. Something to do with the way my cache and security plug ins had written to it I think?
I had moved servers, from one Plesk VPS to another using the Plesk migration tool, there must be something slightly different between the 2 environments in some way ( the IP for starters ), and it set off the security alarm bells…possibly….
anyway it solved the issue…
I am using WP 3.8
I created my website at a localhost. Now I moved it to a live host.
Just found that I can not login anymore. My login page just refreshes giving me no error. The solution of changing password does not at all. I tried the obvious solution of “lost your password?” but I do not receive any email. I changed password via phpMyAdmin but it still refuses to login. I tried the emergency.php script too. This time I received the email saying that the password had been changed (in fact I kept the same) but it did not work either.
I replaced wp-login.php by a fresh one. It did not result.
I renamed the wp-content/plugins as wp-content/1.plugins and created an empty wp-content/plugins as suggested for an older WP version (a 5 year old post on a similar problem). It did not result.
I think this is not a password problem.
Exactly the same problem here 🙁
Tried everything I could find anywhere about this problem, nothing works.
Only got from error to blank page.
Could it be a MAMP thing? I use the regular version, not Pro
I am relatively new at WordPress (all of this coding stuff),
but if I cant login, how can I ever learn :-s
I just solved my problem.
The trouble was caused by the plugins.
I followed a thread posted some time (years?) ago, which suggested to rename (through ftp or ssh) the wp-content\plugins\ directory as wp-content\pluginss\.
This way the plugins were desactivated and I was able to login.
after I logged in, and while I was logged in, I renamed back the directory, i.e. from wp-content\pluginss into wp-content\plugins, and I reactivated the plugins one by one in the WP dashboard. It was also necessary to activate the header image as for some reason this had also been desactivated (and this was preventing an easy edition of the pages).
Now everything is working just fine.
Nevertheless a question remains: why did this happen?
I just updated to 3.8 today, tried to solve a sidebar issue with Twitter Widget Pro not appearing, and now my website is crashed and I cannot login to correct it either.
Glad to see it is not just me, and I hope this reassurance helps others in some way – but not being able to even login to try the above solution is crushingly disempowering.
If anyone figures this out, I will be very grateful.
I just got a great tip from WPRanger, who wrote,
“You need to visit your site using FTP, download the functions.php file, correct the error and re-upload.
You may have to activate PHP on your hosting account to do so.”
I did what he recommended and also found this website very useful for digging up the lost PHP file I needed, and hope it can help others too:
I hope that’s helpful, Neal
I am getting an error 500 message and it is not allowing me to access the login screen. What do I do? Thanks!
To get the site back up and running without any errors, It was first restored to a previous backup and then had a line added to the wp-config.php “@ini_set(‘display_errors’, 0);” to stop the error line from appearing at the top of the webpage.
I have been reading similar threads for THREE straight days now, and I have found no resolution.
Here’s the breakdown of my (similar) situation:
– Running latest (free version) MAMP on Mac OSX Mavericks
– Using newest WordPress 3.8 download
– I’ll install the WP 3.8 onto my localhost no problem — and sign in with no problem!
– BUT, as soon as I shut down my computer and/or MAMP servers, and bring everything up and running again, I get the same old error on lines 749 – 753 of wp-login.php:
“Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.”
– I have repeated this three installations, it happens every time.
I’m using Chrome and cookies are enabled.
I clear the cache, clear the cookies, and the problem persists.
Will wp.org address this please? It seems unresolved as far as local installations of WP-3.8 are concerned.
- The topic ‘Can't log in to wp-admin after updating to wordpress 3.8 – Cookies error’ is closed to new replies.