Host DadaWPBuild

Plans and safety

PHP versions and upgrades

Testing a newer PHP version on staging, and end-of-life versions.

Why it matters

PHP is the language WordPress runs on. Old versions no longer get security fixes, and newer plugins may need a newer version. Upgrading can also break old themes and plugins, so it's worth testing first.

Testing an upgrade on staging

  1. A connected site's staging copy starts on the same PHP version as your live server.
  2. On the Preview tab, choose a newer version from the PHP menu. Staging restarts on it.
  3. Look round the site. If something breaks, ask the AI to fix it, for example "The gallery page shows an error on PHP 8.3: please fix it".
  4. When everything works, send the fixes live from the Changes tab.
  5. Then change the live server's PHP version. For your own hosting, do this in its control panel. For the hosting included in your plan, contact support.

Old, unsupported versions

  • Staging can run an end-of-life version only while your live site does, and only for a limited time. A notice says how long.
  • It runs with extra restrictions. When the time is up, staging moves to a supported version automatically.
  • You can never switch staging to an older version than the live server's.

When sending changes

If the changes you're sending need a newer PHP than the live site runs (for example, an updated plugin), you're warned before anything is sent. Upgrade the live server's PHP first, then check what changed again. Going live on other hosting also checks the server's PHP version first.