What to Include in a QCMM Support Request

Include version/environment, affected record identifiers, timestamps/time zone, task/payment/browser context, and exact reproduction steps in a QCMM support request while withholding secrets.

Identify the Exact Build

Include the installed QCMM/package version (for this documentation baseline, 2.0.21), Joomla version, PHP version, and whether the problem is administrator, frontend, Scheduled Task, Meeting, report, or payment related.

Provide Record Identifiers, Not Credentials

Include the affected Plan ID, subscription ID, booking/Meeting Time ID, billing/invoice ID, or payment reference where relevant. Do not send passwords, PayPal client secrets, encrypted settings, private Meeting credentials, license secrets, or full card/payment credentials.

Give Time and Task Context

Provide the approximate timestamp and site time zone. For asynchronous behavior, include the owning Scheduled Task name, last run/result/exit code, and next-run state if available.

Describe the Payment or Browser Context

For checkout issues, state Sandbox versus Live, funding option used, whether the provider flow opened/returned, and the local billing/payment status. For Meeting/media issues, include browser/device and whether authorization, lobby, or media permission was the failing stage.

Give Reproduction Steps and Expected Result

List the shortest repeatable sequence, the user role, what you expected, what actually happened, and whether it reproduces with a second normal account. Redact personal data from screenshots/log excerpts unless it is essential to diagnosis.

Community Discussion

Want to compare QCMM workflows or share practical tips? 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.