Hubert Sawyers III
Member
Posted 3 years ago #
Hi,
My site is not showing up and I am getting this message when I go to the /wp-admin page.
Warning: Cannot modify header information - headers already sent by (output started at /home/apolitic/public_html/wp-config.php:1) in /home/apolitic/public_html/wp-includes/pluggable.php on line 850
What's wrong?
Did you search the forums for the headers not sent error? You'll get numerous results, mostly saying that you have a space in your wp-config that shouldn't be there. This is often indeed the case.
Hubert Sawyers III
Member
Posted 3 years ago #
I searched for line 850 and something else, but I didn't see what you were saying. I will check it out though. Thanks for the prompt reply.
No the error is in you wp-config.php file. You have an blank line at the top of the file. Delete it.
Hubert Sawyers III
Member
Posted 3 years ago #
Thanks. The thing is, I do not have any blank lines or spaces in my wp-config.php file. I misinterpreted the warning to mean the problem was in the wp-includes/pluggable.php, so I removed an extra line there. I finally found the FAQ and I don't have any extra space in line 1.
Should I put the extra line back in pluggable.php?
<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information by
* visiting {@link http://codex.wordpress.org/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don't have to use the web site, you can just copy this file
* to "wp-config.php" and fill in the values.
*
* @package WordPress
*/
// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
Hubert Sawyers III
Member
Posted 3 years ago #
Now there's an extra two (2) spaces after /** in line 2. Could that be it?
What are you using to edit your wp-config file. You should only use a plain text editor like notepad. Also it doesn't have to be a blank line a single space will cause that error as well. Just place your cursor right before the opening <?php tag and hold backspace to clear any spaces.
Hauh? Re-upload the WordPress 2.7 files. You may have just made your problem worse by trying to modify that file. Edit: scratch that, thought your were editing plugable.php.
Jeremy already told you what the problem is. See this link http://codex.wordpress.org/Answers-Troubleshooting#Headers_already_sent
Now make a copy of your wp-config.php for backup purposes, keep that copy safe.
Copy the wp-config-sample.php to wp-config.php. Using you backup copy as a guide, change (only change!) the database, database user portion. If your database is not localhost, change that too.
Good luck.
Hubert Sawyers III
Member
Posted 3 years ago #
Yeah, I did that. It seemed to have cleared up the webpage showing up, but I still cannot login at my wp-login.php page.
check it out:
http://apoliticalparty.net/images/wp-config.JPG
Hubert Sawyers III
Member
Posted 3 years ago #
I appreciate everyone's help, by the way. I get frustrated when this stuff happens, so I may not be seeing what I should see.
Still have the problem. Your wp-login.php reports
Warning: Cannot modify header information - headers already sent by (output started at /home/apolitic/public_html/wp-config.php:1) in...
Have you created a fresh copy of wp-config.php? The blog page loads but you do get those errors.
Hubert Sawyers III
Member
Posted 3 years ago #
Yeah, I had my wp-config.php saved with UTF-8 encoding. I saved it as the default ANSI and I am back up and running.
Thanks everyone, you kept me from hurting myself. LOL
migbrasil
Member
Posted 3 years ago #
Ps.: i had some trouble too... I download the brazilian wordpress and the wp_config.php is f***ed up.... so i just used the american one... wordpress should know that... ;]
johnwar
Member
Posted 3 years ago #
Did you try another themes? But if you were using the default themes, it should be worked!