MultiPHP problem

My hosting company recently installed MultiPHP to enable PHP 7 support on newer C5 Version 8 sites under my VPS account (Linux CENTOS 6.9 / WHM v68.0.39).

Since that point any Concrete5 5.6.x sites have been "broken" (they're running PHP 5.6). The editor toolbar no longer shows up when trying to edit the page - basically "bricking" the site. Browsing the dashboard works mostly (occasionally getting "access denied" errors in the sitemap). I've tried disabling Cloudflare in case that was related, but no effect.

The only other info I could find about this on the forum was this post:

I've tried changing the PHP handler from suphp to cgi with no difference. Also tried enabling PHP-FPM with no difference (although the site loaded faster).

Does anyone else have any problems running MultiPHP and C5?

View Replies: View Best Answer
Steevb replied on at Permalink Reply
Have you updated 5.6 to the latest version, it will work with php7+?

Have tried setting the php version for a particular installed C5 version that works in your htaccess file?
jb1 replied on at Permalink Reply
Yep, tried upgrading to the newest version and running PHP 7.0 as well as PHP-FPM and no difference to the problem either way (cleared cache and logged out/in each time).
Definitely seems like MultiPHP isn't playing well with C5.6.x.
jb1 replied on at Permalink Reply
I got the web host to roll back the recent update of EasyApache 4 back to 3, and that fixed the problem. I'm curious if anyone else has had this issue and what the workaround was?
jb1 replied on at Permalink Best Answer Reply
In case anyone else has an issue like this - I found the solution...
In the update from easyapache 3 to 4, the "tmp" folder location is changed by default. There's a new temp folder for each version of PHP installed on the server (so if you change php versions the temp folder changes). Ensure correct permissions are applied.

There was a second cause to my issue - I had an SSL certificate installed on the site which wasn't be used (I had too many links pointing to the http version and needed time to switch). However once I made the https version the "live" one, everything started working normally. It looks like easyapache 4 expects the ssl cert to be used if it's installed and won't correctly store the session data - that's my assumption.

Hope this helps anyone struggling with this issue.