Upgrading to EE3 Has Broken My Site - Unable to Resolve - Unexpected character in input - already tried upgrading PHP
News and General
I am extremely frustrated right now. Upgrading to Expression Engine 3.3.2 from Expression Engine 2.11.1 has been a complete disaster.
I followed the directions here locally as thoroughly as possible to ensure I had a working site before I tried pushing it to live. https://docs.expressionengine.com/latest/installation/upgrade_from_2.x.html
Once I got it working, I pushed it through the repo to my production server, and it has nothing but problem after problem. I finally copied my development database to live, and bypassed the whole installation process, as it seems your install has no way of being pushed through a repo, and errors out when it finds a EE 2 database, after the files have already been ran through the upgrade.
I am not down to one major, completely obnoxious issue that appears on index.php on the frontend and admin.php in the backend.
The backend errors I have managed to suppress by removing all comments from admin.php, but that did not solve this on the frontend.
The error I get is …
Warning: Unexpected character in input: ’ in /home4/wscott84/public_html/newcitytimes/index.php on line 184
This is repeated about 50 times, and then finally…
Warning Cannot modify header information - headers already sent by (output started at /home4/wscott84/public_html/newcitytimes/index.php:184) ee/EllisLab/ExpressionEngine/Boot/boot.common.php, line 459 show details
Severity: E_WARNING
I have gone from running php 5.3 to php 7, and then issue remains. Please help, this site has been down way longer than I anticipated already.
Re-upload a clean set of files. My first guess would be some whitespace (a blank line) at the top of one of your files.
Am I checking for while space at the top of only index.php or admin.php, or other files as well?
As I’ve said, re-uploading a set of known good files should help.
I should mention that I don’t get this error running locally on WAMP. Since the site is on version control, if a file was messed up, version control would detect it, but version control says the files are good.