The file upload links in the PDF when clicked on Mac OS Mojave does not open the file

Also the links when opened on Mac OS 10.14 Mojave do not open the file. (Opening pdf in 10.13 preview OR in Adobe Reader the links work)

I'm sorry, but when you say the link does not open the file, do you mean you open the PDF using your browser in Mac OS Mojave and click the link from there? Please clarify. You may also consider keeping your Adobe PDF Reader to open the PDF. That is recommended. 

There are two issues.  

1) If multiple files are selected and we have the FTP upload set. We get the form pdf that shows both files in it that also has hyperlinks to the files.  Opening the PDF in Mojave Preview Version 10.1 (944.6.16.1) the hyperlinks show but clicking on them does not open the link.

Opening the same PDF in Adobe Reader does open the links.

2) The FTP properly uploads the first file, but the 2nd file is never uploaded. So in the example of 2 files uploaded we get a PDF form and the first file.  To get the 2nd file we either have to go to jotform website and download it OR open pdf in Adobe Reader and download the 2nd file. (NOTE: if 3 files are submitted only the first is set to the ftp site)

NOTE: The Preview issue is NOT the main issue, it is the fact that all the files are not FTPed to the remote site that is the problem.  

 

HOWEVER: Doing some experimenting, it is the space in the filename that is causing Mojave link to not work.  EG: 

This does not work:

https://www.jotform.com/uploads/RonLabrozzi/52094818808161/4320157780314380202/2019-03-27 14-48.jpeg

Replacing the space before the 14-48.jpeg make the link "TRY" to work but of course fails because the file is not named that.

https://www.jotform.com/uploads/RonLabrozzi/52094818808161/4320157780314380202/2019-03-27-14..-48.jpeg

 

I will submit this to Apple as a bug in their preview program.

oops.  I just checked and the bug is in Jotform, not Apple

"You must encode a space; it is correct to encode a space as + , but only in the query string; in the path you must use %20 . URLs are defined in RFC 3986, though other RFCs are relevant as well but RFC 1738 is obsolete. They may not have spaces in them, along with many other characters"

Hi @RonLabrozzi!

Thank you for reaching out to our support forum! It looks like the issue was fixed earlier today, can you please test this one more time? 

If the issue persists we will escalate this to our back-end team again to have them look further.