Error generating PDF

Caldera Forms
9 May, 2021 01:38:54
gregmag
Topics: 1
Messages: 5
Since the last update, I have permanently problems with generating pdf on some browser with the shortcode e2pdf-view. The viewer stay with black screen "waiting for pdf". In the background, the pdf is generated and send correctly per email and the e2pdf-download shortcode has no problem.
In the printscreen, you will see an error in pdf.js.
Thanks for your help
9 May, 2021 04:51:13
E2Pdf
Support
Topics: 7
Messages: 3163
Hi,

It looks like can be some cache issue. Can you try to clear cache if you use Cloudflare or any 3rd party cache plugins and try to reload page with CTRL+F5 to see if it will work?

If not, are you able to provide us link where we can try to submit form and see result? Thank you.

We remain at your service.
We would really appreciate your feedback at WordPress.org!
10 May, 2021 00:20:05
E2Pdf
Support
Topics: 7
Messages: 3163
Hi,

We currently were able to test page with Chrome and Firefox and viewer loaded correctly without any issues, so we are almost sure that the problem is in "cache". We see that on your website you are using WP Fastest Cache, so try please:

1. Clear cache with WP Fastest Cache and rebuild minified CSS/JS
2. Clear browser cache -> Close and Re-open browser

We remain at your service.

We would really appreciate your feedback at WordPress.org!
10 May, 2021 00:38:17
gregmag
Topics: 1
Messages: 5
I have cleared all possible things and WP Fastest Cache clear also automatically twice a day. Tested on 2 PC and 1 Mac with Safari, Firefox Developer, Chrome.
On my Mac and another PC, I see the problem only with Firefox. On a second PC (Chrome kiosk-mode), same problem.
11 May, 2021 11:31:41
gregmag
Topics: 1
Messages: 5
Hi, i have overwritten the full pdf.js in assets directory with the old version from e2pdf 1.13.40 and the problem is solved.
As i have seen, the e2pdf 1.15.00 version contains a new pdf.js version and it seems to be the problem.
11 May, 2021 22:14:43
E2Pdf
Support
Topics: 7
Messages: 3163
Hi,

On any next update pdf.js will be overwritten so this is not a good option if you plan to use updates, also we didn't get any other complaints from other users about new pdf.js at this moment.

We are still almost sure that the problem in cache as such message looks like exactly that it's trying to use old pdf.js worker instead of new one or we are missing something on our side to replicate issue like browser/os/logged in...

Can you check please if the current demo will work for you? It uses latest pdf.js version: https://demo.e2pdf.com/caldera-forms/

P.S. If you want to use old pdf.js viewer and to not overwrite it on updates, you can try to copy pdf.js folder out from E2Pdf folder of 1.13.40 version to your child theme (as example) and use custom viewer via command:

[e2pdf-view id="1" viewer="https://example.com/wp-content/themes/twentytwenty-child/pdf.js/web/viewer.html"]
We would really appreciate your feedback at WordPress.org!
12 May, 2021 01:01:36
gregmag
Topics: 1
Messages: 5
Hi.
Yes, I know that it will be overwritten. That was only to confirm that the problem is here since the last update ...

And yes, your demo work for me ...
12 May, 2021 10:53:07
E2Pdf
Support
Topics: 7
Messages: 3163
Unfortunately new pdf.js viewer has some changes in the way it must be called, so the issue looks like connected with some cached js file/files from 1.13.40 version which prevents to load new pdf.js viewer for you.

Due the using WP Fastest Cache & Minify "js" files can be different for you and for us, that's why it was requested "js" file which you see under your browser or try to deactivate temporary WP Fastest Cache to check if new viewer will be loaded without cache as from our side we see that generated minified javascript has updated code and viewer loads correctly for us. Also it works for you on our demo page so the problem looks like not in browser and not with pdf.js viewer. For sure that is a chance that issue can be connected with some specific plugin conflict however at this moment it looks like "cache" was not cleared and browser/website using some cached files from previous version.

We remain at your service.
We would really appreciate your feedback at WordPress.org!