Configure Membership Expiration Reminders and Post-Expiration Email Timing

Configure the three reminder offsets and post-expiration timing, understand duplicate prevention, and keep scheduled Meeting notifications separate from normal membership expiration email.

This guide follows the accepted QC Memberships & Meetings 2.0.21 implementation and applies to All plans; administrator. This category covers the durable membership record: activation, renewal successors, cancellation, expiration, Joomla-group reconciliation, administrator management, and the customer Member Area. 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

• Identify the exact subscription and user before changing dates, status, Plan assignment, payment state, or Joomla-group access.
• Preserve billing and lifecycle history; use QCMM workflows rather than deleting a record to make a status problem disappear.
• Test customer-visible changes with the affected member account because administrator access can hide ownership and menu-access mistakes.

Current QCMM Behavior

Step-by-Step Workflow

1. Open Scheduling and identify the exact Plan, Host, availability rule, Meeting Time, booking, and time-zone context.
2. Create or edit only the scheduling object needed for the scenario and preserve existing booked capacity.
3. Use a normal customer account to book or perform the allowed reschedule/cancel action.
4. Test capacity, notice window, conflict protection, and any No Show/courtesy logic relevant to the case.
5. Verify Host Schedule, customer schedule/Member Area, notifications, and final booking status agree.

Membership Expiration Reminders and Post-Expiration Email Timing

Configure the three reminder offsets and post-expiration timing, understand duplicate prevention, and keep scheduled Meeting notifications separate from normal membership expiration email 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.

Scheduling and Meeting workflows are stateful and time-sensitive. Distinguish Plan eligibility, Host availability, Meeting Time capacity, the customer booking, room/session state, and attendance history; they are related, but none is a substitute for the others.

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.
• Basic supports plain-text email, Pro+ supports HTML, and administrator-created trigger/recipient/Plan-scoped Custom templates require Max/All Access.
• Core and Custom templates are additive; not every internal Core metadata event is selectable when creating a new Custom template.

How This Fits into QC Memberships & Meetings

This category covers the durable membership record: activation, renewal successors, cancellation, expiration, Joomla-group reconciliation, administrator management, and the customer Member Area. 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 Membership Expiration Reminders and Post-Expiration Email Timing, 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 subscription status and dates match the intended lifecycle state.
• Joomla group membership reflects the active Plan without removing unrelated protected/manual groups.
• Member Area shows the expected membership, invoices, actions, resources, custom tabs, and Additional Information.
• Historical predecessor/successor and billing relationships remain intact after renewal or cancellation.

Common Mistakes to Avoid

• Deleting a subscription to correct a lifecycle problem when a status/date/renewal repair is available.
• Assuming Plan edits should retroactively replace every stored subscription snapshot.
• Removing Joomla groups without distinguishing QCMM-managed Plan groups from unrelated manually assigned groups.
• Treating a task delay as data loss before checking Membership Transitions and Lifecycle Automation.

Troubleshooting

• Test Joomla Mail independently, then template publication/format/recipient/tokens, then the event/task that triggers delivery.
• Check duplicate-prevention and prior send state before manually rerunning a reminder or lifecycle event.
• 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

Preserve the membership timeline. Use lifecycle automation for time-based transitions, dedicated actions for renewal/cancellation/corrections, and separate member accounts for frontend acceptance testing. Keep Joomla group reconciliation narrow so QCMM does not disturb unrelated site roles.

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.