Forums

[resolved] Error on login page (10 posts)

  1. 02ranger
    Member
    Posted 2 years ago #

    I run a website for my church and have had it running for several months now. Everything was great, until I moved it from Yahoo's servers to Blue Host. After the move, I've gotten the following error on the wp-login.php page.

    Warning: Header may not contain more than a single header, new line detected. in /home4/southsj5/public_html/main/wp-login.php on line 304

    After trying to login, I get the following message:

    Warning: Header may not contain more than a single header, new line detected. in /home4/southsj5/public_html/main/wp-login.php on line 304

    Warning: Cannot modify header information - headers already sent by (output started at /home4/southsj5/public_html/main/wp-login.php:304) in /home4/southsj5/public_html/main/wp-includes/pluggable.php on line 662

    Warning: Cannot modify header information - headers already sent by (output started at /home4/southsj5/public_html/main/wp-login.php:304) in /home4/southsj5/public_html/main/wp-includes/pluggable.php on line 663

    Warning: Cannot modify header information - headers already sent by (output started at /home4/southsj5/public_html/main/wp-login.php:304) in /home4/southsj5/public_html/main/wp-includes/pluggable.php on line 664

    Warning: Cannot modify header information - headers already sent by (output started at /home4/southsj5/public_html/main/wp-login.php:304) in /home4/southsj5/public_html/main/wp-includes/pluggable.php on line 666

    Warning: Cannot modify header information - headers already sent by (output started at /home4/southsj5/public_html/main/wp-login.php:304) in /home4/southsj5/public_html/main/wp-content/plugins/simple-forum/credentials/sf-credentials.php on line 113

    Warning: Cannot modify header information - headers already sent by (output started at /home4/southsj5/public_html/main/wp-login.php:304) in /home4/southsj5/public_html/main/wp-includes/pluggable.php on line 865

    I've gone through the wp-login file and the pluggable.php file, as well as the sf-credentials.php file. I couldn't find any blank spaces at the start or end of the files, and it appeared to be correct everywhere else. Of course, I'm very much a novice so I may have missed something. I did notice that at each of the indicated lines in the error messages, it is using the setcookie command.

    Lines 301-304 in wp-config.php:
    301 //Set a cookie now to see if they are supported by the browser.
    302 setcookie(TEST_COOKIE, 'WP Cookie check', 0, COOKIEPATH, COOKIE_DOMAIN);
    303 if ( SITECOOKIEPATH != COOKIEPATH )
    304 setcookie(TEST_COOKIE, 'WP Cookie check', 0, SITECOOKIEPATH, COOKIE_DOMAIN);

    Lines 660-666 in pluggable.php:
    660 // Set httponly if the php version is >= 5.2.0
    661 if ( version_compare(phpversion(), '5.2.0', 'ge') ) {
    662 setcookie($auth_cookie_name, $auth_cookie, $expire, PLUGINS_COOKIE_PATH, COOKIE_DOMAIN, $secure, true);
    663 setcookie($auth_cookie_name, $auth_cookie, $expire, ADMIN_COOKIE_PATH, COOKIE_DOMAIN, $secure, true);
    664 setcookie(LOGGED_IN_COOKIE, $logged_in_cookie, $expire, COOKIEPATH, COOKIE_DOMAIN, false, true);
    665 if ( COOKIEPATH != SITECOOKIEPATH )
    666 setcookie(LOGGED_IN_COOKIE, $logged_in_cookie, $expire, SITECOOKIEPATH, COOKIE_DOMAIN, false, true);

    Line 865 on pluggable.php:
    header("Location: $location");

    Line 113 in sf-credentials.php:
    setcookie('sforum_' . COOKIEHASH, stripslashes($dname), time() + 30000000, $cookiepath, false);

    I added the line numbers at the start while typing this post, they are not part of the actual files. Any help anybody can give would be greatly appreciated. I also extracted a fresh copy of the wp-login.php from wordpress' site and uploaded it in place of my file, no luck. I've since put my original wp-login.php file back in place. Thanks.

  2. esmi
    Theme Diva & Forum Moderator
    Posted 2 years ago #

    Try deactivating the Simple Forum plugin.

  3. 02ranger
    Member
    Posted 2 years ago #

    I can't get into the admin page at all. When I click login, it just gives all the errors. I did try a method that I found on another forum entry. I renamed the plugins folder to pluginsholding and made a new folder called plugins to see if that was the problem. It didn't help my problem or change the errors at all. Thanks for your help, though.

  4. esmi
    Theme Diva & Forum Moderator
    Posted 2 years ago #

    Try resetting the plugins folder by phpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

  5. 02ranger
    Member
    Posted 2 years ago #

    OK, I tried deactivating the plugins through phpMyAdmin with no luck. It still gives the same error on the login page, and the same errors after trying to log in.

  6. bh_WP_fan
    Member
    Posted 2 years ago #

    look for and remove extra spaces after the closing ?> php tag in your wp-config.php as well and do another run through of your login.php. Extra spaces will not always show so download the file and open it up in a simple text editor like notepad. Keep the plugins disabled as you test.

  7. kelseyd
    Member
    Posted 1 year ago #

    bh_WP_fan - but how can one disable plugins while not disturbing the functionality/appearance of the website that is live? That's what I don't get about upgrading WordPress too.. They say to disable plugins before you upgrade but how can you do that while a site is live?

  8. James
    Happiness Engineer
    Posted 1 year ago #

    Depending on what plugins you'r using, they may disrupt the appearance of the blog when deactivated, but in the case of troubleshooting and updating, they'll only be inactive for a few minutes.

  9. kelseyd
    Member
    Posted 1 year ago #

    ok. I've only been able to update manually so i think my update process takes a little longer than the automatic upgrade. But still maybe not long enough for things to be down then... Thanks for your reply!

  10. James
    Happiness Engineer
    Posted 1 year ago #

    You're welcome!

Topic Closed

This topic has been closed to new replies.

About this Topic