Potential issue with signature fields

Hi. I'm using the latest version (1.05.03). I created a new template and added a signature field. The signature was not pulled through. I checked my older templates (made before the change in the FF signature extension recently) and noticed all previous signature filed now show as 'images' rather than signatures. I then tried to add an image field to my new template, clicked to 'map field', added this from my form and set up the field. This worked and pulled through the signature, but if that's right, why have the signature field option in E2PDF? I think the signature field needs updating to effectively insert an image field and it would be good if the image field had the option to manually add the field code to the properties as the old signature field did. Hope that makes sense or feel free to let me know if you think I'm missing something obvious here.

Hi,

E2Pdf "Signature" field must work same way as "Image" object in your case. After adding E2Pdf "Signature" field to Template it must be mapped the same way as "Image" object.

The difference that E2Pdf Signature has option "e-signature" which means that it will be created Adobe E-sign Field for Digital Signature.

If you are using "Formidable Forms" signature - "e-signature" checkbox must be unchecked. So it seems that this checkbox was "checked" or "signature" field was not mapped and due this it was not working like expected.

P.S. "Formidable Forms" sends signature like image - so its shortcode can be applied as to E2Pdf "image", as to E2Pdf "signature" field types.

We remain at your service.

---

We would really appreciate your feedback at WordPress.org!