This article contains information on upgrading from antiquated version of PHP (< 7.3) to PHP 7.3.
For a guide on upgrading from 7.3 to 8.1, please see here.
Upgrading from PHP 5.6:
If you are upgrading from PHP 7.1 to PHP 7.2 or 7.3, your host should be able to do this without any files on our end.
If you are upgrading from PHP 5.6 to 7.3, you will need to log into your admin panel and check what IonCube version of the software you have:
Old install:
Current Install:
If you see the following string:
- (ion 7.1)
You or your host can upgrade PHP on your end without any intervention on our part. You or they can follow our CMS Requirements Page and make sure all the necessary libraries are available.
If you see ANY of the following:
- (ion 5.4)
- (ion 5.6)
- (source)
Or any other string besides (ion 7.1), please do the following:
- You or your host will need to upgrade your IonCube loaders to version 10.3.9 or greater. You can find a copy of these loaders here:
- Please contact CMS support. We will need to upgrade your admin panel files before your host can upgrade PHP.
PHP 7.0+ Pitfalls
PHP 7.0 no longer includes the original MySQL API. While the Elevated X CMS no longer uses this library, you may have other software or custom templates that uses this functionality.
If you have any software that uses this deprecated library, your host should be able to install this as a PECL module:
https://pecl.php.net/package/mysql
Although it should be possible to build this extension with PHP 7.0 and use this old library, you are strongly encouraged to port any custom code to use MySQLi / PDO, and contact any vendors that don't have direct PHP 7.0 support.
PHP 7.2+ Pitfalls
PHP 7.2 has some changes to type handling that may introduce errors on your templates.
If you are upgrading to PHP 7.2 and are using existing templates, we have a script your host can run that will correct several common errors on your PHP templates:
They can get this script here:
https://cs.elevatedx.com/fix_templates_php72.php.txt
They can retrieve this file by running:wget https://cs.elevatedx.com/fix_templates_php72.php.txt -O fix_templates_php72.php
And run the script by doing:php fix_templates_php72.php /path/to/cms_admin/phptemplates/
Where /path/to/cms_admin/ is a path to their template folder.
Note: PLEASE BACK UP ANY TEMPLATES BEFORE RUNNING THIS SCRIPT.
If you are still getting template errors after your upgrade to PHP 7.2 we recommend that you go into Global Settings, and find a setting called "Error Reporting Level". You'll want to set this value to "Only Show Fatal Errors". If you do not see this setting within your admin panel, contact CMS support and we'll update you to a new build that has this setting.
Here are some common errors you may see as part of an upgrade. The above script should fix many of these errors, but you or your designer may need to fix these manually.
Here are common ways to mitigate these errors:
sizeof: If you are receiving errors on your front-end saying that the argument passed to sizeof is not an array, you, or your designer can go into the templates and replace instances of sizeof with:
array_not_empty
This is a function built into the CMS that will return the size of an array object, or NULL if the object passed is not an array.
If you are using our standard templates, we recommend upgrading to the newest build of our templates. You can find them here:
https://cs.elevatedx.com/newest_templates.php
Warning: Use of undefined constant XXXXXX - assumed 'XXXXXX' (this will throw an Error in a future version of PHP) in /path/to/file.tpl
This happens when you see a value that looks like so:
XXXXXX
What's needed here is to put single quotes around this item. In the above case, changing the value to this:
'XXXXXX'
Will fix this error.
PHP 7.3+ Pitfalls:
If you are upgrading from PHP 7.1 or earlier, please look at the above section for PHP 7.2 pitfalls.
Otherwise, you should be able to safely upgrade from PHP 7.2 to PHP 7.3 with little to no issues.
Here are a list of backwards incompatible changes from PHP 7.2 to 7.3. None of these specific instances are used in any of our standard templates, and we have not found any of these specific use cases in custom templates as of yet.
