• Resolved yolandal

    (@yolandal)


    Hello support,

    The PDF plugin works well in Firefox, but in Chrome and Edge it’s not working, and it’s showing an error. See screenshot https://imgur.com/a/E1y4fka

    What is going wrong?

    Thank you,

    Yolanda

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Slava Abakumov

    (@slaffik)

    Hello there,

    That’s because you used a LiteSpeed caching plugin that broke our JS.

    We have a relevant doc article on our site which will help you resolve the issue (LiteSpeed plugin settings needs to be adjusted to exclude PDF Embedder scripts): https://wp-pdf.com/docs/using-caching-or-minifying-plugins/

    Thread Starter yolandal

    (@yolandal)

    Hello Slava,

    Thanks for your respons. Unfortunately my problem is not solved yet.

    I’ve added these URL’s to the exclusion list
    /wp-content/plugins/pdf-embedder/assets/js/pdfjs/pdf.min.js
    /wp-content/plugins/pdf-embedder/assets/js/pdfjs/pdf.worker.min.js
    /wp-content/plugins/pdf-embedder/assets/js/pdfemb.min.js

    I’ve flushed all cache, restarted, even re-installed the plugin, even used a different computer to test it, but the error keeps showing in Chrome and Edge. What am I doing wrong?

    Thank you,

    Yolanda

    Plugin Author Slava Abakumov

    (@slaffik)

    I see that the page displays this error:

    Cannot load script at: wp-content/litespeed/js/64317563ac95e6a302a88ececfe62f4f.worker.js?ver=1c32f

    Which means the cache hasn’t been flushed and the site still tries to load the cached version.

    I see the server is LiteSpeed, and Plesk is used to control the hosting. Maybe there is a dedicated cache/clear cache section in Plesk provided by your hosting provider?

    Because as of right now, that URL you shared is hitting the server cache: x-litespeed-cache: hit, so the whole page/site is definitely cached – either through the LiteSpeed Cache plugin, or through the hosting and its Plesk panel.

    Thread Starter yolandal

    (@yolandal)

    I excluded the URL from caching and now the problem is solved.

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.