Fix this dodgy looking install :/
How Do I?
Moved my install of expression engine 2.5.5 to a new VPS and now the content is there but with none of the layout. Any ideas what the most common cause of that would be, enabled debugging and getting PHP errors (using the same version of PHP as the old server) A PHP Error was encountered Severity: Notice
Message: Only variable references should be returned by reference
Filename: core/Common.php
Line Number: 242
A PHP Error was encountered Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/johnstonehouseco/public_html/system/codeigniter/system/core/Exceptions.php:170)
Filename: libraries/Functions.php
Line Number: 809
A PHP Error was encountered Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/johnstonehouseco/public_html/system/codeigniter/system/core/Exceptions.php:170)
Filename: libraries/Functions.php
Line Number: 809
A PHP Error was encountered Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/johnstonehouseco/public_html/system/codeigniter/system/core/Exceptions.php:170)
Filename: libraries/Functions.php
Line Number: 809
A PHP Error was encountered Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/johnstonehouseco/public_html/system/codeigniter/system/core/Exceptions.php:170)
Filename: core/Common.php
Line Number: 412
Sounds like there may be two issues. The PHP errors appear to be related to the PHP version. I suspect the new host is running a newer version of PHP than the old host and EE v2.5 is pretty old and simply not compatible with the newer version.
You either need to downgrade PHP or better- upgrade ExpressionEngine.
> now the content is there but with none of the layout.
That could be related to the PHP errors or it could be a path or URL setting needs to be updated to reflect the new server. But I’d get the PHP error resolved first. If that doesn’t clear it up, double check your settings. Here’s a good overview of what might have changed.
Thank you so much Robin, I thought the PHP was set to 5.6 on the old server but after dropping it down to 5.4 on the new one the errors have cleared up, the content layout was down to the paths being set as http instead of https and chrome blocking the “insecure script sources”. Will update EE next week now I have it up again I’ve bought some time.
Good catch on https! And yes, even just getting on the latest v2 would get PHP 7.0 compatibility.
Glad you’re back up- and good call on getting updated once you can!