Understanding Updates That Are Not Available to Test

“Not available” means QCUL can display the update identity/target but the current metadata or laboratory state does not allow a safe Test in Lab action.

Common reasons

  • Joomla update metadata is incomplete or no longer selectable.
  • The package cannot currently be resolved/downloaded safely.
  • The target is a retained historical tested row rather than a currently selectable update.
  • The laboratory already has the target version or newer.
  • The row represents a type/state outside the current one-update-at-a-time workflow.

What to do

  1. Select Refresh Updates.
  2. Compare Live Site, Laboratory, and New Version.
  3. Check Joomla’s updater/update-site state if metadata is missing.
  4. If the lab already has the target, use the existing tested result or refresh/undo as appropriate rather than forcing another install.

Do not substitute packages

Not available is a safety state, not an invitation to upload a random ZIP. QCUL’s production promise depends on capturing and later reusing the exact package associated with the laboratory test.

Keep the evidence chain intact

The value of Understanding Updates That Are Not Available to Test depends on preserving one traceable transition: known starting version, one selected update, exact captured package/hash, resulting laboratory version, automated evidence, and human review. Avoid manual package installs or unrelated lab changes that make that chain ambiguous before a production decision.

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.