alfjmrodrigues

@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]

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

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

@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

@cam here goes in a video my installation:

@cam I did exactly as you told, and no success.
As this was a fresh installation, I had to create the mu-plugins folder and to create the cookie-fix.php file inside that folder.

Did that on the local machine, uploaded it to the server, refreshed the page were I was testing the login on my site, and again, the same error…

Basically I did a fresh installation of WordPress 3.7.1, on a new domain, and I get this cookies error, all the time (tried to login not 2, but 10 times, with no success).

Any ideas, please?
Cheers
Alfredo

Cam, where exactly did you put your code?…