Create and Name a Reusable QCDR Token

Token-name syntax, friendly name, description, state, output type, save/enable flow, and the {token.name} placeholder format.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to All plans; token managers. Where older manuals or walkthrough wording differs from the current source or the accepted keyless-entitlement behavior, the current implementation takes precedence.

Before You Begin

• Use a stable lowercase Token name and understand where the placeholder will appear.
• Keep new or high-impact Tokens Draft/Disabled until tested.
• Check dependency and tier requirements before nesting Tokens.

Step-by-Step Workflow

1. Open Tokens and choose Create Token.
2. Enter a stable Token name beginning with a letter and using lowercase letters/numbers/dots/underscores/hyphens.
3. Add a Friendly name/description and keep the Token Draft or Disabled while building.
4. Choose the output type and configure its purpose-built fields.
5. Add targeting/schedule/technical gates only when the use case requires them.
6. Save and test the {token.name} placeholder on a controlled frontend page.
7. Enable the Token after output, targeting, tier, and dependency behavior are verified.

Current Token Capability Map

Token-name syntax

QCDR Tokens centralize reusable runtime values under placeholders such as {token.name}. The same Token can be authored directly in eligible frontend content or selected as a Rule replacement source; there is no separate “standalone Token” versus “Rule Token” object. Token targeting and tier gates still apply in both uses. If a Token is Disabled, Draft, Archived, plan-locked, outside its target, or blocked by an unavailable dependency, QCDR deliberately preserves the authored placeholder or original Rule match instead of silently producing an unexpected blank.

For Create and Name a Reusable QCDR Token, evaluate this against the exact frontend request that matters. A saved QCDR item can be valid in Administrator yet remain inactive because a different eligibility gate, dependency, permission, cache layer, or runtime safety boundary correctly prevents transformation. Keeping those concerns separate makes both testing and later support much easier.

Friendly name

QCDR Tokens centralize reusable runtime values under placeholders such as {token.name}. The same Token can be authored directly in eligible frontend content or selected as a Rule replacement source; there is no separate “standalone Token” versus “Rule Token” object. Token targeting and tier gates still apply in both uses. If a Token is Disabled, Draft, Archived, plan-locked, outside its target, or blocked by an unavailable dependency, QCDR deliberately preserves the authored placeholder or original Rule match instead of silently producing an unexpected blank.

For Create and Name a Reusable QCDR Token, evaluate this against the exact frontend request that matters. A saved QCDR item can be valid in Administrator yet remain inactive because a different eligibility gate, dependency, permission, cache layer, or runtime safety boundary correctly prevents transformation. Keeping those concerns separate makes both testing and later support much easier.

Description

QCDR Tokens centralize reusable runtime values under placeholders such as {token.name}. The same Token can be authored directly in eligible frontend content or selected as a Rule replacement source; there is no separate “standalone Token” versus “Rule Token” object. Token targeting and tier gates still apply in both uses. If a Token is Disabled, Draft, Archived, plan-locked, outside its target, or blocked by an unavailable dependency, QCDR deliberately preserves the authored placeholder or original Rule match instead of silently producing an unexpected blank.

State

QCDR Tokens centralize reusable runtime values under placeholders such as {token.name}. The same Token can be authored directly in eligible frontend content or selected as a Rule replacement source; there is no separate “standalone Token” versus “Rule Token” object. Token targeting and tier gates still apply in both uses. If a Token is Disabled, Draft, Archived, plan-locked, outside its target, or blocked by an unavailable dependency, QCDR deliberately preserves the authored placeholder or original Rule match instead of silently producing an unexpected blank.

Output type

QCDR Tokens centralize reusable runtime values under placeholders such as {token.name}. The same Token can be authored directly in eligible frontend content or selected as a Rule replacement source; there is no separate “standalone Token” versus “Rule Token” object. Token targeting and tier gates still apply in both uses. If a Token is Disabled, Draft, Archived, plan-locked, outside its target, or blocked by an unavailable dependency, QCDR deliberately preserves the authored placeholder or original Rule match instead of silently producing an unexpected blank.

How This Fits into QCDR

Tokens are reusable runtime values. When a Token is unavailable, QCDR intentionally preserves authored content rather than silently erasing it.

The safest operating pattern is to keep configuration narrow, use QCDR’s private diagnostics before broad activation when your tier permits them, and preserve Joomla Administrator as the recovery surface. Because QCDR changes the rendered response rather than source files, a correctly disabled or bypassed runtime path should expose the underlying Joomla output again without requiring a source-file rollback.

Verify the Result

• The Token resolves where it is eligible and preserves authored content where it is intentionally unavailable.
• Reference/dependency behavior is understood before deleting or downgrading a Token.
• Reload the real frontend request instead of relying only on the saved Administrator form.
• Check Joomla/CDN cache effects if the result is request-specific.

Common Mistakes to Avoid

• Assuming an unavailable Token should become an empty string; QCDR often preserves the original placeholder or Rule match intentionally.
• Trusting forwarded client-IP headers without restricting which proxy/CIDR is allowed to supply them.
• Changing several gates at once during troubleshooting, which makes the actual cause difficult to identify.
• Testing only while signed in as Super User when ordinary users/guests are the intended audience.
• Skipping a recovery plan before enabling a site-wide HTML, JavaScript, protected-area, or PHP-backed change.

Troubleshooting

• If nothing changes, confirm the package-owned System plugin is enabled, the relevant Live Processing switch is on, and the item is eligible for the current Effective tier.
• If targeting appears wrong, inspect page/menu/URL, extension, audience, schedule, IP, technical conditions, and protected-region behavior as separate gates.
• If a Token-backed Rule preserves the original match, troubleshoot the Token dependency/readiness before changing the Find value.
• If behavior differs between browsers/users, clear or bypass relevant Joomla/full-page/CDN caches and compare request context.
• If private Preview/Discovery fails, start a fresh authorized same-site session and confirm the Joomla ACL action as well as the product tier.

Operational Best Practice

Make runtime changes deliberately: use a narrow scope first, keep broad Rules Draft or Disabled until tested, preserve the independent Rule/Token emergency switches, and record the QCDR version plus the exact Rule/Token and affected URL when handing a problem to another administrator. For high-impact HTML, protected-region, JavaScript, dynamic-data, or PHP work, test representative anonymous and authenticated requests and review caching before expanding scope.

Community Discussion

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