Use Site and Request Data in QCDR Dynamic Tokens

QCDR's Max-tier Joomla dynamic-data builder can expose safe site/request context without custom PHP. These sources are evaluated for each eligible frontend request, so the same Token can produce a different URL, path, component, view, language, or hostname as visitors navigate the site.

The values come from QCDR's current Joomla request context; they are not copied into the Token when you save it.

Current Site and Request Sources

  • Site name: Joomla's current configured site name.
  • Current page URL: the current absolute page URL available to QCDR.
  • Current page path: the request path used by QCDR targeting/runtime context.
  • Current hostname: the current request hostname.
  • Current Joomla component: the active component identifier, such as com_content.
  • Current Joomla view: the active component view when Joomla provides one.
  • Current language tag: the language tag in the current request context.

Create a Request-Aware Token

  1. Create a Token and choose Joomla content / dynamic data.
  2. Under Site and request, select the source you need.
  3. Leave Output handling on Automatic unless the consuming location has a specific requirement.
  4. Apply page/audience/extension targeting if the request value should appear only in a narrow context.
  5. Save and test the Token on at least two routes where the expected value differs.

Automatic and URL-Safe Output

Automatic handling treats Current page URL as a URL value and ordinary site/request properties as escaped text. You can explicitly choose URL / attribute-safe output when a compatible consumer needs a safe URL-style value.

URL output is trimmed and rejected when it begins with an unsafe executable scheme such as javascript:, vbscript:, or data:. Plain-text handling strips markup and escapes the remaining value.

Examples

  • Use a Current language tag Token in reusable content that displays the active language code.
  • Use Current Joomla component/view Tokens while testing conditional frontend diagnostics for a narrow administrator-controlled audience.
  • Use Current page URL as a reusable destination/value when the consuming Rule or Token expects the visitor's current URL.
  • Use Site name to avoid copying the Joomla site title into multiple reusable content fragments.

Remember That Targeting Runs Too

The source may be available while the Token itself is not eligible. Status, plan tier, page/extension targeting, audience, schedule, IP rules, technical conditions, and nested dependencies are evaluated separately. A failed Token gate preserves authored content instead of forcing the request value into an unintended location.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.