• Hi All,

    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.

    Many Thanks

Viewing 10 replies - 16 through 25 (of 25 total)
  • @jameshurst, the issue is most likely not wp3.8, but more likely the server setup concerning MAMP localhost. There are a lot of possibilities when dealing with a localhost considering we are all using our personal computer. That fact alone bring in unlimited possible side effects.

    Your cookies could be getting scrambled by a conflict between any of the following: php version, ports or document root. I’m not 100% on what kind of conflict, just spitballing here.

    <u>My setup</u>
    Ports:

    • Apache: 8888
    • MySql: 8889

    PHP v5.4.4
    Document Root: MAMP/Preferences/Apache

    As far as I know my setup is the default setup. When I downloaded and setup MAMP I changed nothing in the preferences. The only issues I’ve had have been related to file permissions and I don’t think that is the case here.

    Is that not a strange root?
    Mine says:

    PHP v.5.5.3 (cache –)
    Doc Root: /Applications/MAMP/htdocs

    Or could that be the error?

    Yeah, not sure what the heck that doc root was or why I wrote that, maybe it was late at night…

    Document Root: /Applications/MAMP/htdocs

    LOL

    Still no solution ??

    I did find that one of my friends has some white space after the closing php tag in their functions.php. Also turn on WP_DEBUG from the wp-config.php on line 81 by setting it to true.

    <?php
    // my code goes here
    ?>

    I did not find any white spaces but did change false into true.
    Now I get the following massages trying to log on….
    (cookie errror remaines the same)

    Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /Applications/MAMP/htdocs/wordpress/wp-includes/wp-db.php on line 1142

    Warning: Cannot modify header information – headers already sent by (output started at /Applications/MAMP/htdocs/wordpress/wp-includes/wp-db.php:1142) in /Applications/MAMP/htdocs/wordpress/wp-login.php on line 415

    Warning: Cannot modify header information – headers already sent by (output started at /Applications/MAMP/htdocs/wordpress/wp-includes/wp-db.php:1142) in /Applications/MAMP/htdocs/wordpress/wp-login.php on line 427

    It looks like there is a file somewhere that is triggering the headers.

    Try this to start:
    – temporarily de-activate your plugins or temporarily remove them (do not delete them, just move them to a temp folder)
    – revert your theme to to the 2014 theme

    This should put you back to start with your installation.

    Next,
    – activate just the theme and see if that is your issue.
    – if your good start activating one plugin at a time.

    Alternate ideas
    – If you’re running a theme that you’ve modified, try to install a clean version
    – if you’ve modified your theme look for white space

    Read the following post for more info on “header already sent”
    https://stackoverflow.com/questions/8028957/how-to-fix-headers-already-sent-error-in-php
    – stackoverflow can be a good resource, especially when the stats are really high

    stackoverflow can be a good resource

    So can the WP codex.

    Try reviewing Solving “headers already sent” warnings

    ok…

    Why or how come al the original wp-.php files don not end with a ‘ ?> ‘
    Is that not necessary?

    Not – a closing ?> is not necessary at the very end of a .php file. And it is often considered good practice to omit it in order to avoid these “headers already sent” messages.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘Can't log in to wp-admin after updating to wordpress 3.8 – Cookies error’ is closed to new replies.