Jane Onorati replied 1 month ago

Hi Victor. I did get a response from Toyin at Formidable Support: "This is because the file path breaks the format when sending data RAW format. The signature field sends a file path, this path contains characters that affect the data structure in RAW format. I have escalated this to our developers for further review." I'll wait to see if they come up with a fix. I have handled serialized data in PHP before but don't remember how I did it so would need to review how to do that.

Jane Onorati replied 1 month ago

Well, I got as far as I could with support, but it does not totally solve the problem. I was told I could use [x show=url] in the API action, where x is the ID of the signature field. However, then there is the problem of how to display the signature image when needed.

This does transfer the signature url to the receiving form without error. However it works differently than when I have done this with forms that do not have repeaters and not using the API raw format. When I look at the entry produced by an API json format action, I see the image. However, using this method, I don't see the image but instead just the url.

I need to be able to display the signature image in views. I also have a working form without repeaters that creates a pdf signed waiver using e2pdf. I want to be able to do the same with repeaters and e2pdf or Formidable's PDF add-on (which requires a view).

Then support suggested I could display the image in a view by using the image tag, i.e. '<img src="[x]"/>', where x is the ID of the signature field where the URL is saved. That works but only for the signatures that are drawn and does not work for the ones that are typed. Support had no suggestion for a conditional shortcode that would display the signature based on whether it was typed or drawn. So unless I can figure a way to solve that, I'd have to offer all form users only one option for creating their signature.

Jane Onorati replied 1 month ago

I was able to display the signatures by type conditionally using both the e2pdf plug-in and in a view. In both cases, I used the criteria of whether the field contained "https" in it or not to display each signature in the correct format.

In the view, it looks like this: [if 6pl98 contains="https"][/if 6pl98][if 6pl98 does_not_contain="https"][6pl98][/if 6pl98]. In my e2pdf template, I have an image object field and an html object field on top of each other with actions that hide the elements based on the same criteria.

So the complete solution is to use [x show=url] in the API action, where x is the ID of the signature field, and then display the signature that has been delivered to a text field in another form conditionally based on whether "https" is contained in the value.