1

I'm getting the following errors after upgrading from EE version 2.5.3 to 2.11.7.

Any ideas how to solve this one?

Thanks in advance,

Tom

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/expressionengine/public_html/index.php:54)
Filename: core/EE_Input.php
Line Number: 213

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/expressionengine/public_html/index.php:54)
Filename: core/EE_Input.php
Line Number: 213

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/expressionengine/public_html/index.php:54)
Filename: core/EE_Input.php
Line Number: 213

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/expressionengine/public_html/index.php:54)
Filename: core/Common.php
Line Number: 475
Improve this question
7
  • Your real error(s) will be just above this list - are you sure you didn't miss something off the top?
    – James Smith
    Commented Mar 17, 2017 at 15:15
  • That's all that's displaying? (tomperkins.net) I had to add some special code to index.php to get that to display, turning on debugging did nothing.
    – Tom Perkins
    Commented Mar 17, 2017 at 15:17
  • Taken from stackoverflow.com/questions/1475297/phps-white-screen-of-death/…
    – Tom Perkins
    Commented Mar 17, 2017 at 15:18
  • Hm, strange. Make sure you have nothing before the opening <?php tag in index.php. Then try disabling extensions in your config file to see if it's a third party incompatibility - $config['allow_extensions'] = 'n';
    – James Smith
    Commented Mar 17, 2017 at 15:26
  • That's now loading the site James, any ideas how I go about identifying which is causing the problem?
    – Tom Perkins
    Commented Mar 17, 2017 at 16:07

1 Answer 1

Reset to default
2

It does sound like some file either has whitespace inserted ahead of its opening <?php tag, or you have a file that is using closing PHP tags ?> and has whitespace after it. ExpressionEngine files do not use a closing PHP tag for this reason.

If it happened after an upgrade and that's the only change, there is a chance that a file got corrupted in deployment (FTP errors for example). You might try re-uploading the system files if you aren't able to spot the whitespace easily in user-modified-files.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.