Update, Reinstall, and Preserve QCMM Data Safely

QCMM is designed for in-place Joomla package upgrades and preservation-first schema repair. Updating or reinstalling the package is not a reason to erase product tables, membership history, billing records, bookings, Custom Field snapshots, or administrator configuration.

The 2.0.21 installer contains guarded repair and historical-migration checks specifically so an older or partially inconsistent installation can be brought forward without treating customer data as disposable.

Before an Update or Reinstall

  • Take a current full Joomla/database backup.
  • Record the installed QCMM version and any Status warnings.
  • Confirm the site meets the PHP 8.1+, OpenSSL AES-256-GCM, and MySQL/MariaDB requirements.
  • Use the full outer QCMM package so the component and Scheduled Task plugin remain aligned.

Use the Normal Joomla Upgrade Path

  1. Install/update the full QCMM package through Joomla Extensions/Updates.
  2. Allow the installer to inspect and repair the supported database baseline and current schema.
  3. Let guarded historical data migrations and configuration migrations complete; do not interrupt them by deleting tables first.
  4. Open QCMM → Status and verify version, entitlement, update-site state, and task integrity.
  5. Retest one membership path and each premium workflow the site actually uses.

What the Installer Preserves

  • Administrator-authored Plan/catalog decisions on update; automatic starter/sample creation is a fresh-install convenience, not a reason to repopulate a deliberately empty catalog during update.
  • Historical commercial and membership records while schema/index/column integrity is repaired.
  • Existing Custom CSS during storage migration.
  • Legacy/dormant coupon history with preservation-safe normalization rather than silently activating old codes.
  • Customized or unverified files/menu state where the installer cannot prove a legacy artifact is safe to remove.

Reinstall Is Not Data Reset

The component manifest uses upgrade semantics and does not define an uninstall SQL file that drops QCMM business tables. Its installer preflight/postflight intentionally skips destructive work for uninstall requests. Treat uninstall/reinstall as software package operations—not as a supported “clear all memberships” tool.

After Updating

  • Verify 2.0.21 on Status.
  • Confirm the five canonical QCMM tasks exist and the Entitlement Revalidation task is healthy.
  • Confirm Authorized-Domain entitlement and Base/Effective tier.
  • Open existing subscriptions, billing history, Plans, and—if used—bookings/Meetings/Custom Fields to confirm preservation.
  • Run a controlled frontend regression test instead of assuming a successful installer message proves the whole customer workflow.

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.