Publish, Unpublish, Duplicate, or Delete QCLF Email Templates

QCLF treats publication, duplication, and deletion as separate template lifecycle actions. Core templates are protected factory records; Custom templates are additive Max/All Access records.

Use publication state to control whether a template participates in real event delivery without deleting its saved content.

Publish or Unpublish

  1. Open Email and locate the template.
  2. Use the Published/Unpublished pill or edit form to change its state.
  3. For a Custom template, confirm Max/All Access is currently effective; below Max the Custom row is read-only.
  4. Trigger a safe matching event only after the intended templates are published.

Duplicate

Duplicate is available with Max/All Access. It can copy either a Core or Custom template, but the result is always a new Custom template with a generated key, copied content/routing context, and Unpublished state. Review it before publishing.

Delete

Only Custom templates can be deleted, and deletion requires the Max/All Access Custom-template capability. Core templates cannot be deleted through the Email workspace. Unpublish a Core template instead.

Downgrade Behavior

Custom rows remain stored after downgrade below Max but become read-only/unusable until entitlement returns. Likewise, Custom HTML bodies remain stored below Pro even though runtime falls back to built-in responsive HTML from Plain Text.

Avoid Accidental Duplicate Delivery

Because every published matching template sends independently, publishing a duplicated Custom copy while leaving its source template published can intentionally—or accidentally—produce multiple emails for the same recipient/event.

Community Discussion

Want to compare forum workflows, share practical QCLF tips, or discuss how other Joomla site owners use this feature? Visit the QC Live Forum Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.