maximum.software

What do you mean by ‘validation issue’ exactly? I though you just had an issue with embedding not working.

Please see https://wordpress.org/support/topic/signature-failure/.

Hi @mleprich,

Which signature plugin are you using?

I know that the ‘Contact Form 7 Signature Addon’ plugin has an issue since CF7 version 5.4. There is a post on their forum about this issue:
https://wordpress.org/support/topic/validation-required-issues/#post-14130291

For best results your width to height ratio needs to be the same as the width to height ratio of the embed bounding box.

Hi @eros86,

I’ve deployed version 1.3.13. It allows you to switch to using API v2. The second version of the API should solve your issue. It is only deployed on the beta server for now, so, you will need to change the API URL to “https://beta.pdf.ninja”, then request a new key by pressing the “Get New Key” button on the edit page.

Let me know if you have any issues with the new API version. I will deploy it at the primary API soon, so, you will not need to use the beta API in the future.

Thank you.

You may be able to come up with something on the CF7 side. All you need is a mail-tag for each option that will give you “Yes” when the corresponding PDF checkbox needs to be checked. You can then map each of those mail-tags to the corresponding PDF fields. I’m not sure, there might be a CF7 plugin that helps with that.

Otherwise, I will need to change the mapping feature to allow conditional filling based on CF7 field value. I feel like this is out of scope of my plugin.

I’ve received your PDF. The export values of checkboxes are all “Yes”, not “Check Box119”, “Check Box120”, “Check Box122”, and “Check Box123” as you indicated. It will not work this way.

The mapping feature works field-to-field, not field-value-to-field-value. CF7 produces 1 field with multiple possible values with your tag. That gets mapped to a PDF field which presumably should have those exact multiple values as options. The mapping feature doesn’t allow you to do this mapping conditionally to different PDF fields based on the CF7 field value while also mapping CF7 field values to some other PDF field values.

I recommend editing the PDF and naming all 4 checkbox fields with the same name while setting a unique export values for each checkbox (matching the values in the CF7 tag). This will allow you to map 1 CF7 field to 1 PDF field while having a “natural” value mapping.

Hi @slybr,

I haven’t yet gotten around to multi-select support yet. I’ve been working on preparing for the Pdf.Ninja API version 2 launch. It has been delayed due to various problems. It is holding me up right now.

Regarding your issue with checkboxes not getting filled, it is not related to the multi-select feature. As I understand it, you don’t actually need the multi-select feature. You just need the user to click on one of the options.

Make sure your PDF checkboxes have the same name (pdf_name) but different export values (value1 value2 value3). Use the checkbox tag with the ‘exclusive’ option:
[checkbox* pdf_name exclusive "Something 1|value1" "Something 2|value2" "Something 3|value3"]
Once you create the mapping, it should work. If you are still having issues, please post your PDF file or email it to me to admin at maximum dot software and I will see if I can figure out what the issue is.

Thanks.

Ignore the error message, I will release a new version shortly which will certify CF7 v5.4.1 as being supported.