• paulgobble

    (@paulgobble)


    Like many newbie installers, I started to get a lot of errors in the admin sections after upgrading to 1.5. For example:

    Warning: Cannot modify header information – headers already sent by (output started at /home/.waddlesheater/pdg/sbox.net/blogrd105/wp-config.php:1) in /home/.waddlesheater/pdg/sbox.net/blogrd105/wp-admin/admin.php on line 6

    I’ve searched this forum and read many post advising that this is most likely the result of extra line feeds, carriage returns, etc at the very beginning or very end of the wp-config.php file. I checked this file in both bbedit (locally, showing line numbers and invisibles) and then in vim (editing the live file on my server). And I swear to you, there is nothing extra there.

    (I just got nervous and triple checked. Still nothing there)

    I also get similar errors when I click the login link except the error initiates from the wp-login.php file.

    Warning: Cannot modify header information – headers already sent by (output started at /home/.waddlesheater/pdg/sbox.net/blogrd105/wp-login.php:1) in /home/.waddlesheater/pdg/sbox.net/blogrd105/wp-login.php on line 7

    Any ideas?

    Thanks for you time,
    Paul

Viewing 15 replies - 1 through 15 (of 19 total)
  • 105/wp-login.php:1)

    Is this at the very very top of wp-login.php

    <?php

    Nothing at all above it ? Nothing ?

    Thread Starter paulgobble

    (@paulgobble)

    nothing

    What text editor are you using ?

    Notepad / Wordpad / BBEdit / Textwrangler ?

    Hmm….you said BBEdit…… view it in something else ?

    Thread Starter paulgobble

    (@paulgobble)

    vim – on the server when I ssh in.

    wp-config.php then – did you use the one with 1.5 or has that not altered during upgrade ?

    Thread Starter paulgobble

    (@paulgobble)

    Well, thats where the whole problem started. My hosting is through DreamHost (a very excellent outfit, I must say). I originally installed WP 1.2 via their oneclick installer which worked great except that I did not own the wp-config.php file nor did I have sufficient privileges to read or write to it. Consequently, when I upgraded to 1.5 I had to install a new wp-config.php file, copied from the 1.5 wp-config-sample.php file. Then I had to configure it myself (not a good thing).

    Thread Starter paulgobble

    (@paulgobble)

    Would you like to see it (my wp-config.php file)?

    Odd …. the headers already sent error is always – at least on these forums – a whitespace error.
    wp-config.php is called first so that info can be got from the db, and according to the error text, there is an issue on line 1

    Anything after <?php at that end of the file will be fine, but anything before that will kick the error out.

    How about you remove the personal info from your file – the 4 details – then post your file at https://paste.uni.cc ? I’ll refresh there until I see it ??

    Thread Starter paulgobble

    (@paulgobble)

    OK, I think I did what you asked. Did you find it?

    Thread Starter paulgobble

    (@paulgobble)

    Line 7 hardwrapped. “value” is really at the end of line 6.

    Gets odder ….. I’d now ask about the ftp program but you mention vim, and things like ‘vim’ and ‘ssh’ mean nothing to me, especially when it comes to files / characters.

    If you delete the existing config file, then upload a fresh one, does the error persist ?
    Can your site be viewed ?

    Thread Starter paulgobble

    (@paulgobble)

    Yeah, the site mostly functions (I’m still having troubles getting the exhibit plugin to work)

    https://www.sbox.net/blogrd105

    I’ll take a crack at reuploading the file.

    (ps. vim is a unix text editor that runs in a command line shell (ssh) )

    lbessant

    (@lbessant)

    For Exhibit, you might find this useful (a user[1] contribution to Dreamhost’s really quite useful[2] KnowledgeBase)

    In exhibit10.php, there is a block of code near the very beginning (line 46) that says:

    $_SERVER['SCRIPT_NAME']=
    ...
    $_SERVER['REQUEST_URI']);

    Remove that whole block and replace it with:

    $_SERVER['SCRIPT_NAME'] = $_SERVER['SCRIPT_URL'];

    Before I found that, I couldn’t get Exhibit to appear in the admin interface

    [1] Not me – found it after much head-scratching and googling
    [2] Understatement – it’s an excellent resource for DH users

    Wierd .. and why can’t I shake off the feeling that there is a tree right in front of me that I just can’t see …

    I’ve seen blog, and it works – wp-config is therefore healthy
    I’ve registered – email is sent and all is still good
    I click ‘Login’ and errors pop up .. which all narrows it down to those files involved in login – wp-login.php

    Try deleting wp-login.php and reupload a new file.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Header Errors (no extra white space, I swear)’ is closed to new replies.