I visited [my website](http://propellerng.com/) and discovered this error report:
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/propelle/public_html/index.php:113) in /home/propelle/public_html/wp-content/themes/dw-focus/framework/helpers/class-fw-flash-messages.php on line 241
I tried to access the [Dashboard](http://propellerng.com/wp-admin/), I encountered another error:
Warning: Cannot modify header information – headers already sent by (output started at /home/propelle/public_html/wp-load.php:113) in /home/propelle/public_html/wp-content/plugins/wordpress-seo/admin/class-admin-init.php on line 84
Warning: Cannot modify header information – headers already sent by (output started at /home/propelle/public_html/wp-load.php:113) in /home/propelle/public_html/wp-includes/pluggable.php on line 1171
Please what is the cause of these?
This error is caused if the your PHP scripts are printing to the browser prior to sending headers. A common example is printing the html tags prior to starting a session, or setting a cookie. The error tells the line that needs to be altered (in this case, it is on wp-includes/pluggable.php on line 1171
wordpress-seo/admin/class-admin-init.php on line 84
dw-focus/framework/helpers/class-fw-flash-messages.php on line 241).
To resolve this error remove the lines from the PHP code that are printing to the browser prior to sending headers.
Another common cause for this error is white space either at the beginning or end of the file. The fix is to remove that whitespace from the file. Read the error message carefully. It says output started at … followed by a file name and a line number. That is the file (and line) that you need to edit. Ignore the second file name – that is only a file that included the file that has the whitespace. The first file is the one you have to edit, not the second one.
Take a look at this section in the Codex: https://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F
Thank you, I have resolved it.
Please login or Register to submit your answer