QCMM Requirements Before Installation
Before installing QCMM 2.0.21, confirm the hard package prerequisites and the Joomla services needed by the workflows you intend to use. The installer performs explicit PHP, cryptography, and database-driver checks before installation proceeds.
A site can pass the package preflight yet still have incomplete email, Scheduled Task, payment, or Meeting behavior, so the operational checks below matter too.
Hard Installer Requirements
| Requirement | QCMM 2.0.21 requirement |
|---|---|
| PHP | PHP 8.1 or later. |
| OpenSSL | OpenSSL must support AES-256-GCM. |
| Database | MySQL or MariaDB. The installer rejects unsupported Joomla database drivers. |
| Joomla installation access | An administrator must be able to install/update the QCMM package and manage the component/task plugin. |
Joomla Services QCMM Relies On
- Joomla users, groups, access levels, sessions, and menu access for identity and site authorization.
- Joomla Mail for membership, Meeting, billing, and other QCMM notifications you enable.
- Joomla Scheduled Tasks for membership transitions, lifecycle automation, Meeting notifications, entitlement revalidation, and resource-reservation synchronization.
- A working frontend login/account experience so members, Hosts, and Fulfillment Editors can reach their intended workflows.
HTTPS and Browser Readiness
Use HTTPS for a production membership site, especially when PayPal checkout or native Meeting Room features are enabled. Meeting media also depends on normal browser media permissions and secure-browser behavior. PayPal funding options can additionally depend on browser/provider eligibility.
Authorized-Domain Connectivity
Current paid entitlement is keyless. Explicit Administrator refreshes and the Entitlement Revalidation task must be able to reach QuantaCade and complete the Authorized-Domain verification flow. Normal frontend page rendering uses the local signed snapshot instead of making that remote request.
Pre-Install Checklist
- Take a current site and database backup.
- Confirm PHP is 8.1+ and OpenSSL exposes AES-256-GCM.
- Confirm Joomla is using MySQL or MariaDB.
- Verify Joomla Mail and Scheduled Tasks work on the site.
- Confirm the production domain can use HTTPS and the frontend login flow is functional.
- If you already own a paid tier, make sure the site domain is present in the QuantaCade Authorized Domains area before expecting paid entitlement to resolve.
If Preflight Fails
Correct the server prerequisite instead of editing QCMM to bypass the check. A failed cryptography or database prerequisite affects security and storage assumptions used by the current implementation.
Community Discussion
Want to compare QCMM workflows or discuss how other Joomla site owners use this feature? Visit the QC Memberships & Meetings Community. For private support, account-specific entitlement or billing issues, or bug reports, use the QuantaCade support system.