Create HTML or Formatted Content Tokens in QCDR

Pro, Max, and All Access can create HTML or formatted content Tokens for reusable administrator-authored markup. Unlike Plain text, QCDR returns HTML Token content as markup, so use this output type only for content you trust and intentionally want the browser to render.

HTML Tokens are useful for small reusable blocks, formatted notices, badges, or other markup that would be awkward to duplicate in several locations.

Create an HTML Token

  1. Open Tokens and select Create Token.
  2. Enter the Token name and Friendly name, and keep it Draft during testing.
  3. Set Output type to HTML or formatted content.
  4. Enter the trusted markup in Token content or configuration.
  5. Save the Token and test its placeholder on a controlled frontend page.
  6. Enable it only after inspecting the resulting DOM/layout.

HTML Is Intentionally Not Escaped

The runtime returns HTML Token values directly instead of converting tags to visible text. That is the feature—not a sanitization layer. Restrict Token-management permission to trusted administrators and do not copy untrusted visitor input into an HTML Token.

Nest Other Tokens When Needed

An HTML Token can contain other QCDR placeholders. QCDR resolves those dependencies before formatting the outer output. Nested references require at least Pro and the outer Token inherits the highest plan requirement of its dependencies.

Circular or excessively deep references are stopped safely rather than allowed to recurse indefinitely.

Know Where a Direct Placeholder Can Resolve

When you type an HTML Token placeholder directly into page content, standalone Token scanning is deliberately conservative. It scans eligible visible rendered output but skips HTML tag/attribute markup and normally protected script, style, code, form, comment, and similar regions. The resolved Token may produce markup at the eligible placeholder location.

If you need to transform a specific technical fragment already present in rendered HTML, create a Rule and use the HTML Token as its replacement instead.

Test Layout and Caching

Because one HTML Token can be reused across many locations, validate responsive layout, accessibility, and any CSS-class dependencies on representative pages. If the Token has visitor-specific targeting, also review Joomla/CDN caching so one audience’s generated HTML is not served to another.

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.