Moving Joomla Into or Out of a Subdirectory

Moving Joomla into or out of a subdirectory changes the native WebCron route and the QCTNH origin path, so the final path must be explicitly registered.

Examples

Moving from https://example.com/ to https://example.com/joomla/, or the reverse, changes the base path used when Joomla builds its WebCron route. QCTNH’s local origin comparison also includes the path.

Procedure

  1. Complete the Joomla move and confirm frontend/administrator routing at the final base path.
  2. Open QCTNH from the final canonical URL.
  3. Run Check WebCron so the component rebuilds the native Joomla WebCron route from Joomla routing rather than a hard-coded URL.
  4. Run Test Connection to explicitly adopt the changed origin/path.
  5. Verify the Dashboard’s WebCron readiness and connection state.

Why manual endpoint editing is not recommended

QCTNH intentionally derives the route from Joomla, supporting SEF and non-SEF layouts such as /component/ajax, /index.php/component/ajax, or the non-SEF /index.php?option=com_ajax... form. Let Joomla/QCTNH generate the path.

Use Recent Activity as migration evidence

For Moving Joomla Into or Out of a Subdirectory, QCTNH records useful origin lifecycle events. An unconfirmed different origin can produce origin_mismatch_ignored; an explicit accepted move can produce origin_changed_confirmed, followed by registration/synchronization results.

These events are safer evidence than guessing from a stale Connected badge after a restore or clone.

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.