ScrltOTara Posted January 8, 2017 Share Posted January 8, 2017 I foolishly upgraded my php to version 7 and have all sorts of errors. I did it because WHMCS suggested it, but it seems they aren't quite ready for it. When I try to edit one of my products, I get the following error: Fatal error: The file /home/tlang/public_html/modules/servers/ahsaybackups/ahsaybackups.php was encoded by the ionCube Encoder for PHP 5.0 and cannot run under PHP 7.0. Please ask the provider of the script to provide a version encoded with the ionCube Encoder for PHP 5.6. in Unknown on line 0 Any ideas how to fix this so I can edit my products? 0 Quote Link to comment Share on other sites More sharing options...
ScrltOTara Posted January 8, 2017 Author Share Posted January 8, 2017 I figured it out - apparently there were several modules from older installations that are not in the current installation, so I just deleted them. 0 Quote Link to comment Share on other sites More sharing options...
agentblack Posted January 8, 2017 Share Posted January 8, 2017 We are running into the same issues. We upgraded to PHP7 and the server started having issues when we attempted to add new products. A review of the logs shows that the following modules have not/are not/were not/did not get upgraded in 7.1: Enomtruste plesk8 plesk9 plesk10 pleskreseller fluidvm Once we purged all of those modules (we dont use them anyways so its ok), our installation started working again. Shame on whmcs for suggesting upgraded to php7 without ensuring their product is ready for the new version. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted January 8, 2017 Share Posted January 8, 2017 A review of the logs shows that the following modules have not/are not/were not/did not get upgraded in 7.1: Enomtruste plesk8 plesk9 plesk10 pleskreseller fluidvm Once we purged all of those modules (we dont use them anyways so its ok), our installation started working again. Shame on whmcs for suggesting upgraded to php7 without ensuring their product is ready for the new version. but those files aren't included in the v7 releases - they were deprecated ages ago and the only reason you have them is because they were already there on your server. for their own reasons, WHMCS installations don't remove old files - that's down to you to do. fair enough that you followed the WHMCS upgrade advice and just installed the upgrade on top of the existing files... though I always think that's not great advice as it will leave v6, or earlier, files still on the server... and WHMCS often only needs one dodgy file to break it. if you had done a clean installation, after first testing your v6 site using a developer license, you wouldn't have ran into the above issues. 0 Quote Link to comment Share on other sites More sharing options...
twhiting9275 Posted January 9, 2017 Share Posted January 9, 2017 WHMCS really needs to get on the ball with upgrades here, replacing old files with blank ones. This would help out tremendously. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.