Moderator
t-p
(@t-p)
Have you tried:
– deactivating ALL plugins temporarily to see if this resolves the problem. If this works, re-activate them individually (one-by-one) to find the problematic plugin(s). If you can’t get into your admin dashboard, try deactivating via FTP or SFTP or whatever file management application your host provides. If applicable, also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old.
– To rule out any theme-specific issue, try switching to the unedited default, core-bundled Theme (such as Twenty Twelve or Twenty Thirteen) for a moment using the WP dashboard. If you don’t have access to your admin area, you can switch to the default theme by renaming your current theme’s folder in wp-content/themes and adding “-old” to the end of the folder name using via FTP or SFTP or whatever file management application your host provides. Alternately, you can remove other themes except the default theme. That will force your site to use it.
– resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems (because the hooks remain unless plugins completely removed or some plugins stick around in cached files. So by renaming the folder, you break them and force them inactive).
I’m now having exactly the same issues; a site that was working perfectly prior to the update now issues the “Error: Cookies are disabled or…” message whenever *anyone* tries to log on. nothing on the site was changed other than the WP 3.7.1 update; This issue is cross-browser.
I’ve disabled all plugins and switched to a stock twenty twelve theme to no avail. I’ve cleared Cache & cookies on each browser I’ve tried (IE, Firefox, Chrome, Safari…)
Apparently as part of the new update login.php is now issuing a test cookie that is not being properly read on the first pass. If you reenter the username and pw on the error screen, you will be successfully logged in, but far to many users are not giving it a second try…
So, basically, this nifty new update has tanked my – and a great many other users – ability to have people log on to their WordPress sites.
Any ideas how to fix this?
Seeing the same issue here on multiple 3.7.1 sites. Trying to log in a second time works properly.
I’m having exactly the same issues, tried all of the above. http://www.communsense.nl
I have same issue too.
I use 3.7.1 . and I cant login to my site .
I re install 3.7 & 3.6.1 but no thing happened .
Also when some one send a command white page showed .
I really don’t know what should I do . and advise every one don’t upgrade 3.7.1 . I thing this version have big problem .
I agree 100%. I just found my other site won’t log off. I have the white page as well. This is a major problem!
I have the white page as well.
Moderator
t-p
(@t-p)
Have you guys discussed this issue with your respective webhost?
Thread Starter
Kevin
(@kcmquickreport)
It is apparently a login update with WordPress. An “improved” control mechanism during the login process to check if a browser can store cookies. This cookie, however, is only set in the wp-login.php file and in many login scenarios, the cookie is set too late to be of any real use.
Luckily for me, my membership plugin provided an update to work around the issue. As for solving directly, I unfortunately can’t provide much assistance but hope this information helps!
* I use OVH hosting more than 6 month and there is no change in hosting setting . My site worked until last update 3.7.1 .
* I change wordpress : 3.7.1 to 3.7 and 3.61
I remove all plugin folder to deactivate all of them
I used default 2013 & 2012 theme
I change browser too : chrome & IE & fierfox & opera
but none of above solution work to solve this problem .
I have discussed it with my web host. Fairly easy because I am my web host.
While I do apprciate suggestions such as “check with your web host,” please keep in mind that this isn’t an install or plugin issue, but a problem created by the core code being the only thing modified, causing the previously working install to fail.
It’s a matter of us needing to know *what* to talk about to our web host (or ouselves in my own case) in order for us to fix a problem someone else made for us.
I encountered the same issue and have managed to make it work, and a theory of what could be the issue.
First of all, how to get logged in again. Comment out lines 744-746 in wp-login.php . It should look like this:
// if ( isset($_POST['testcookie']) && empty($_COOKIE[TEST_COOKIE]) )
// $user = new WP_Error('test_cookie', __("<strong>ERROR</strong>: Cookies are blocked or not supported by your browser. You must <a href='http://www.google.com/cookies.html'>enable cookies</a> to use WordPress."));
// else
$user = wp_signon('', $secure_cookie);
This will bypass the check entirely and logs you in.
At first I didn’t understand why it might fail, but then I remembered I am running behind a Varnish cache which filters out all but some select cookies. I haven’t checked, but I am fairly certain that my Varnish setup filters out the WordPress test cookie when it receives the login request (the actual POST with the login data). Is it possible all of you are running behind a proxy which filters cookies?
This is pretty sloppy by the WordPress team. They could also just test the session cookie. If THAT one doesn’t get through, it will fail anyway. Completely breaking when a test cookie is missing should not happen.
I hope this helps…
@niosus Thank you very much!
Would it help to use wp-login.php from a previous version? Probably not, because I understand from your post that the real problem is somewhere else in WordPress’s code?
