Cookie Error when Logging In

@cam sorry, no double coding. You may consider yourself officially stumped. Same goes for me. I applied the same patches to my other install, https://www.willemdboer.org. Same result there. The blank screen.
The gmail.css mystery is cleared as well. It is a Chrome extension and disabling makes the blank screen stop one step earlier ??
I just don’t know what else to try. If I can’t get into the admin screen I am in serious trouble. I don’t think reinstalling is going to be of help either, looking at MariaA’s post ……
Where are the WordPress guys in all of this?

2willem.deboer I have read all posts several times and tried every suggestions – several times ;). But the best I can get is a white page.
I am not s? familier with scripts, maybe I doing something wrong. My page is https://www.medisinsk-yoga-oslo.no, maybe somebody can take a look?

I just want to have it easy, thats all, but I even cant get into it. Have this problem two week now. So where is Wp guys, oppgrading? fix it easy way?

@cam, @willem, @Amstor and the rest of the tribe, You are ALL AWESOME!
Thanks a bunch for all the suggestions you made, as that shows a very high standard on the consideration arena.

So, replying to your questions/suggestions:
I have used Chrome and Firefox, with no luck.

My cookies are enabled on both Browsers, that’s for sure, and nothing works with 3.7.1.

I have an IPAD (with cookies ENABLED) which has the same problem with the 3.7.1 version.

I tried to download version 3.7, get the wp-login.php and apply it to my 3.7.1 installation, with no luck again.

Yesterday I have been trying to have this problem solved, and it took me around 3 hours to just give up and go to bed.

Today I decided to start from scratch, and so, I completely erased my installation, and installed version 3.7, ET VOILA! It worked like a charm!

So, my dearest friends, 3.7.1 has definitely a problem, and I will not take anymore time to understand what is it.

Lessons learned:
I WILL NOT upgrade to 3.7.1, and will only upgrade to the next version, AFTER reading the comments on forums like this and be assured I will not get stuck.

Wish you all the best of lucks and if I discover something about this I will post it here, as a comment.

Love you all!
Alfredo Rodrigues

Guys, just a final note:

WordPress just decided to automatically upgrade my 3.7 installation to 3.7.1, and…

IT′S WORKING ??

Well, let′s cross the fingers…

Cheers
AR

@alfjmrodrigues It has worked for me too from the beginning with the exception of the CNAME issue which I fixed with the .htaccess redirect. I also upgraded from a prior version and did not do a fresh 3.7.1 install.

You may still run into issues with that if you try to login from the opposite CNAME (www or non-www) from that set in your settings. That is why I recommend the .htaccess redirect to whichever CNAME you’re using so it doesn’t happen.

Lovely, Amsgator!

Implemented as the master suggested ??

Can you do your hacking to see if was well implemented?
(I removed the ‘<?php’ and ‘?>’ as it were already on the functions.php file)

Cheers
AR

@alfjmrodrigues: I cant find any 3.7 just 3.7.1.

Anybody took contact with WP team and rapport this problem?

@mariaa Here are the archive downloads https://www.ads-software.com/download/release-archive/

@alfjmrodrigues I deleted the hack from the forum when I saw you were able to update. Regardless, it’s a good idea to hide those files and hide the version number. I’ll re-add the code for those who want it.

It looks like the blocking worked, when I try to access https://www.maiscashback.com/readme.html (and the others) it gives a 403 error so that’s good.

# BEGIN Deny Access to Certain Files
	<FilesMatch "readme.html|license.txt|wp-config-sample.php">
	Order allow,deny
	Deny from all
	</FilesMatch>
# END Deny Access to Certain Files

The generator tag is also removed from your page source, so it looks like you’re good.

Add this to the functions.php file to remove the wordpress version from source code.

# Remove WordPress Version
	function remove_wp_version() { return ''; }
	add_filter('the_generator', 'remove_wp_version');

# Remove Version Query Strings From JavaScript JS and CSS Stylesheet Files
function _remove_script_version( $src ){
	    $parts = explode( '?', $src );
	    return $parts[0];
	}
	add_filter( 'script_loader_src', '_remove_script_version', 15, 1 );
	add_filter( 'style_loader_src', '_remove_script_version', 15, 1 );

@amsgator, I already had inserted the last portion of code to the beginning of the functions.php:

<?php
/**
 * Twenty Twelve functions and definitions
 *
 * Sets up the theme and provides some helper functions, which are used
 * in the theme as custom template tags. Others are attached to action and
 * filter hooks in WordPress to change core functionality.
 *
 * When using a child theme (see https://codex.www.ads-software.com/Theme_Development and
 * https://codex.www.ads-software.com/Child_Themes), you can override certain functions
 * (those wrapped in a function_exists() call) by defining them first in your child theme's
 * functions.php file. The child theme's functions.php file is included before the parent
 * theme's file, so the child theme functions would be used.
 *
 * Functions that are not pluggable (not wrapped in function_exists()) are instead attached
 * to a filter or action hook.
 *
 * For more information on hooks, actions, and filters, @link https://codex.www.ads-software.com/Plugin_API
 *
 * @package WordPress
 * @subpackage Twenty_Twelve
 * @since Twenty Twelve 1.0
 */
# Remove WordPress Version
	function remove_wp_version() { return ''; }
	add_filter('the_generator', 'remove_wp_version');

# Remove Version Query Strings From JavaScript JS and CSS Stylesheet Files
function _remove_script_version( $src ){
	    $parts = explode( '?', $src );
	    return $parts[0];
	}
	add_filter( 'script_loader_src', '_remove_script_version', 15, 1 );
	add_filter( 'style_loader_src', '_remove_script_version', 15, 1 );

// Set up the content width value based on the theme's design and stylesheet.
if ( ! isset( $content_width ) )
	$content_width = 625;

I did that to both twentytwelve and twentythirteen

What did I do wrong?
[Use backticks or code button while posting code]

You didn’t. I was just adding it back for others, sorry for the confusion. When I view your page source the generator tag and version is gone, so it worked.

It only has to be added to the theme you have active.

Anyone who still needs help with this issue, I’d suggest starting your own thread per:

https://codex.www.ads-software.com/Forum_Welcome#Where_To_Post

When a thread gets this long, it gets quite unwieldy and difficult to tell who still needs help.

For those who are following (or who stumble upon) this thread.

The first hack (commenting out lines in wp-login.php) is likely to cause a blank white screen if there are legitimate cookie issues with your browser. This stops wp-login.php from checking to see if cookies are enabled and just tries it. If there aren’t the cookies set, then white screen and no explanation.

The function @mirajas and I suggest (do one or the other) simply adds setting the test cookie whenever someone visits any page of the site, so it has more opportunity to get set, and therefore when logging in, it is less likely to flag the error message when it shouldn’t.

I have not tried installing a clean copy of 3.7.1 to know if it has issues. My installs have all been updated (either automatically or manually) to 3.7.1 on each release dating back to pre-3.6.

It sounds like there may be a problem with fresh installs of 3.7.1, but this is outside the scope of what the OP (@Kevin) was asking about. He could log in on the second or third attempt, but received the cookie error on the first. This was the case in my installation, except for me, the error was limited to only iOS browsers.

As @wpyogi said, if you are still having a problem with this or a new issue, it would make sense to start a new thread.

I have a similar problem except I’m running 3.7 and this problem popped up out of the blue on a blog that’s been running for years. I’ve been trying the stuff you guys are suggesting here (thanks @cam, @amsgator for the stream of suggestions ?? but nothing seems to work.

I started my own thread yesterday.
https://www.ads-software.com/support/topic/cant-login-error-cookies-are-blocked?replies=3
Unfortunately not getting much help there at all!! I’ve been working on this for days. Nothing seems to be working. Hope someone comes up with something that works for everyone who’s having this problem.

Well, it was not any answer on my own tread. So I wil probably wait to 3.7.2 og 3.8. Hope it comes soon.
Or go for another edtitor.

Same here. No answer to my own thread either ?? I detect little sense of urgency from the WordPress people which is very disappointing.