How to Back Up Joomla Before Changing PHP Versions
Check Joomla and extension compatibility first
Before changing PHP, confirm the installed Joomla release supports the target PHP version and check third-party extensions and templates with their developers. Current Joomla technical requirements publish supported PHP versions for each Joomla family. A server can successfully switch PHP while application code still fails under the new runtime.
Create a full recovery point
Back up the Joomla database and site files immediately before the PHP change. Include configuration.php, extensions, templates, media, and other site-specific files. The PHP version itself is server configuration, so also record the current runtime settings needed to reverse the environment change.
Record the working PHP configuration
Capture the current PHP version, handler or execution mode when relevant, enabled extensions/modules, memory limit, upload limits, execution time, timezone, and any custom php.ini, .user.ini, pool, or hosting-panel settings. A rollback is much easier when the previous environment is documented rather than remembered.
Keep the backup outside the production account when practical
Store at least one recovery copy in protected storage away from the Joomla web root and preferably outside the same hosting failure domain. Do not leave a database export or full-site archive at a predictable public URL.
Make the PHP change separately from other upgrades
When possible, do not combine a PHP switch with a Joomla update, extension update, template replacement, and configuration redesign in one step. Change one major layer at a time, then test. This makes an incompatibility much easier to attribute and reverse.
Test Joomla immediately after the switch
Check the frontend, /administrator, login, forms, media handling, email, scheduled tasks, command-line jobs, and important extensions. Review PHP and web-server logs for deprecations, fatal errors, missing modules, or configuration differences. A homepage loading successfully does not prove the entire site is compatible.
Roll back the runtime before restoring data when appropriate
If the PHP change alone causes failure and no Joomla data was altered, reverting to the previous PHP configuration may be enough. If other changes or failed processes modified files or the database, use the verified backup as needed. Document the result before attempting a different PHP version or compatibility fix.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.