Joomla Content and Dynamic Data Tokens in QC Dynamic Replacer

Max and All Access installations can create Joomla content / dynamic data Tokens that read Joomla information at request time. Instead of copying a title, user name, menu value, article body, custom field, or module value into the Token, QCDR stores a structured source configuration and reads the current permitted Joomla record when the Token resolves.

This makes the Token useful for values that should follow Joomla automatically, while QCDR still respects publication state and the current visitor's Joomla access levels.

Create a Joomla Data Token

  1. Open Tokens and create a new Token.
  2. Choose Joomla content / dynamic data for Output type. This output type requires Max-level QCDR access.
  3. Choose a Joomla data source.
  4. If the source targets a specific article, module, or menu item, enter the required Joomla ID. For article custom fields, enter the field ID or machine name.
  5. Choose Output handling: Automatic, Plain text, HTML / formatted content, or URL / attribute-safe value.
  6. Configure normal Token targeting, save, and test the Token in the frontend context where it will be used.

Available Source Groups

QCDR 1.1.05 groups the builder into these current source families:

  • Site and request: site name, current URL/path/hostname/component/view/language.
  • Current menu item: current menu ID, title, alias, and QCDR-generated menu link.
  • Current user: authenticated user ID, display name, and username.
  • Current Joomla article: ID, title, alias, intro text, full text, and a custom field.
  • Specific Joomla article: title, alias, intro text, full text, or custom field by article ID.
  • Specific Joomla module: module title or stored module content by ID.
  • Specific Joomla menu item: menu title, alias, or link by ID.

Request-Time Access Checks

Specific/current articles must be published, within their publish window, in a published accessible content category, and visible at one of the current visitor's authorized view levels. Menu items and site modules must likewise be published, within their publish window, frontend records accessible to the visitor.

If the required record is not available to that visitor/request, the Token is unavailable. QCDR does not bypass Joomla access controls to obtain the value.

Choose the Output Handling Carefully

Automatic uses HTML for article bodies and stored module content, URL handling for current/menu links, and plain text for ordinary scalar values. Plain text strips tags and escapes the result. URL handling rejects unsafe executable schemes.

HTML output is accepted only for article body/custom-field sources and stored module content. QCDR enforces that restriction at save/runtime even if configuration is manipulated outside the normal editor.

Important Boundaries

Stored module content reads the module database record; it does not execute or recursively render the Joomla module. Current-user providers expose only ID, display name, and username—there are no current builder sources for passwords, session values, authentication tokens, or email addresses.

Because values are read when the page request is processed, later Joomla record changes can appear automatically without editing the Token itself.

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.