Navigate the QCDR Tokens Library

Token Library layout, filters, drag organization, status cycling, reference counts, row actions, plan-lock badges, and current Live Processing control.

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

Open Tokens and select the reusable Token.
Configure the Token value/output type and keep it in a safe state during testing.
Place the placeholder or connect it to a Rule on a controlled page.
Verify eligibility, dependencies, and tier on the real request.
Enable/live-test only after authored-content preservation and output are understood.

Current Token Capability Map

Token type	Plan	Typical use
Plain text	Basic	Names, labels, and reusable short messages.
HTML or formatted content	Pro	Trusted reusable formatted output.
Image or media	Pro	Joomla Media/external image, alt text, dimensions/class/loading/link.
Link / button / URL	Pro	Reusable destination with optional menu-item source and presentation.
Nested Tokens	Pro	Reuse supported Tokens inside another Token value.
Joomla content / dynamic data	Max	Request-time site, menu, user, article, module, custom-field, and URL/context values.
CSS	Max	Reusable CSS output.
JavaScript	Max	Reusable JavaScript output.
PHP code	Max + Manage PHP Tokens ACL	Server-side PHP whose captured output becomes the Token value; no sandbox.

Token Library layout

Rule Live Processing and Token Live Processing are independent controls in current QCDR. Turning Rule Live Processing off stops normal Rules while leaving eligible standalone Token resolution available. Turning Token Live Processing off preserves authored {token.name} placeholders and prevents Token-backed Rule replacements from resolving, but a direct-value Rule can still run if Rule Live Processing remains on. For emergency recovery, disable the smallest affected runtime path first; turn both off when you need all normal QCDR frontend transformations stopped while preserving saved configuration.

For Navigate the QCDR Tokens Library, 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.

Filters

Drag organization

Status cycling

Reference counts

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.
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.