• When I try to login into WordPress, I stumble upon this…

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-login.php on line 7

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-login.php on line 8

    ——————
    Does the problem come from my host or the php file? And how can I solve it?

    Thank you in advance.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Scrub what I just posted
    When did this happen exactly ?
    what happened just before ?

    Thread Starter zachster

    (@zachster)

    I just installed wp, and I’m trying to log in for the first time.

    When installing for the first time, the ‘headers already sent’ error is usually caused by wp-config.php

    The odd thing here is the file it mentions:
    https://crushmebaby.s33.net/.header:2

    What is the file .header ? It is not a core wp file.

    Please explain your install so we can understand it ?

    Thread Starter zachster

    (@zachster)

    <?php
    // ** MySQL settings ** //
    define(‘DB_NAME’, ‘5295’); // The name of the database
    define(‘DB_USER’, ‘5295’); // Your MySQL username
    define(‘DB_PASSWORD’, ‘password’); // …and password
    define(‘DB_HOST’, ‘localhost’); // 99% chance you won’t need to change this value

    // Change the prefix if you want to have multiple blogs in a single database.
    $table_prefix = ‘wp_’; // example: ‘wp_’ or ‘b2’ or ‘mylogin_’

    // Change this to localize WordPress. A corresponding MO file for the
    // chosen language must be installed to wp-includes/languages.
    // For example, install de.mo to wp-includes/languages and set WPLANG to ‘de’
    // to enable German language support.
    define (‘WPLANG’, ”);

    /* Stop editing */

    define(‘ABSPATH’, dirname(__FILE__).’/’);
    require_once(ABSPATH.’wp-settings.php’);
    ?>

    ——————
    I only followed the Famous 5-minute install and edit the top part only for the wp-config.php . The DB Name was given to me by the host as well as the DB User, and the password as well in which I’ve changed above but the actual password is stated on my wp-config.php that I’ve uploaded.

    And as far as I know (checked the whole file manager) I dont have the the file ‘.header’
    Could it be from my host?

    It could be …. do they put banners on the site ?

    The error is pointing at wp-login.php (not wp-config.php), which appears to be cracking on these lines:

    header('Expires: Wed, 11 Jan 1984 05:00:00 GMT');
    header('Last-Modified: ' . gmdate('D, d M Y H:i:s') . ' GMT');

    Try reuploading wp-login.php.

    Thread Starter zachster

    (@zachster)

    Do I need to change the dates and reupload?
    —-
    And yes they do put a banner on the site.

    Change the dates in the header()s? No, just try removing the copy of wp-login.php you have online now and upload it again. It’s possible it got corrupted the first time through (assuming it really is wp-login.php at fault).

    Thread Starter zachster

    (@zachster)

    I removed the copy and upload it again, and no difference.

    ——————

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-login.php on line 7

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-login.php on line 8

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-login.php on line 9

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-login.php on line 10

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-login.php on line 11

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-includes/pluggable-functions.php on line 151

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-includes/pluggable-functions.php on line 152

    Warning: Cannot modify header information – headers already sent by (output started at https://crushmebaby.s33.net/.header:2) in /home/vhosts/crushmebaby.s33.net/wp-includes/pluggable-functions.php on line 129

    Possible this is a transfer mode issue (definitely weird enough for one). Are your php files uploaded as (ASCII) text, or binary?

    Thread Starter zachster

    (@zachster)

    I’m not sure, I think it’s in Windows Binary

    See if you can unload in ASCII text. It’s *possible* the binary mode is causing problems with the file(s).

    Greetings Zach. I have had the same problem/error messages with my sites:

    https://www.ads-software.com/support/topic/38444

    I’ve learned doing little patches doesn’t work (as people here suggest). I’m no code guy, but everytime I fix a something.php file (as shown in the error messages) it produces a new somethingelse.php file that is now the problem. It’s a loop, like patching holes while new ones open in a sinking ship.

    The suggestion I was offered was to do a clean install. I’m about to do that now, but what I did first was create a new ‘fake’ blog on my server space to see if that one came with the error messages as well. It didn’t, and I could post to it, and that’s what is encouraging me to do a reinstall of my existing blogs.

    Good luck and I’ll try to keep you posted.

    ATT WP GURUS:

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘wp-login error’ is closed to new replies.