How Extension and Joomla Core Production Protection Differ

QCUL uses a narrower evidence-informed checkpoint for extension updates and a deliberately broader database scope for Joomla core updates.

Extension checkpoint

Protects complete affected tables derived from laboratory-observed database scope and affected files. If the observed database scope is uncertain, QCUL can fall back broader rather than risk an incomplete rollback.

Joomla core checkpoint

Protects all Joomla-prefixed production tables plus the affected core-file scope. Core updates can alter central schema/runtime assets that are not safely represented by one extension identity.

Both remain operation-scoped

Neither is a general site backup. Non-Joomla databases, arbitrary external systems, remote APIs, and every unrelated file are outside the promise of the QCUL checkpoint unless they are part of the protected update scope.

Recovery discipline

When working with How Extension and Joomla Core Production Protection Differ, keep the independent backup available even if the QCUL checkpoint is valid. The checkpoint is a fast, short-lived update rollback mechanism; if its protected scope, validity window, or verification cannot satisfy the incident, move to the broader recovery plan rather than extending QCUL beyond its promise.

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.