How to Update Joomla Extensions
Joomla can update third-party extensions that publish compatible update information through Joomla's update system. An extension update may replace files, run installer scripts, and change database tables, so treat it as a real application change: back up first, review the vendor's requirements, install deliberately, and verify the extension afterward.
Back up and review the extension before updating
Create a current files-and-database backup before updating production, especially for components or plugins that handle authentication, payments, forms, security, scheduled tasks, or important site data.
Check the extension developer's release notes and upgrade instructions. Confirm that the proposed version supports your installed Joomla and PHP versions and whether the developer requires an intermediate release, migration step, new download key, or other preparation.
For a large version jump or a business-critical extension, test the update on staging before production.
Open Extensions Update and refresh the list
- Go to System → Update → Extensions.
- Use Find Updates to query the configured extension update sites again when you want fresh results.
- Locate the extension you intend to update and compare its installed and available versions.
- If an expected extension is missing, do not assume it is current; check its update site and the developer's website.
Only extensions that support Joomla's update mechanism can appear in this screen. Commercial products may also require a download key or subscription before Joomla can retrieve the package.
Install the update deliberately
- Select the checkbox for the extension update you have reviewed.
- Choose Update from the toolbar.
- Wait for Joomla to download and install the package.
- Read the installer result and any extension-specific post-installation messages before leaving the page.
Although Joomla can update multiple extensions, updating one critical product at a time makes failures easier to isolate. Products from the same vendor may need to be updated as a package or in a documented order, so follow the vendor's instructions rather than assuming bulk update is always safe.
Verify the installed version and the extension's real workflow
After the update, go to System → Manage → Extensions or the extension's own dashboard and confirm the installed version. Then test the functions the extension actually provides.
- For a form extension, submit a test form and verify notifications.
- For an authentication extension, test login/logout using an account that will not lock you out of Administrator.
- For ecommerce or payment software, test in the provider's safe/test mode where available.
- For a scheduled-task extension, verify its task definitions and a safe test execution.
- For a template or page builder, inspect representative frontend pages at multiple viewport sizes.
Review Joomla/PHP logs and the browser console if the extension behaves differently after the update.
If the extension update fails, preserve the error before retrying
Capture the exact error message and determine whether Joomla failed while finding the package, downloading it, extracting files, writing files, running database changes, or executing the extension's installer script.
Do not repeatedly click Update after an unexplained failure. Check the vendor's recovery instructions and the Joomla/PHP/server logs. If the update may have partially changed both files and database and the correct recovery path is uncertain, restore the known-good pre-update backup rather than manually mixing old and new extension files.
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.