Configure Plan Upgrade and Change Paths

Create, publish, and remove allowed Plan-to-Plan change paths so Member Area only offers intentional transitions while preserving existing subscription and billing history.

This guide follows the accepted QC Memberships & Meetings 2.0.21 implementation and applies to All plans; administrator. This category covers the membership catalog model: Plan Groups, Plans, publication, Joomla access assignment, customer-visible choices, and controlled paths between Plans. When older walkthrough or project-manual wording conflicts with 2.0.21 source or later accepted Authorized-Domain behavior, the current implementation takes precedence.

Before You Begin

• Decide which membership products are genuinely distinct Plans and which are better represented as durations, prices, or change paths.
• Identify the Joomla groups that should be granted by each Plan and confirm those groups do not accidentally grant unrelated administrative authority.
• Check current publication limits before publishing additional Plan Groups or Plans on Basic or Pro.

Current QCMM Behavior

Step-by-Step Workflow

1. Take a current backup and record the installed QCMM/package/task versions.
2. Install the current outer QCMM package over the existing installation using Joomla Extensions.
3. Confirm component and task-plugin installation completed without uninstall-side repair errors.
4. Open QCMM Status and verify version 2.0.21, entitlement state, and task registration.
5. Run the normal membership/frontend smoke test; do not uninstall first for a routine upgrade.

Plan Upgrade and Change Paths

Create, publish, and remove allowed Plan-to-Plan change paths so Member Area only offers intentional transitions while preserving existing subscription and billing history is part of the current QCMM 2.0.21 behavior. Treat the stored QCMM record and server-side authorization as authoritative: frontend controls guide the user, but QCMM still validates identity, ownership/access, current object state, entitlement, and request integrity when an action is submitted.

Keep the distinction between a reusable Plan definition and a purchased subscription snapshot. Administrators can improve or retire future catalog offers without rewriting the commercial and access context that belongs to an existing membership unless a dedicated migration/change workflow intentionally does so.

Current Details That Matter

• Current lifecycle behavior is preservation-first: ordinary upgrades install over the existing package and must not erase customer data/configuration.

How This Fits into QC Memberships & Meetings

This category covers the membership catalog model: Plan Groups, Plans, publication, Joomla access assignment, customer-visible choices, and controlled paths between Plans. A reliable QCMM configuration keeps Joomla authoritative for users, groups, access levels, sessions, mail transport, and Scheduled Tasks while QCMM owns Plan, subscription, billing, scheduling, Meeting, Custom Field, resource, and member-facing state.

For Configure Plan Upgrade and Change Paths, verify the behavior with the role that will actually use it. Administrator, member, Host, and Fulfillment Editor experiences intentionally differ. A successful test as Super User does not prove that a normal user has the correct ownership, access, timing, or feature entitlement.

Permissions, Entitlement, and Data Safety

• Joomla menu access, QCMM object ownership/access, role-specific permissions, and commercial feature entitlement are separate checks.
• QCMM re-authorizes state-changing requests server-side; never treat a visible or hidden frontend control as the security boundary.
• Do not expose PayPal credentials, encrypted settings, legacy keys, private room credentials, or other secrets in screenshots, URLs, public documentation, or community posts.
• Preserve subscription, billing, booking, attendance, Custom Field, credit, and entitlement history when correcting a problem; current QCMM is designed to repair in place rather than erase evidence.
• When Effective tier falls, premium configuration/history is preservation-first: features can become unavailable without deleting the saved data.

Verify the Result

• The Plan appears in the intended Plan Group and published catalog order.
• Plan Detail shows the expected price, duration, description, customer choices, and purchase/change actions.
• A test subscription receives only the intended Joomla groups and Plan-specific capabilities.
• Downgrade or temporary entitlement loss does not delete saved higher-tier Plan configuration.

Common Mistakes to Avoid

• Treating a hidden menu item as an access-control substitute for QCMM/Joomla authorization.
• Publishing more Plans or Plan Groups than the current tier permits and assuming saved data should be deleted.
• Changing a live Plan without considering existing subscription snapshots and historical billing context.
• Creating broad Plan-change paths that let customers move between offers that were not designed to be interchangeable.

Troubleshooting

• Check status, dates, predecessor/successor links, pending payment state, and lifecycle task results before editing the membership.
• Compare QCMM-managed Plan groups with unrelated manual/protected Joomla groups before changing user-group membership.
• Reproduce the exact action with the smallest safe test and record the user role, Plan/subscription/booking/billing identifiers, current state, and time zone where relevant.
• If a control is missing, check Joomla access, QCMM permission/ownership, record state, Effective tier, and task health before assuming packaged files are damaged.
• If behavior is asynchronous, inspect the owning Scheduled Task and its last result instead of repeatedly performing the business action.
• After a correction, rerun the same scenario from the real frontend; a successful Administrator save alone is not end-to-end verification.

Operational Best Practice

Keep the catalog understandable. Prefer a small number of clearly differentiated Plans, assign only the Joomla groups each Plan truly needs, and make customer change paths explicit. Before changing a live Plan, consider existing subscriptions, renewal behavior, and historical billing snapshots.

Community Discussion

Want to compare membership or Meeting workflows, share practical QCMM tips, or discuss how other Joomla site owners use this feature? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.