Install or Upgrade QCMM and Verify Version 2.0.21

Install the outer package over the existing installation, verify the component and task plugin versions, confirm 2.0.21, and preserve existing QCMM data and configuration.

This guide follows the accepted QC Memberships & Meetings 2.0.21 implementation and applies to All plans; administrator. This category establishes installation, entitlement, administrator navigation, permissions, update safety, and the first end-to-end membership test that every other QCMM workflow depends on. 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

• Take a current Joomla/site backup before installing, upgrading, changing component permissions, or making entitlement-related repairs.
• Confirm you can access Joomla Administrator, Extensions, Scheduled Tasks, and the frontend login/menu areas used by QCMM.
• Record the installed QCMM version plus the current Base tier and Effective tier before changing entitlement or task state.

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.

QCMM and Verify Version 2.0.21

Install the outer package over the existing installation, verify the component and task plugin versions, confirm 2.0.21, and preserve existing QCMM data and configuration 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.

Separate message definition from message delivery. Templates define content, recipients, Plan scope, and tokens; Joomla Mail transports messages; Scheduled Tasks handle unattended timing where required. A failure in one layer should not be “fixed” by changing the others indiscriminately.

Current Details That Matter

• QCMM 2.0.21 has five canonical Scheduled Tasks: Membership Transitions 5m, Lifecycle Automation 60m, Meeting Notifications 15m, Entitlement Revalidation 60m, and Resource Reservation Sync 5m.
• 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 establishes installation, entitlement, administrator navigation, permissions, update safety, and the first end-to-end membership test that every other QCMM workflow depends on. 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 Install or Upgrade QCMM and Verify Version 2.0.21, 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

• QCMM reports version 2.0.21 and the intended Base/Effective tier.
• The five canonical QCMM Scheduled Tasks exist and the Entitlement Revalidation task is structurally healthy at 60 minutes.
• Frontend menu routes open only for their intended Joomla access levels.
• A representative membership purchase/activation reaches Member Area and the expected Joomla groups without administrator-only shortcuts.

Common Mistakes to Avoid

• Using old instructions that ask customers to paste a current license key into Joomla instead of using Authorized Domains.
• Assuming install, page views, entitlement refresh, or Scheduled Tasks silently start the one-time Max Preview.
• Testing only as Super User and treating that as proof that normal members, Hosts, or Fulfillment Editors have correct access.
• Uninstalling before an ordinary upgrade instead of installing the current outer package over the existing installation.

Troubleshooting

• Reproduce the exact action with the same user role and record identifiers before changing unrelated configuration.
• If the UI and stored state disagree, refresh the real frontend after checking the owning record and relevant Scheduled Task.
• 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 a small regression checklist for Plans, checkout, Member Area, lifecycle tasks, billing, and any enabled Scheduling/Meeting features. Before a QCMM or Joomla update, maintain a current backup, record the installed versions and task state, and test with normal roles instead of relying only on Super User access.

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.