QCDR Technical Condition Operators and All-vs-Any Logic

QCDR technical conditions support exact comparisons, substring tests, wildcard matching, and list membership. The Condition logic setting then decides whether every saved condition must pass or whether one passing condition is enough.

Supported Operators

  • equals / not_equals — exact value equality or inequality.
  • contains / not_contains — substring presence or absence.
  • starts_with / ends_with — compare the beginning or end of the current value.
  • matches — anchored wildcard matching; * matches any sequence and ? matches one character.
  • in / not_in — compare the current value(s) with a comma-separated expected list.

Case Behavior Matters

The matches wildcard implementation is case-insensitive. The direct equality, substring, prefix, suffix, and list comparisons use the values as supplied and are case-sensitive. Use the exact Joomla/request value when you are not using wildcard matching.

All Conditions Must Match

With All selected conditions must match, QCDR rejects the item when any configured condition is false. This is the right choice for a narrow intersection such as “article view AND English language AND GET request.”

Any Condition May Match

With Any selected condition may match, the condition gate passes when at least one configured condition is true. This is useful for alternate contexts, such as one of several menu IDs or hostnames.

If there are no technical conditions, this gate passes regardless of the All/Any selection.

List Comparisons and Joomla Groups

The in and not_in operators split the expected value on commas. A user_group:in:2,8 condition passes when at least one current Joomla group ID intersects that expected list. This technical condition is separate from QCDR’s higher-level Audience selector.

Troubleshooting Complex Logic

Test each condition independently before combining several with All/Any logic. For Rules, Rule Health can identify the technical-condition gate as a failure, but isolating one line at a time is the fastest way to find a wrong type, value, case, operator, or wildcard.

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.