Forums

[resolved] login error regarding wp-login and wp-config (4 posts)

  1. jenngood
    Member
    Posted 1 year ago #

    Anyone have any idea how to fix this? I think I may have forgotten to deactivate my plugins before upgrading WP to 3.0. I have since deleted all plugins and re-uploaded wp-config.php, wp-login.php and wp-pluggable to wp-includes.

    HELP! PLEASE!

    Warning: Cannot modify header information - headers already sent by (output started at /home/edwardma/public_html/massage-in-asheville/wp-config.php:63) in /home/edwardma/public_html/massage-in-asheville/wp-login.php on line 337

    Warning: Cannot modify header information - headers already sent by (output started at /home/edwardma/public_html/massage-in-asheville/wp-config.php:63) in /home/edwardma/public_html/massage-in-asheville/wp-login.php on line 349

    Warning: Cannot modify header information - headers already sent by (output started at /home/edwardma/public_html/massage-in-asheville/wp-config.php:63) in /home/edwardma/public_html/massage-in-asheville/wp-includes/pluggable.php on line 690

    Warning: Cannot modify header information - headers already sent by (output started at /home/edwardma/public_html/massage-in-asheville/wp-config.php:63) in /home/edwardma/public_html/massage-in-asheville/wp-includes/pluggable.php on line 691

    Warning: Cannot modify header information - headers already sent by (output started at /home/edwardma/public_html/massage-in-asheville/wp-config.php:63) in /home/edwardma/public_html/massage-in-asheville/wp-includes/pluggable.php on line 692

    Warning: Cannot modify header information - headers already sent by (output started at /home/edwardma/public_html/massage-in-asheville/wp-config.php:63) in /home/edwardma/public_html/massage-in-asheville/wp-includes/pluggable.php on line 890

  2. patyuen
    Member
    Posted 1 year ago #

    That is indicative of some bad code in one of the files. It might be as simple as an extra space. Download a new copy of WP3 and all the plugin and reupload them making sure you have a backup of any modified files.

    Don't replace wp-config.php, .htaccess, and any other files you have placed there that is not part of WordPress.

    I had this exact msg the other day when I used Filezilla to edit a file remotely. Editing the file locally and uploading fixed it.

  3. Samuel B
    moderator
    Posted 1 year ago #

  4. jenngood
    Member
    Posted 1 year ago #

    Wow! I can't believe the white spaces AFTER my last ?> php closing tags being deleted solved the problem. It's like having gremlins in code. Bizarre!
    SOLVED.

Topic Closed

This topic has been closed to new replies.

About this Topic