Understand the QCST Update Site and Protected Package Updates

This article explains the QuantaCade update-site record, package linkage, and why component/plugins update together without a pasted current license key.

Where this fits in QC Support Ticket

QCST is distributed as a Joomla package so the component and its packaged integration/task plugins advance together. The Status tab reports the installed version, available version, update-site state, last update check, and the Joomla upgrade action when an update is available and the current administrator has installer permission.

Current protected updates use the QuantaCade update service with Authorized-Domain entitlement rather than asking the site administrator to paste a license key into QCST.

Primary location: QC Support Ticket → Status and Joomla Administrator → System → Update / Install Extensions.

Package-shaped updates

  • QCST registers/uses the QuantaCade update-site/package relationship so Joomla updates the outer package rather than treating the component and bundled plugins as unrelated products.
  • Current update/download authorization follows the keyless Authorized-Domain model; users do not paste a current license key into the component to get normal updates.
  • After an update, validate the component version plus packaged task/privacy/user/content/finder/action-log/webservices integrations together.

Important behavior and limits

  • QCST 1.0.42 has five current Scheduled Tasks. Older SLA Automation and Webhook Delivery task types are retired.
  • Lazy Scheduler depends on site traffic. Server CRON is preferable when inbound mail or other time-sensitive work must run predictably.

Current-version note

This documentation is based on QC Support Ticket 1.0.42, the package currently deployed on the QuantaCade production site. The behavior described for Understand the QCST Update Site and Protected Package Updates should be checked against the current screen labels before applying instructions to an older QCST release.

Verify the result

  • The expected QCST routine exists once, is Published at the intended cadence, and completes without a repeated error state.

If it does not work as expected

  • If a due task does not run on a quiet site, verify server CRON rather than repeatedly changing the QCST interval.
  • For entitlement warnings, separate structural task health (missing/disabled/duplicate/slow) from temporary network/validation results.

Community Discussion

For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.