Use the QCDR Frontend Workspace Runtime Readiness Dashboard

Workspace title/introduction, Readiness/Rules/Tokens sections, stored/enabled counts, runtime-scope message, and distinction from Administrator editing.

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

• Plan least-privilege groups before assigning specialized QCDR actions.
• Remember that entitlement and Joomla permission are separate gates.
• Test with a non-Super-User account after ACL changes.

Step-by-Step Workflow

1. Identify the minimum QCDR action the user/group needs.
2. Configure Joomla ACL without granting unrelated entitlement/settings/code privileges.
3. Test with the delegated account rather than the Super User session.
4. Verify denial behavior for actions that should remain restricted.
5. Document the assigned group/action for later audits.

QCDR Joomla Permission Reference

Workspace title/introduction

Rule and Token state is a separate gate from targeting. Enabled items can participate in normal runtime processing when their tier and targeting also pass. Disabled and Archived items are preserved but excluded from live processing. Draft items remain easy to find under the All library filter so work-in-progress configuration does not disappear from view. Private Preview can test a saved Draft or Disabled Rule without making it live for ordinary visitors, which is the preferred path for risky changes.

For Use the QCDR Frontend Workspace Runtime Readiness Dashboard, 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.

Readiness/Rules/Tokens sections

Rule and Token state is a separate gate from targeting. Enabled items can participate in normal runtime processing when their tier and targeting also pass. Disabled and Archived items are preserved but excluded from live processing. Draft items remain easy to find under the All library filter so work-in-progress configuration does not disappear from view. Private Preview can test a saved Draft or Disabled Rule without making it live for ordinary visitors, which is the preferred path for risky changes.

For Use the QCDR Frontend Workspace Runtime Readiness Dashboard, 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.

Stored/enabled counts

Rule and Token state is a separate gate from targeting. Enabled items can participate in normal runtime processing when their tier and targeting also pass. Disabled and Archived items are preserved but excluded from live processing. Draft items remain easy to find under the All library filter so work-in-progress configuration does not disappear from view. Private Preview can test a saved Draft or Disabled Rule without making it live for ordinary visitors, which is the preferred path for risky changes.

Runtime-scope message

Rule and Token state is a separate gate from targeting. Enabled items can participate in normal runtime processing when their tier and targeting also pass. Disabled and Archived items are preserved but excluded from live processing. Draft items remain easy to find under the All library filter so work-in-progress configuration does not disappear from view. Private Preview can test a saved Draft or Disabled Rule without making it live for ordinary visitors, which is the preferred path for risky changes.

And distinction from Administrator editing

Rule and Token state is a separate gate from targeting. Enabled items can participate in normal runtime processing when their tier and targeting also pass. Disabled and Archived items are preserved but excluded from live processing. Draft items remain easy to find under the All library filter so work-in-progress configuration does not disappear from view. Private Preview can test a saved Draft or Disabled Rule without making it live for ordinary visitors, which is the preferred path for risky changes.

How This Fits into QCDR

The frontend Workspace is a readiness/status surface. Rule and Token editing remains an Administrator workflow.

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

• The Rule state and drag order are exactly what you intended.
• A page that should match changes as expected, and a page outside scope remains unchanged.
• The Token resolves where it is eligible and preserves authored content where it is intentionally unavailable.
• Reference/dependency behavior is understood before deleting or downgrading a Token.
• The delegated user can perform only the intended QCDR actions.
• The same user is denied actions that were intentionally withheld.
• Reload the real frontend request instead of relying only on the saved Administrator form.

Common Mistakes to Avoid

• Assuming an unavailable Token should become an empty string; QCDR often preserves the original placeholder or Rule match intentionally.
• 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.