Troubleshoot QCMM Custom Fields, Fulfillment, and Plan Resources

Troubleshoot Custom Field snapshots, fulfillment authorization/concurrency, customer visibility, Plan Resource scope, and protected downloads without losing submitted data.

Identify the Field Layer

Check the global Custom Field definition, its assignment/order on the Plan, required/editable/admin-only behavior, and the subscription snapshot. Values belong to the subscription context, so two subscriptions for one Joomla user can legitimately differ.

Fulfillment Uses Plan-Assigned Editor Groups

Frontend Fulfillment access is server-authorized from each Plan's Fulfillment Editor Groups and requires the applicable feature entitlement. Host status or Joomla Administrator status alone is not the Plan authorization rule.

Respect Fulfillment Concurrency

Fulfillment saves carry a version value so one editor does not silently overwrite another editor's newer change. Reload the current record after a concurrency conflict instead of forcing stale values over it.

Check Customer Visibility by Field Type/State

Customer-entered information can be read-only in fulfillment while administrator-assigned/Internal values are managed by authorized editors. Missing customer display should be traced to the field assignment/snapshot and display rules, not recreated as a second field.

Protected Resources Re-authorize Every Download

For Download resources, QCMM checks the logged-in user, owned subscription, Plan resource, access rule, and safe local/remote target before streaming. A failed protected download can therefore be an ownership/access, resource configuration, filesystem, DNS/host, redirect, or remote-response problem.

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.