-
-
Notifications
You must be signed in to change notification settings - Fork 87
Open
Description
Describe the bug
I am trying to use the Signature field in a custom Email and PDF template.
Current behavior:
- The "Save to Assets" setting is missing from the Signature field configuration (General/Advanced settings).
- Because I cannot save the signature as an asset,
{{ submission.getFieldValue('signatureField').one() }}returns null. - The field value defaults to a Base64 string, which renders as raw text in my templates unless I manually wrap it in an
<img>tag.
Expected behavior:
I should be able to save the signature as an asset to handle it as a standard Craft Asset in my Twig templates.
Steps to reproduce
- Create a new form in Formie.
- Add a "Signature" field.
- Navigate to the field settings (General, Settings, and Advanced tabs).
- Observe that the "Save to Assets" toggle is missing.
- Submit the form and check the
contentHtmlin a custom email; the signature appears as a Base64 string.
Form settings
- Field Type: Signature
- Logic: No conditional logic enabled.
- Template: Custom Email and PDF templates using
form.getFields()loop.
Craft CMS version
5.8.22
Plugin version
3.1.6
Multi-site?
No
Additional context

Metadata
Metadata
Assignees
Labels
No labels