How QCTNH Chooses and Stores the Registered Site Origin

QCTNH derives the current site origin from Joomla’s live root URL and stores the registered canonical origin as part of clone/migration protection.

Origin format

The local origin includes scheme, lowercase hostname, any non-default port, and Joomla base path with the trailing slash removed. Only HTTP and HTTPS are accepted. Normal web requests use Joomla Uri::root(); the same-server post-run CLI helper can supply the already registered origin explicitly because a CLI process has no reliable browser request context.

Local equivalence rule

For clone protection, QCTNH treats www.example.com and example.com as the same host, but scheme and Joomla base path must still match. Non-standard ports are not considered equivalent by the migration-comparison helper.

Why origin is stored

If a copied database is opened on a different hostname/path, QCTNH sees that the current origin differs from the registered origin and blocks automatic identity rotation. The copy cannot silently replace the original site’s wake-up registration.

Identity and timing are both required

For How QCTNH Chooses and Stores the Registered Site Origin to work safely, QuantaCade needs both a valid registered identity/endpoint and useful scheduler timing. A perfectly known next-due time is not enough if the site origin or WebCron credential is invalid; a perfect connection is not enough to schedule intelligently if Joomla has no eligible task timing.

Test Connection focuses on identity/public reachability, while task-change/WebCron-completion check-ins keep operational timing current.

Community Discussion

Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.