Legacy QCDR Token Output Types and Preserved Historical Records

QCDR 1.1.05 no longer offers four historical Token output types for new selection: Structured data / JSON, XML, INI / language value, and HTML attribute value. Current Token creation should use the supported output types shown in the editor instead.

Upgrades do not silently rewrite old Token rows. A historical Token can remain stored with its legacy type so administrators can review and migrate it deliberately.

Current vs. Retired Output Types

The current Token editor offers Plain text, HTML or formatted content, Image or media, Link or button, Joomla content / dynamic data, CSS, JavaScript, PHP code, and URL link.

The retired types—structured_data, xml, ini, and attribute—are not available when creating a new Token or changing another Token to a new output type.

How an Existing Legacy Token Appears

When you edit a Token that already stores a retired output type, QCDR shows a Legacy output type — no longer available selection. Saving unrelated fields can preserve the historical output type and its existing Token value rather than silently converting the record to Plain text.

This behavior is for compatibility and controlled migration. It does not make the retired type a recommended current workflow.

Runtime Compatibility Is Conservative

The 1.1.05 runtime still contains compatibility formatting for historical rows. INI/XML-style values are escaped as text, attribute values are attribute-escaped, and a valid historical structured-data value can be emitted as JSON in a JSON target or as an application/ld+json script in ordinary output.

Because retired output types are no longer assigned a current lower-tier feature mapping, QCDR treats preserved legacy types conservatively as Max-level for eligibility. A downgrade can therefore leave the record stored while preventing it from running.

Migrate Instead of Building New Dependencies

  1. Identify where the legacy Token is referenced before changing it.
  2. Create a new current Token type that produces the value you actually need.
  3. Test the new Token in the same page, Rule, audience, and target context.
  4. Replace dependent references with the new Token and save them.
  5. Archive the legacy Token for a review period or delete it only after its dependency count reaches zero.

Do Not Recreate Retired Workflows Manually

A legacy database value is not proof that the current UI supports a new JSON/XML/INI/attribute workflow. Avoid hand-editing QCDR database rows to force a retired type into a new Token. Use a current Token output type or an explicit rendered-output Rule that matches the current product model.

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.