Duplicate, Reorder, Archive, and Delete QCDR Tokens

The QCDR Token Library includes maintenance tools for copying, organizing, retiring, and deleting reusable Tokens. These actions affect stored Token definitions differently, so use Draft or Archived states when you want reversibility and reserve Delete for a Token that is genuinely no longer referenced.

QCDR also tracks Token dependencies so it can block deletion while Rules or other Tokens still reference the Token.

Duplicate a Token Safely

Choose Duplicate on a Token row when you want to use an existing Token as a starting point. QCDR creates a new UUID, appends Copy to the Friendly name, creates a unique Token name based on the original name plus -copy, and forces the duplicate to Draft.

The duplicate carries the source Token's stored configuration, including its targeting, schedule, IP rules, technical conditions, and dependency references. Review all of those settings before enabling the copy. Duplicating a PHP Token additionally requires Max and the Manage PHP Tokens ACL.

Reorder the Token Library

Drag Token rows with the library handle to organize the list. Keyboard Up/Down reordering is also supported by the drag control. QCDR saves the complete Token ordering in increments of 10 and refuses a stale reorder submission if the library changed before the new order was saved.

Token ordering is primarily library organization. Tokens are resolved by their names and dependencies; do not use visual Token order as a substitute for explicit dependency design.

Archive a Token

Open the Token and set Status to Archived when you want to retain the definition but remove it from normal runtime use. Archived Tokens appear in the Archived library filter and do not enter the enabled runtime Token set.

The library bulk menu currently provides Enable, Disable, and Move to Draft. It does not provide a bulk Archive command, so archival is an intentional per-Token state change.

Check References Before Deleting

The Token Library displays reference/usage information derived from Rule and Token dependencies. Before deletion, replace or remove those references and save the dependent items.

If the Token still has dependencies, QCDR blocks deletion and reports how many Rule or Token references remain. This prevents an administrator from unknowingly removing a reusable value that active configuration still expects.

What Delete Removes

After the dependency count reaches zero, Delete permanently removes the Token row and its Token-owned schedule, technical conditions, IP rules, and dependency records in one database transaction. It does not search through arbitrary Joomla article text and remove literal placeholders that you typed into content.

Because deletion is permanent, use Archived when you are unsure whether the Token may be needed again. If a deleted/unknown placeholder still exists in authored Joomla content, QCDR has no Token value to substitute for it, so the authored placeholder remains visible.

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.