How to Back Up Joomla Before Changing PHP Versions
Before changing the PHP version used by a Joomla site, create a fresh recovery point and record the working server configuration. A PHP switch does not normally alter Joomla data by itself, but an incompatible runtime can make the site or Administrator inaccessible, and troubleshooting often leads to additional changes that are much safer when a verified backup exists.
Confirm the target PHP version is compatible
Check the technical requirements for the installed Joomla release and the requirements published by the developers of important extensions and templates. Do not assume that a PHP version supported by Joomla core is automatically supported by every third-party extension on the site.
For a production site, test the target PHP version on staging first when practical. This is especially important when moving across a major PHP release.
Create a full Joomla recovery point
- Back up the complete Joomla database.
- Back up the Joomla filesystem, including
configuration.php, extensions, templates, media, and site-specific files. - Record the backup time and the Joomla version.
- Copy the recovery set to protected storage outside the public web root.
Confirm that both the database export and file archive are readable before making the PHP change.
Record the current PHP environment
Write down the current PHP version and any settings you may need to restore: enabled extensions/modules, memory limit, upload limits, execution time, handler or execution mode, and custom php.ini or .user.ini settings. If your hosting panel lets you change PHP per domain, record the current selection before switching it.
Change PHP without combining unrelated upgrades
Change the PHP version as a separate maintenance step whenever possible. Avoid simultaneously updating Joomla, replacing a template, and upgrading multiple extensions. Keeping the PHP switch isolated makes it much easier to identify the cause if the site fails.
Test the site immediately after the change
- Load the frontend and several deep pages.
- Sign in to
/administrator. - Test login, forms, media handling, email, scheduled tasks, and critical extensions.
- Review PHP and web-server error logs for fatal errors, missing modules, warnings, or deprecations.
A working home page alone does not prove the site is compatible with the new runtime.
Roll back PHP first when the runtime is the only change
If the site failed immediately after the PHP switch and no Joomla files or database data were changed, restoring the previous PHP version and settings is usually the cleanest first recovery step. If troubleshooting or failed processes also changed the application, use the verified Joomla backup as needed.
Once the site is stable, resolve the incompatible extension or configuration before attempting the PHP change again.
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.