Configure QCMM Frontend Appearance

Understand QCMM 2.0.21 Frontend Design settings, validation, inheritance, and the important fact that legacy appearance values are currently dormant on the site frontend.

Frontend Design Settings Still Exist

QCMM 2.0.21 retains Administrator Frontend Design settings for default styling and scoped areas such as Plans, Plan cards/detail, subscribe, checkout, payment selector, dashboard, billing, tables, alerts, and buttons. Values are validated as supported colors, numeric ranges, or select options before storage.

Scoped Settings Inherit from Default

Each non-default section can be marked custom. When it is not custom, its Administrator value resolver inherits the Default frontend styling values. The Default section can restore QCMM's packaged defaults.

Important 2.0.21 Frontend Behavior

In the current site helper, the legacy Frontend Design value resolver intentionally returns fixed product defaults. Existing appearance values remain stored for backward safety, but they are dormant and do not currently drive the site frontend. Do not diagnose a saved color that does not change the frontend as a failed database save without first accounting for this 2.0.21 design state.

Use Custom CSS for Supported Live Overrides

Where a live visual override is required, Max / All Access sites can use QCMM Custom CSS. Keep selectors scoped under .qcm-frontend and verify the affected Plans, checkout, Member Area, scheduling, and Meeting surfaces after changes.

Preservation

The dormant appearance values are preservation-first: current frontend behavior does not require deleting them, and future implementation can continue to migrate or reuse stored configuration safely.

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.