Use Current Joomla Article Data in QCDR Tokens

QCDR Max/All Access Joomla data Tokens can read the article that owns the current frontend content request. Instead of copying an article value into the Token, QCDR resolves the current article at request time and can return its ID, title, alias, intro text, full text, or a custom-field value.

The provider is access-aware. If the current request does not identify an eligible published Joomla article, the dynamic value is unavailable and QCDR preserves the authored Token placeholder or the original text of a dependent Rule.

Available Current-Article Sources

When the Token output type is Joomla content / dynamic data, the Current Joomla article group provides:

  • Current article ID
  • Current article title
  • Current article alias
  • Current article intro text
  • Current article full text
  • Current article custom field value

QCDR gets the current article ID from the frontend request context. This is intended for requests where Joomla has identified a content article; it is not a search for the most recent article or a fallback to an arbitrary record.

Create a Current-Article Token

  1. Open Components > QC Dynamic Replacer > Tokens and create or edit a Token.
  2. Choose Joomla content / dynamic data as the output type.
  3. Under Joomla data source, choose the required Current Joomla article property.
  4. If you choose Current article custom field value, enter the Joomla field ID or its machine name. Do not use the visible field label.
  5. Choose the required Output handling, save the Token, and test it on an actual article route that the intended visitor can access.

Publication and Access Checks

QCDR reads the article only when it is published, within its publish-up/publish-down window, and assigned to a Joomla Access level available to the current visitor. Its content category must also be published and accessible to that visitor.

A custom field has its own check: the field must be a published com_content.article field whose Access level is available to the visitor. QCDR then reads the stored field value for the current article.

Choose Output Handling Deliberately

Automatic treats the article ID, title, and alias as escaped text. It treats intro text, full text, and custom-field values as HTML-capable sources. If a custom field should always display as literal text even when its stored value contains markup, choose Plain text instead.

Use HTML / formatted content only when you intend stored article or field markup to enter the rendered page. QCDR reads the stored value; it does not run a second Joomla content-rendering pipeline for that field or article fragment.

When the Token Does Not Resolve

The provider is unavailable when there is no current article ID, the article/category is unpublished, a publication date excludes it, the visitor lacks the required Access level, or a requested field is unavailable. In those cases, a standalone authored placeholder remains unchanged and a Rule that depends on the Token leaves its original matched content in place.

Test the Exact Visitor Context

Test the same article as a guest and as any relevant logged-in group when Access levels differ. Also test alternate menu routes if they can lead to a different Joomla request context. Dynamic data is resolved from the request that actually reaches QCDR, not from what an administrator assumes the page represents.

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.