WordPress.org

1. sfcooper
   Member
   Posted 8 months ago #

   I'm trying to install a fresh version of 3.2.1 but get:

   Warning: Cannot modify header information - headers already sent by (output started at /nfs/c08/h03/mnt/121974/domains/prettyfishbowl.com/html/wp-config.php:1) in /nfs/c08/h03/mnt/121974/domains/prettyfishbowl.com/html/wp-admin/install.php on line 54

   I've read lots of other posts about removing whitespace yada yada yada, but this is a brand new installation. I've only just downloaded it from the wp.org site, and the only thing i've changed is the wp-config file with my db values. (and there's no spaces there either).

   Does anyone have ideas?

2. Samuel B
   moderator
   Posted 8 months ago #

   that error output is almost always right on
   you have a tab or space at the beginning or end of wp-config.php

3. sfcooper
   Member
   Posted 8 months ago #

   No I dont.

   Just did a download of v.3.1 and managed to get it to work fine.

4. Jan Dembowski
   Volunteer Mod. & Brute Squad
   Posted 8 months ago #

   Just did a download of v.3.1 and managed to get it to work fine.

   You did somewhere; It's always a tab or space. And running older versions of WordPress is asking for trouble.

   If you've backups give re-applying 3.2.1 a try. And check your wp-config.php file too.

5. sfcooper
   Member
   Posted 8 months ago #

   Already upgraded to 3.2.1 via the UI.

   Still think there's something odd in the original config file. I only entered the db values.

   Thanks

6. Jan Dembowski
   Volunteer Mod. & Brute Squad
   Posted 8 months ago #

   Still think there's something odd in the original config file. I only entered the db values.

   There might be. Try making a backup copy of your current wp-config.php file and then make a copy of the wp-config-sample.php file to wp-config.php.

   Now go into the new wp-config.php (keep that old backup copy safe!) and carefully using a plain jane text editor put in your DB user id, password, etc.

   If your blog works, then you can put in the other bits that may be in your backup copy. If your blog tanks just put back that backup copy you made and you'll be back where you were.

7. sfcooper
   Member
   Posted 8 months ago #

   But that's the thing. It's a brand new site. I'd downloaded a copy of 3.2.1, opened wp-config, and only entered my db values precisely.

   Didnt make any other change in that file and didn't even open any other.

   Then just pushed up to my server via FTP and then the warning.

   There's nothing to back up.

   Anyway, fixed now.

   Thanks

Reply

You must log in to post.