How QCTNH Uses Joomla's Correct SEF or Non-SEF WebCron URL
QCTNH does not hard-code one WebCron path. It asks Joomla’s router for the current native route so SEF URLs, URL rewriting, and Joomla subdirectories are respected.
How the route is built
The local service starts from the core AJAX target index.php?option=com_ajax&plugin=RunSchedulerWebcron&group=system&format=json and uses Joomla Route::link() to generate the site URL.
Accepted server-side route shapes
| Mode | Accepted shape |
|---|---|
| Non-SEF | The Joomla base path plus /index.php, with option=com_ajax, plugin=RunSchedulerWebcron, group=system, and format=json. |
| SEF | The Joomla base path plus /component/ajax or /index.php/component/ajax, with the same plugin/group/format query values. |
Why this matters
If Joomla is installed in a subdirectory, that path is part of both the registered origin and expected WebCron route. QCTNH therefore works with https://example.com/joomla as a distinct origin instead of assuming the site lives at the domain root.
Use Joomla’s own evidence
When validating How QCTNH Uses Joomla's Correct SEF or Non-SEF WebCron URL, compare QCTNH with Joomla’s Scheduled Tasks screen. The database next_execution, task enabled state, CLI-exclusive flag, registered task routine, and lock state are the facts QCTNH uses. If Joomla itself shows a task disabled, locked, or no longer backed by a routine, QCTNH should not pretend it is a normal WebCron candidate.
This source-first comparison is especially useful after uninstalling or upgrading an extension that previously registered Scheduled Tasks.
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.