Use Custom HTML in QCLF Email Templates

QCLF Custom HTML email bodies require Pro, Max, or All Access. Plain Text is still mandatory because QCLF uses it as the alternate/fallback body and as the source for built-in responsive HTML when Custom HTML is not active.

Custom HTML is a presentation option on a template—not a separate notification trigger.

Enable Custom HTML

  1. Open a Core or available Custom template on Pro+.
  2. Keep the Plain-text body complete and useful.
  3. Set Format to Custom HTML.
  4. Enter the HTML body and use Preview HTML.
  5. Save, then send a test through Joomla Mail before relying on the template in production.

Server-Side HTML Safety

Before storage/rendering QCLF strips high-risk elements such as script, iframe, object/embed, form controls, base/link elements, event-handler attributes, and unsafe JavaScript or data:text/html URLs. The saved HTML is sanitized again for rendering.

What Happens Below Pro

Existing custom HTML remains stored, including its enabled state, but the runtime custom-HTML gate fails below Pro. QCLF then sends the built-in responsive HTML generated from the Plain Text body. Returning to Pro/Max restores eligibility for the saved Custom HTML without re-entry.

Core vs Custom Factory HTML

Core templates have QCLF-generated factory responsive HTML and can restore that factory-style HTML when the stored copy is blank/default-like. A newly-created Custom template has no factory Custom HTML: enter your own HTML or keep it in the Plain Text/built-in mode.

Transport Format

QCLF sends through Joomla Mail as HTML and supplies the Plain Text body as AltBody. Troubleshoot template rendering separately from Joomla SMTP/mail transport.

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.