Pushing a Tested Joomla Core Update to Production Step by Step

A Joomla core production push follows the same exact-package/readiness model as an extension push but protects and validates a much broader Joomla database/file/runtime surface.

Step-by-step procedure

  1. Complete a wider Joomla core review in the laboratory and verify a successful Undo Lab Update/retest cycle.
  2. Confirm production still reports the exact expected starting Joomla version.
  3. Choose production protection; a QCUL core checkpoint protects all Joomla-prefixed tables plus the affected core-file scope.
  4. Select Push to Production and keep the page open.
  5. After installation, confirm the Joomla version in System Information and review frontend/admin templates, login, menus, editing, forms, mail, cache, extensions, and Scheduled Tasks.
  6. Use Review Live Site and retain the final report; rollback within the configured window if necessary.

Core checkpoint scope

When temporary QCUL protection is selected for a core update, the checkpoint protects all Joomla-prefixed production tables plus the affected core-file scope. This is intentionally broader than an extension checkpoint derived from observed update changes.

Production change rule

For Pushing a Tested Joomla Core Update to Production Step by Step, 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.