How to Update Joomla Safely

A Joomla update can change core files, database schema, compatibility requirements, and the way third-party extensions interact with the site. The safe way to update is to create a tested rollback point, confirm the target release is appropriate for the site, resolve compatibility issues before the update, and verify the site afterward instead of treating the Update button as the whole procedure.

Create a recovery point before changing Joomla

Make a complete backup of both the Joomla files and database. The two belong together: restoring only old files against a newer database, or restoring an old database beneath newer files, can create a second failure.

  1. Create a full site backup using a backup extension, hosting backup system, or another method you know how to restore.
  2. Confirm the backup completed without errors and is stored somewhere that will still be available if the site becomes inaccessible.
  3. For an important production site, verify the restore procedure on staging or otherwise confirm that the backup is genuinely restorable.
  4. Record the currently installed Joomla, PHP, and database versions so you know the starting state.

If the site accepts orders, registrations, form submissions, or other live data, choose an update window where a rollback will not silently discard important transactions.

Review the target update and the Pre-Update Check

In Joomla Administrator, go to System → Update → Joomla. Confirm the installed version, the version Joomla proposes to install, and the update channel configured under the Joomla Update options.

For an update to the next major Joomla version, review the Pre-Update Check rather than clicking through it. Resolve failed required settings and investigate every third-party extension whose compatibility is uncertain. Joomla's compatibility report depends on update metadata supplied for extensions, so an apparently clean report is useful evidence but not a substitute for checking critical extensions with their developers.

For the Joomla 5.4 to Joomla 6 upgrade path, Joomla's current migration documentation requires the Joomla 5 Behaviour - Backward Compatibility plugin to be disabled and Behaviour - Backward Compatibility 6 to be enabled before Live Update can proceed. If the Joomla 5.4 site breaks when the older compatibility plugin is disabled, re-enable it and resolve the incompatible extension or custom code before attempting Joomla 6.

Update dependencies and test the exact upgrade on staging

Check the current release notes and upgrade instructions for business-critical extensions and templates. Some extensions require a bridge release or database migration before Joomla itself is upgraded. Update, replace, or safely remove incompatible dependencies in the order their developers recommend.

For a major upgrade or an important site, restore a current production backup to staging and perform the same sequence you intend to use in production. Test Administrator login, frontend navigation, templates, forms, email, user workflows, scheduled tasks, payment or API integrations, and other functions that matter to the site. Staging is where you want to discover that a plugin is incompatible—not halfway through the production update.

Run the Joomla Update component and let it finish

  1. Return to System → Update → Joomla.
  2. Recheck for updates if the displayed information may be stale.
  3. Review the final update information and backup acknowledgement.
  4. Start the update using Joomla's core update workflow rather than manually overwriting core files.
  5. Keep the browser request open while Joomla is actively processing unless Joomla itself tells you otherwise.
  6. Read the completion message before navigating away.

If the update stops with an error, capture the exact message and check the Joomla/PHP/server logs before retrying. Repeatedly starting the update without understanding a failure can make a partial-update state harder to diagnose.

Verify the update before deleting your rollback point

Confirm the installed Joomla version and then test the site as a user and as an administrator. Check several deep frontend URLs, Administrator pages, login/logout, editing and saving content, forms, email, media, and critical extensions.

Review System → Maintenance → Database and correct a Joomla core schema mismatch if Joomla reports one. Clear Joomla and external caches where appropriate, and review PHP/server logs for new warnings or fatal errors.

Keep the pre-update backup until the production site has passed these checks. If the update leaves the site seriously broken and the cause is not quickly understood, restoring the known-good recovery point is safer than stacking speculative fixes onto a partially upgraded site.


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.

Open a Support Ticket