Troubleshoot a QCDR Token That Appears Literally as {token.name}

Seeing a literal QCDR placeholder such as {token.name} is often deliberate fail-safe behavior. QCDR preserves authored placeholders when a known Token cannot be used safely instead of replacing them with misleading or broken output.

Start with Token Live Processing

Open Tokens and confirm Token Live Processing is enabled. This switch controls standalone placeholders in rendered frontend content independently from Rule Live Processing.

If Token Live Processing is off, standalone placeholders remain authored. A direct-value Rule can still run, but a Rule that depends on a Token will remain unapplied when its replacement cannot resolve.

Confirm the Token Is Runtime-Eligible

  • The Token must be Enabled for ordinary live resolution.
  • The current Effective tier must include the Token's output type and any higher-tier targeting it uses.
  • Page/menu, component/module, audience, schedule, IP, and condition targeting must qualify where configured.
  • For Joomla-data Tokens, the selected record must exist, be published/available, and pass the current visitor's Joomla view levels.
  • For PHP Tokens, Max access and the Token's runtime conditions must still be available.

Check Nested Dependencies

A Token can reference other QCDR Tokens. Nested use requires at least Pro and inherits the highest dependency tier. QCDR also detects dependency cycles and limits runtime Token nesting to eight levels.

If a nested dependency cannot resolve, the outer Token is not allowed to silently fabricate a result. Correct the missing/locked/out-of-target dependency and retest.

Distinguish an Unknown Placeholder from an Unavailable Known Token

QCDR loads stored Token names so it can recognize known placeholders even when those Tokens are not currently eligible. Known-but-unavailable placeholders are intentionally preserved. This makes an entitlement downgrade, Disabled state, targeting miss, or runtime failure visible and reversible instead of destroying authored content.

For PHP Tokens, Check the Error Policy

With Hide PHP errors, a PHP failure returns QCDR's internal unresolved result and the placeholder remains unchanged. With Show sanitized PHP errors, a safe diagnostic can be rendered instead. A PHP Token that successfully returns an empty string is different: empty output is a valid success and removes the placeholder.

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.