error— The API version “2.0.288” does not match the Worker version “1.9.648”.

Same problem here. Hope it can be solved.
I have WordPress version 4.9.8–nl_NL

Hi yellowduck003 and svrancken,

The issue has to do with caching of the scripts on your respective sites. The method to fix this can be found here in our FAQ: https://wp-pdf.com/kb/the-api-version-does-not-match-the-worker-version-error-on-update/

If you have further questions regarding this, please drop us an email to [email protected] as we may not see posts on these forums in a timely fashion.

Emma

I immediately cleared my browser’s cache and then updated the plugin.
After that, it worked without problem.

/wp-content/plugins/pdf-embedder/js/all-pdfemb-basic.min.js,
/wp-content/plugins/pdf-embedder/js/pdfjs/pdf.min.js, and
/wp-content/plugins/pdf-embedder/js/pdfjs/pdf.worker.min.js

As a precaution, I deleted the above three files with reference to FAQ.

Thank you very much.

I had the same error and this fix worked for me also.

Thanks!

Thanks for the help

I am still having difficulty in getting rid of the problem on https://fyzuntu-games.international.
I have WordPress V 4.9.8.
All plug-ins are up to date.
I also use Leverage Browser Caching V 1.7.

I have input the following to Hummingbird’s browser cacheing section
/wp-content/plugins/pdf-embedder/js/all-pdfemb-basic.min.js,
/wp-content/plugins/pdf-embedder/js/pdfjs/pdf.min.js, and
/wp-content/plugins/pdf-embedder/js/pdfjs/pdf.worker.min.js

I have cleared website data from Safari and restarted my Mac Laptop.

While the pdfs show up ok in Chrome the error still appears on mine and other users’ Macs.

Should I reinstall PDF Embedder?

Any advice would be welcomed

Hi bobevanuk,

Hmm, if the issue is cleared in Chrome but remains in Safari, it does sound like it is an issue with that specific browser caching. I would suggest doing a hard reload to force the page and scripts to be reloaded (Mac/Apple: Apple + R or Cmd + R). I’m not sure if Safari has a “hidden” cache, but the following article may provide some further assistance: https://www.macworld.co.uk/how-to/mac-software/safari-cache-mac-3496193/#toc-3496193-2

Reinstalling the plugin shouldn’t be necessary as it is working on other browsers, but if nothing else works with Safari, then it is worth a try. Deleting the PDF plugin will not remove any of your embedded documents – the shortcode will be displayed until the plugin is reactivated.

If you have any other questions, please do not hesitate to send us an email at [email protected].

Emma

This error just started happening on all of our pages. I’ve used this plugin extensively on our news site and all getting this error message. I can’t ask thousands of readers to press Ctrol+F5. That worked on Desktop version, but still getting the error message on mobile. Very frustrating.

You can force a browser cache to load the new scripts using Cache Control: https://varvy.com/pagespeed/cache-control.html.

Did you fix this problem yet? I want to go back to this plugin if it’s been fixed. Thank you.

I can’t find a fix. No caching and minifiers exclude the recommended is files. Maybe it’s a plug-in but nothing seems to be caching.

Googling the issue comes up with hundreds of websites that have indexed this error message.

Perhaps the plugin needs a new release! How come this has just become an issue even if caching is the culprit – it’s become a new problem with latest update.

All of the scripts in the plugin were updated to the latest versions of PDF.js on the latest plugin release.

Clearing caches – site, if used, and browser – maybe necessary. For more information on how to resolve this please see our FAQ: https://wp-pdf.com/kb/the-api-version-does-not-match-the-worker-version-error-on-update/

You can force a client’s browser cache to load the new scripts using Cache Control: https://varvy.com/pagespeed/cache-control.html

If you have further questions regarding this, please drop us an email to [email protected] as we may not see posts on these forums in a timely fashion.

I just tried the htaccess cache control – it didn’t solve anything.

… and I can hardly ask every website visitor to reset their cache.