Hi,
Unfortunately we can’t replicate issue on our side.
We see that your “Signature” renders with “timestamp=1664271894” so in this case, E2Pdf will try to retrieve the Image by URL and not locally, and here it can be issue that “Image” doesn’t accessible due to Firewall rules (it could be blocked own Server IP address) or some specific security settings. You can submit a Full URL so we can check the response from your server here: https://e2pdf.com/support/contact
We suspect that it was added a custom hook as by default Formidable Forms signature must not have a “timestamp”.
You can also try to solve the issue by:
-Try to update the shortcode that is used inside the E2df Template as: [123 use_html=0]
If it will not help:
– You can try to use a shortcode wrapper to remove “timestamp” to allow E2Pdf to request it locally as:
[e2pdf-format-output explode="?" output="{0}"][123 use_html=0][/e2pdf-format-output]
We remain at your service.
mmmm i just added the signature field and mapped it to the proper form field like i did always.
I will try your tips, the correct url is not a secret, just preventing bots and script kiddies. If u replace xxx with shipdocs it will work.
I will try your tips, the correct url is not a secret, just preventing bots and script kiddies.
This is can be the reason why the “Signature” image can’t be shown. You need to whitelist / remove rules for your Server IP Address to prevent this check as it seems the image request by E2Pdf is detecting as a bot.
mmm it may be cloudfare then, messing things up
edit checkit it and indeed cloudfare was the isue
