Publish or Unpublish an Email Template

Publication controls whether QCFUM can load a template for normal workflow delivery. Both Core and Custom records can be published or unpublished without deleting their saved content.

Unpublishing is therefore an operational switch, not merely an organizational label.

Change Publication State

Use the Published/Unpublished pill in the Email template row or the Published field in the editor. QCFUM updates published, records the update time, and audits the state change.

What Runtime Delivery Requires

Normal workflow delivery calls getEmailTemplate(templateKey), which requires published=1. If the key is missing or unpublished, QCFUM logs that the email was not sent and returns before Joomla mail is called.

Unpublished Mail Is Not Automatically Queued

The queue-on-failure logic only runs after QCFUM has rendered a published template and Joomla mail returns failure. A missing/unpublished template fails earlier, so that event is not placed into the email retry queue merely because the template is unavailable.

Core Templates Can Be Unpublished

Core templates are permanent records but may be unpublished. Do this only when you intentionally want the corresponding built-in workflow email suppressed; hardcoded workflow keys do not automatically switch to another Custom template.

Custom Template Dependencies

An unpublished Custom template can remain stored—and may remain selected by an Invite Pack in the administrator UI—but runtime delivery by that template key will fail until it is published again. Test the dependent workflow after any publication change.

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.