What PHP is, and why its version matters
PHP is the programming language most websites run on behind the scenes, WordPress, WooCommerce, and most others are built on it. Like any software, PHP comes in versions, and which version your site runs on matters for two reasons: newer versions are faster and more secure, while some older software only works on older versions. Occasionally you need to change which version your site uses, and this article is about doing that.
Note this is a different thing from the PHP memory limit, which is how much memory PHP may use rather than which version it is, and which our article on WordPress memory errors covers. This article is about the version number.
When you'd change it
- Software that needs a newer version. Modern WordPress, plugins, and applications increasingly require a recent PHP version, and may warn you or misbehave on an old one. Moving up fixes this and usually speeds the site up as a bonus.
- Older software that needs an older version. The reverse case: a legacy site, an old plugin, or a dated application may break on the latest PHP and only run correctly on an older version. Here you need to step the version down to keep it working.
- A direct instruction. A plugin, a theme, or a developer tells you the site needs a specific PHP version.
Our servers run a current version of PHP by default, which suits most modern sites, so you would typically only change this to accommodate software with a specific requirement.
Changing the version
- Log in to cPanel at yourdomain.tld/cpanel and open MultiPHP Manager, findable via the search box.
- Select the domain you want to change, you can set the version per domain, so different sites on the same account can run different PHP versions if needed.
- Choose the PHP version from the list.
- Apply the change. It takes effect immediately.
Test your site straight afterwards, and properly, a few pages, not just the homepage, and any forms or shop functions. A PHP version change is usually smooth, but because it changes the engine your whole site runs on, the occasional site does not like the new version, and you want to find that out immediately rather than days later.
If the site breaks after changing version
If your site misbehaves right after a version change, the version is almost certainly the cause, so the first move is to change it back to what it was, which returns the site to working. From there, the real question is which version your software actually needs, and that is worth establishing before trying again. A site that breaks on a newer PHP version usually has an outdated plugin, theme, or application that needs updating to catch up, our articles on updating WordPress safely cover that side.
A word on not staying on old versions
It is tempting, when an old site only works on an old PHP version, to leave it there indefinitely. Understand the trade-off: outdated PHP versions stop receiving security updates, so a site pinned to a very old version is running on an engine with known, unpatched holes. Sometimes staying on an older version is genuinely necessary for a while, but treat it as a temporary accommodation, not a permanent home, and plan to update the software so the site can move to a supported version. If you are stuck on an old version and unsure how to move forward, that is worth a conversation with us.
Where the safe steps end, and where we help
Switching the version in MultiPHP Manager is safely yours to do, and reversing it is just as easy. Working out why a site needs a particular version, fixing software so it runs on a current one, or diagnosing a site that breaks across versions, is where we come in. Open a support ticket, tell us the site and what you are trying to run, and we will sort out the right version and, where needed, what has to be updated to get you onto a modern, supported one.
Good to know
The sensible default is the newest PHP version your software happily runs on, because newer means faster and safer, so the goal is always to be as current as your site allows rather than as old as it tolerates. Change the version only to meet a real requirement, test immediately after, and treat any need to run an old version as a problem to solve rather than a setting to forget. And because the version is set per domain, you can move one site forward without disturbing another, which makes trying a newer version low-risk: change it, test, and change it straight back if anything complains.