Current vs Retired QCDR Features: Avoiding Obsolete Instructions

Current seven-tab UI and rendered-output workflows versus retired source-file editing, Count Only, JSON/XML/INI options, hidden legacy Email/Design/Text surfaces, old 3-day/automatic preview, and license-key activation wording.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to All plans; administrators. 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

Capture the exact affected URL, Rule/Token state, tier, and visible result before changing multiple settings.
Use Rule Health/Discovery evidence where available instead of guessing at origin or eligibility.
Never include license secrets, arbitrary PHP secrets, credentials, or private customer data in public support material.

Step-by-Step Workflow

Save the Rule first, even if it remains Draft or Disabled.
Confirm your Joomla account has Test Rules and the current tier includes private Preview.
Enter a same-site frontend URL that represents the intended Rule target.
Launch Preview from the Rule editor and inspect the private transformed page.
Read Rule Health for state/tier, target, audience, schedule, dependency, match, and protected-region gates.
Correct the Rule and relaunch Preview rather than enabling it just to test.
After successful private testing, enable the Rule only if ordinary runtime behavior is desired.

Seven-tab UI and rendered-output workflows versus retired source-file editing

QCDR operates on rendered Joomla frontend output. The package-owned System plugin observes eligible frontend HTML after Joomla has rendered it, builds request context, evaluates Rule gates, resolves eligible Token output, and transforms the response before it is sent to the browser. The PHP source Find type means PHP-like text that is present in rendered output; it is not a file editor and does not open, patch, or persist changes to .php files. Historical source-file configuration may remain stored for preservation, but new source-editing workflows are intentionally unavailable.

For Current vs Retired QCDR Features: Avoiding Obsolete Instructions, 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.

Count Only

JSON/XML/INI options

Hidden legacy Email/Design/Text surfaces

Old 3-day/automatic preview

How This Fits into QCDR

Troubleshooting should isolate one eligibility gate or runtime boundary at a time and preserve a known-good recovery path.

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

Status shows the expected Base and Effective tiers for the normalized domain.
Entitlement Revalidation is healthy and hourly unless the article is specifically diagnosing that task.
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

Treating rendered PHP-like text as permission to edit the PHP file that produced it.
Enabling a broad Rule for ordinary visitors merely to test something private Preview can validate safely.
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.