In September 2020, Nuagerie began moving the native PHP version of its hosting environment from PHP 5.6 to PHP 7.4. The objective was to modernize the runtime used by hosted websites while retaining a transition path for applications with specific compatibility requirements.
Modernizing PHP with application compatibility in mind
PHP runs a large proportion of hosted websites and applications. Its evolution matters both for developer features and for software maintenance. A version change must also account for each website’s content management system, plugins, theme and custom code.
The announced transition was in progress at that point. PHP 7.4 was the intended new native version, while preparations for PHP 8.0 were undergoing testing. That preparatory work was not an announcement that PHP 8.0 was generally available.
Version selection to support the transition
The CloudLinux PHP Selector allowed a different version to be selected when required by an application. The environment also offered extension settings, including options for Phalcon and ionCube Loader. These components needed to remain compatible with the selected PHP version and the software using them.
This flexibility supports a methodical upgrade: check application requirements, prepare a backup, test essential functions and validate the website after changing its runtime. A version being available in a selector does not mean that it remains supported by the PHP project.
Choosing an appropriate version for your website
When planning a change, review your application’s requirements and the official PHP support schedule. Our team can help you review the options available for your hosting service and identify the compatibility checks to make before proceeding.
Map the requirements of an older application
For a business that relies on an older application, the useful first step is to identify what keeps it tied to its current PHP environment. That may be a plugin, an encoded component or custom code. Nuagerie can help review the hosting-side requirements and discuss development work when the application itself needs to evolve.
Send the application name and version, its required extensions and the function that must remain available through the client area. If a developer or software publisher maintains it, include their compatibility requirements. This turns a broad request to change PHP into a clearer plan for preserving the work your application supports.
