Have you every encountered this WordPress error? Are you getting this error in your WordPress blog? This is something I’ve seen quite a bit. All of a sudden your blog disappears and you’ve got this error.

Warning: Cannot modify header information – headers already sent by(output started at /home/htdocs/wordpress/wp-config.php:1) in /home/htdocs/wordpress/wp-login.php…….

I understand the frustration. Encountering an error like this is very frustrating indeed. Especially if you have no idea what to do and you can’t risk deleting a file because it might cause the whole site to break.

But all errors have fixes and this one is not an exception. So, we will guide you through the whole process of fixing the error and hope that by the end of this guide, it is fixed.

What Causes this WordPress Error?

There may be a few reasons why this is happening, from bad coding to probably plugin errors. With fixes that involve you resetting your site but this only happens rarely and doesn’t have to involve resetting your site.

Worry not, we are here to help. Just follow the step-by-step guide below and that should fix this WordPress error.

WordPress Error Fix

Connect via FTP

Step 1

You’ll need to connect to your blog via FTP. Look for a file called wp-config.php and download it. This file is created when you install WordPress, and it won’t be available in your local files, so you must download it to fix the error.

Step 2

Now open the file and check out the top of the file starting with <?php. If there are any spaces before it, delete them. Then scroll down to the bottom of the file and check for any spaces below the php?> and remove them if there are any.

In most cases, this should solve the problem and it’s the easiest fix, so best to at least rule it out first.

Check the plugins

If the above method doesn’t work, you may want to try removing your plugins, because it may be a plugin that is causing the error.

You can do this by doing the following:

Step 1

Connect to your site via FTP and downloading the /plugins/ folder.

Step 2

Once you’ve done that, delete all the plugins from the /plugins/ directory on the remote server. Don’t be alarmed if we are asking you to delete the /plugins/ folder on your site. The /plugins/ folder that you downloaded from your FTP is a back-up. So your plugins are not removed completely.

Check and see if the error is gone.

If it is, reupload the plugins from your local /plugins/ directory one by one checking each time to make sure the error hasn’t returned.

A few words

And that was it!

If none of the above method is working,  you can also try upgrading your version of WordPress as it may be caused by a wrong WordPress version.

And that was a few fixes that can possibly solve that problem. Due to the diversity of the error, you may require professional assistance from a web developer who knows what he is doing.

If the error still persists after doing the steps above, then seek out professional help, but we are confident that by doing the steps above, the error should be fixed.

If you do require a professional assistance, we can gladly help you. Feel free to contact us and we can personally fix it for you.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.