Broken Legacy SIte after migration
Permalink
Hi we needed to migrate a working version of a Concrete Site 5.6.3.5 to a new VPS server. We knew the site would break with the higher php version so we moved the website to a shared hosting platform where the php version was lower. Unfortunately the website is now broken and the server guys are struggling to fix it.
We have a holding page up so we are using this URL to see the websitehttps://www.ahaawards.co.nz/index.php...
Im at a loss to fix this and despite it being old it is a very well used site for an international ballet competition and the client is naturally annoyed. She has agreed to rebuild but in the meantime if anyone could shed any light on this?
There are loads of errors.
followed by:
If anyone can offer some help I would be very grateful.
We have a holding page up so we are using this URL to see the websitehttps://www.ahaawards.co.nz/index.php...
Im at a loss to fix this and despite it being old it is a very well used site for an international ballet competition and the client is naturally annoyed. She has agreed to rebuild but in the meantime if anyone could shed any light on this?
There are loads of errors.
2019-06-27 10:34:03 Error 203.109.251.115 500 GET /index.php HTTP/1.0
followed by:
AH01071: Got error 'PHP message: PHP Warning: require(updates/concrete5.6.3.5_remote_updater/concrete/dispatcher.php): failed to open stream: No such file or directory in /var/www/vhosts/ahaawards.co.nz/httpdocs/concrete/startup/updated_core_check.php on line 8\nPHP message: PHP Warning: require(updates/concrete5.6.3.5_remote_updater/concrete/dispatcher.php): failed to open stream: No such file or directory in /var/www/vhosts/ahaawards.co.nz/httpdocs/concrete/startup/updated_core_check.php on line 8\nPHP message: PHP Fatal error: require(): Failed opening required 'updates/concrete5.6.3.5_remote_updater/concrete/dispatcher.php' (include_path='.:/opt/plesk/php/5.6/share/pear') in /var/www/vhosts/ahaawards.co.nz/httpdocs/concrete/startup/updated_core_check.php on line 8\n'
If anyone can offer some help I would be very grateful.
- disable and clear cache
- upgrade the core to 5.6.4.0 (manual update required). 5.6.3.5 to 5.6.4.0 is a safe upgrade.
Then move the site with the core already updated.
The risk at this stage is that addons or application specific code are not php7 compatible. Most addons are fairly easy to update to php7, requiring a few changes to class names and some tweaking of function parameter lists. If the site uses eCommerce, or as an example of a particularly tricky addon, see my notes at https://www.c5magic.co.uk/add-ons/zone-based-shipping/php7/...