Unable to print forms

  • infinet
    Asked on July 22, 2014 at 11:03 AM
    We are experiencing the same issue. Trying to print from the forms in Chrome, Firefox, or IE fails. Currently, the only fallback has been to get it as a pdf and then print from there.
  • David JotForm Support
    Replied on July 22, 2014 at 12:54 PM

    Hi,

    I am also able to replicate this issue in Chrome, but everything appears to work fine in FireFox and IE.

    Chrome:

    Unable to print forms Image 1 Screenshot 30

    FireFox:

    Unable to print forms Image 2 Screenshot 41

    As my colleague stated in the previous thread, even chrome worked after I cancelled the initial print and started a new one.  It appears to have been temporary.  Please let us know if you are still experiencing this and we will be happy to look into your issue further.

    Thank you for using Jotform!

     

  • infinet
    Replied on July 23, 2014 at 9:34 AM

    Double checked this morning and I am able to print from IE and Firefox without a problem. For Chrome, cancelling the initial print and then reprinting works as well. We ran into a similar issue with one of our websites in Chrome. If I remember correctly (it has been a while) we were able to fix the issue by moving the Javascript file calling the print function to the top of the page.

  • KadeJM
    Replied on July 23, 2014 at 11:21 AM

    After spending a little bit of time researching this more the result is usually temporary but can resonate according to chromium reports etched out by other users having the same exact issue in various other ways on an ongoing basis. 

    Reference Search - https://www.google.com/webhp?sourceid=chrome-instant&rlz=1C1CHFX_enUS592US592&ion=1&espv=2&es_th=1&ie=UTF-8#q=print%20preview%20fails%20in%20chrome

    I think one of my colleagues might have possibly found something similar as a fix to what you mentioned before with moving the Javascript Link, but unfortunately so far I am not finding it anywhere in our forum at the moment. I'm not so sure if this is fixable on our end since I'm not seeing a permanent solution yet in my findings other than to retry it or by attempting alternative previewing methods. If I find something better to help you here though then I will let you know.