WordPress.org

1. catcher1138
   Member
   Posted 4 years ago #

   Ok, here's my problem:
   blog was working allright, then I installed wp-cache and problems started
   I kept having this error
   Warning: Cannot modify header information - headers already sent by (output started at /home/xxxxxxxx/public_html/wp-config.php:1) in /home/xxxxxxxx/public_html/wp-includes/pluggable.php on line 391

   I uninstalled all plugins. Nothing. I updated to 2.3.
   Now I have 2.3, and this error keeps popping up when I try to post, or when I access from http://www.xxxxx.com instead of http://xxxxx.com
   I have checked my wp-config.php and there arent any blanks in the first line, I have already uploaded a fresh version of the file, and nothing.
   I have also noticed that the wp-config.php file changes size after I upload it...
   Please please help me

2. moshu
   Member
   Posted 4 years ago #

   According to the Codex FAQ - you have an empty line/space before the opening <?php on line #1 in your config file...

   Help yourself by reading the docs:
   http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

3. catcher1138
   Member
   Posted 4 years ago #

   I know that's what's supposed to be, but I dont have any blank lines, spaces or anything!!!!
   I've checked a thousand times. Is there a way of editing the wp-config.php file without downloading it? that might be the problem...

4. moshu
   Member
   Posted 4 years ago #

   How do you upload it?

5. catcher1138
   Member
   Posted 4 years ago #

   I use cuteftp
   I edit the file with wordpad, saving it as a php with utf-8 coding
   and cuteftp does upload it in ascii, pretty sure about that

6. catcher1138
   Member
   Posted 4 years ago #

   I also seem to get this on top when I browse through the site

   WordPress database error: [Table 'XXXXXXX.wp_categories' doesn't exist]
   SELECT COUNT(1) FROM wp_categories

   where XXXXXXX is the same DB name as in wp-config

7. moshu
   Member
   Posted 4 years ago #

   Then check the "sticky" post on the front page of the forum for that error.

8. catcher1138
   Member
   Posted 4 years ago #

   ok, I finally made it work.
   the problem was a folder called headers, which was on the root folder of my server.
   thanks anyway

Topic Closed

This topic has been closed to new replies.