Troubleshooting an Update That Does Not Appear in Test Updates

Troubleshooting an Update That Does Not Appear in Test Updates starts by identifying which QCUL stage or safety gate is actually failing; the fix should address that layer rather than bypassing the protection.

Likely causes

  • Joomla may not currently offer the update through its updater metadata.
  • The update list may need Refresh Updates.
  • QCUL intentionally excludes its own active update.
  • Language updates may be hidden by the UI filter.

Troubleshooting procedure

  1. Select Refresh Updates.
  2. Clear Hide Joomla language file updates when relevant.
  3. Check Joomla Update/Extensions update sites and metadata outside QCUL.
  4. Confirm the item is a supported Joomla core or extension/package update.

Verify before production

After resolving Troubleshooting an Update That Does Not Appear in Test Updates, the selected update should return to a clear testable/completed state with exact package/version evidence. Open the lab and report again; do not proceed to production while the test remains failed, ambiguous, or based on a damaged/stale laboratory state.

Capture evidence before changing more things

While troubleshooting Troubleshooting an Update That Does Not Appear in Test Updates, preserve the exact displayed state/error and relevant report/task/log evidence before reinstalling, refreshing, removing, or manually editing data. QCUL’s state machine is designed to make failed work diagnosable; changing several layers at once can erase the evidence that identifies the real cause.

Community Discussion

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