Preview HTML and Send a QCDS Email Template Test

Preview HTML and Send Test answer different questions. Preview shows the template currently in the editor with sample values in your browser; Send Test sends the saved template through real Joomla mail to the Joomla account that is signed in.

Preview the Current Editor Content

  1. Open QCDS → Email Templates and edit a template.
  2. Make the Subject/message changes you want to inspect.
  3. Click Preview HTML.

The preview uses the current editor values, including changes you have not saved yet. Built-in mode generates the QCDS styled HTML from the current Plain-text message; Custom HTML mode previews the current Custom HTML body.

QCDS replaces its known tokens with sample values such as an example signer, Request number, secure link, and verification details. If {{...}} placeholders remain unresolved, the preview displays an Unresolved tokens warning.

The Preview Is Browser-Side

The preview is placed in a sandboxed iframe. It is useful for checking layout, token placement, and the generated QCDS HTML shell, but it does not prove that Joomla mail can authenticate with your mail server or deliver a message.

Save Before Using Send Test

Send Test is launched from the Email Templates list and tests the saved personal/template row. If you have unsaved edits open in the editor, Preview can show them, but Send Test will not use them until you save the template.

QCDS intentionally allows Send Test to test a saved personal override even when Published = No, so you can verify an inactive override before enabling it for future Requests.

What Send Test Does

QCDS sends the test only to the email address on the Joomla account that is currently signed in. No posted recipient, Contact, signer, workspace address, or administrator address can override that destination.

It renders sample token values, applies the configured QCDS/Joomla mail identity, prefixes the Subject with [Template Test], sends an HTML message through Joomla mail, and records the test event.

If unresolved token syntax remains after rendering, QCDS blocks the test instead of sending a message with unresolved placeholders.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.