Delete a Custom Email Template Safely

Only Custom email templates can be deleted. QCFUM treats Core templates as permanent workflow records and tells the administrator to unpublish a Core template instead.

Custom deletion also has dependency checks so an active workflow or pending delivery is not left pointing at a removed template key.

Check Invite Pack Assignments

Before deletion, QCFUM counts Invite Packs whose email_template_key equals the Custom template key. If one or more Packs still reference it, deletion is refused until those Packs are reassigned.

Check the Email Delivery Queue

QCFUM also checks email-queue rows for the same key with status queued or failed. Those unresolved deliveries block deletion. Sent queue rows do not block the current delete routine.

Delete the Custom Record

When both dependency checks pass, QCFUM deletes the row from #__qcfum_email_templates and writes an audit event with the deleted template ID and key.

What Is Preserved

The delete routine does not erase historical audit or delivery records. That preserved history can continue to identify the old template key even though the editable template record no longer exists.

Safer Retirement Workflow

  1. Unpublish the Custom template first.
  2. Reassign every Invite Pack that uses it.
  3. Resolve queued/failed deliveries.
  4. Confirm no current workflow depends on the key.
  5. Then delete the Custom record.

Community Discussion

Want to compare Joomla user-management workflows, share practical QCFUM tips, or discuss how other administrators use this feature? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.