Publish, Unpublish, Duplicate, or Delete QCLF Email Templates
Explain lifecycle controls and why Custom templates can remain stored/read-only below Max.
This guide follows the accepted QC Live Forum 1.1.27 implementation and applies to All plans / Max for applicable custom actions; administrator. QCLF separates event/notification logic from presentation: Joomla Mail transports messages, QCLF selects triggers/recipients/tokens, and appearance controls remain scoped to the forum frontend. When older walkthrough or project-manual wording conflicts with 1.1.27 source or later accepted Authorized-Domain behavior, the current implementation takes precedence.
Before You Begin
- Verify Joomla Mail can send independently before troubleshooting a QCLF template.
- Keep plain-text content useful even when HTML is available on the current tier.
- Test appearance and CSS changes on desktop and narrow/mobile layouts.
Current QCLF Behavior
| Item | Current behavior |
|---|---|
| Basic email | Plain Text plus supported tokens |
| Pro+ email | HTML body support |
| Max / All Access | Additional Custom trigger-based email templates and Custom CSS |
| Template model | Core templates are protected; Custom templates are additive and preservation-first across downgrade |
| CSS scope | Use the stable .qclf-frontend scope; do not include |