Create Basic Plain-Text Tokens in QC Dynamic Replacer

Plain text is the Basic-tier QCDR Token output type. Use it for reusable labels, phone numbers, short notices, codes, or other values that should be displayed as text rather than interpreted as HTML.

QCDR escapes plain-text output before inserting it, making this the safest choice when you do not need markup, an image, a link, Joomla dynamic data, or executable PHP.

Create a Plain-Text Token

  1. Open Components > QC Dynamic Replacer > Tokens and select Create Token.
  2. Enter a stable Token name and Friendly name.
  3. Leave Status as Draft while testing.
  4. Choose Plain text for Output type.
  5. Enter the reusable value in Token content or configuration.
  6. Save, place the placeholder on a controlled frontend page, and enable it after verification.

What Plain Text Does with Markup

Plain-text output is HTML-escaped by the runtime. If the value contains markup such as <strong>Important</strong>, QCDR does not treat that value as administrator-authored HTML. Choose the Pro-tier HTML or formatted content output type when rendering markup is intentional.

Basic vs. Nested Tokens

A simple independent plain-text Token is Basic. If its saved value embeds another QCDR Token reference, the configuration becomes a nested Token and requires at least Pro. It also inherits any higher tier required by the referenced Token.

For a Basic deployment, keep the plain-text value self-contained rather than composing it from other Tokens.

Targeting Can Raise the Requirement

Page/menu/URL targeting can remain Basic. Adding Pro features such as extension targeting, audience targeting, or scheduling raises the Token’s required tier. Adding Max IP rules or technical conditions raises it to Max. The library’s plan-lock indicator reflects the complete saved configuration.

Good Uses for Plain Text

  • A support phone number or office-hours string.
  • A reusable product label or short disclaimer.
  • A campaign code or version label.
  • Text selected by a Rule as its replacement value.

Do not use a plain-text Token where you specifically need a safe URL/attribute value or rendered markup; choose the purpose-built output type instead.

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.