Troubleshoot a QCBM Update That Is Not Discovered

QCBM uses Joomla's package update system. When a release you expect is not discovered, distinguish update-site discovery from update installation: first confirm Joomla has the correct QCBM package update-site relationship, then force a discovery check.

Do not reinstall the extension or change entitlement settings until you know which part of the update path is actually failing.

Check the Extension Update Card

Open QC Backup Manager → Status and find Extension Update. Record Installed version, Available version, Update site, and Last checked.

If the card says Update site needs attention, fix update-site configuration before assuming the QuantaCade release feed is missing.

Use Check for Updates

Select Check for Updates on the QCBM Status tab. This asks Joomla to refresh QCBM update discovery and then re-reads Joomla's update state.

If a newer package is discovered, the card changes to Update available. Administrators with Joomla Extension Manager permission can then use Upgrade QC Backup Manager.

Understand What Update Delivery Readiness Checks

The Update Delivery Readiness Card checks QCBM's package-owned Joomla update wiring. Current QCBM expects one matching enabled update site associated with the QCBM package, not a stray component-only association.

The card also checks update identity. In the current keyless model, an installation with no saved legacy license key is already considered ready for keyless update identity; a missing old key is not itself an update-discovery error.

Basic Entitlement Does Not Explain Missing Discovery

QCBM's package updater and feature entitlement are separate concerns. Falling back to Basic can lock paid features, but it should not be used as the explanation for a malformed/missing Joomla update-site association.

Troubleshoot the update feed in Status/Update Delivery and troubleshoot Authorized Domain entitlement in Current Entitlement. Do not mix the two diagnostic paths.

Check Joomla Permissions for Installation

Discovery and installation are also different. A user may be able to see update information but lack com_installer management permission. QCBM explicitly requires Joomla Extension Manager permission before it shows the package-upgrade action.

If the update is discovered but cannot be installed, solve the permission or installer problem rather than continuing to troubleshoot discovery.

If the Update Site Still Needs Attention

Open Joomla's update-site/extension-management tools and look for disabled, duplicated, stale, or incorrectly associated QCBM update-site records. QCBM's Readiness Card reports counts for matching sites, enabled sites, package associations, and component associations to help identify the mismatch.

Use the current QCBM package as the authority if update-site registration itself is damaged. Installing the current package over the existing installation can restore package-owned updater metadata without deleting QCBM data, but first preserve the diagnostic evidence so you know why the repair was needed.

Separate Discovery Failure from Download/Install Failure

If Available version shows the expected release, discovery is working. A later HTTP/download/signature/installer error is a different problem and should be diagnosed from Joomla's installer message.

If no release is shown after a successful check and Update Delivery is healthy, compare the installed version with the release you expect and capture the update endpoint/status details before escalating.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.