What Happens During Production Extension and Core Installation

Production installation uses Joomla’s installer path appropriate to the tested update type and is driven from an immutable record of the exact laboratory-tested item.

Extension push

QCUL copies the exact tested ZIP to Joomla temporary storage, re-verifies SHA-256, and uses Joomla Installer to apply the extension/package update on the live root/database.

Joomla core push

QCUL uses its dedicated core adapter for the captured core package and Joomla core finalization/cleanup, then reads the actual Joomla manifest version.

Common production sequence

1. Acquire operation ownership/locks and confirm readiness.
2. Create/validate temporary checkpoint when selected.
3. Manage site availability if required.
4. Install exact tested package.
5. Verify resulting version.
6. Run production route/validation checks.
7. Restore original availability state.
8. Keep the tested row/report/undo state visible for administrator review.

Production change rule

For What Happens During Production Extension and Core Installation, the live site should change only through the explicit tested-item production workflow after current readiness checks pass. Do not substitute a new package, skip the review/protection decision, or run a second production action while QCUL already owns an active push/rollback state.

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.