A sudden problem causing it to not respect the default setting +

  • Resolved gdmi

    (@gdmi)


    1 year, 9 months ago

    Hey

    After the most recent update, DearPDF which used to work flawlessly have encountered two errors:

    The first being that PDF’s that are set to default setting (Vertical Reader) is now suddenly all acting as flipbooks. One can force the vertical reader is setting it specifying it manually, but the default value which should do the same isn’t working.

    The other issue that appeared is that it will on some pc’s show an error, which may be related (and only appears for the dearPDF entries):
    Error: Cannot access file! "URL to site.pdf" The API version "2.12.313" does not match the Worker version "2.5.207".

    The site is running customify as theme, it was working perfectly for several months. Only plugin changed around the time this first occurred was an installation of duplicator (and removing it made no difference).

    We are mostly using the light-box shortcode, but testing shows the same error for the embed.

    As we run with elementor for the editors, I have also tested this with plain old editor. We are also using the classic editor.

    It is the free version so far.

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

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

    (@dearhive)

    Hi,

    Thanks for your report. We will update the plugin shortly.
    Can you also confirm if you are using any other plugin than DearPDF – that uses pdf.js We use 2.12 new version something else is loading the old 2.5 version.

    Best Regards,

    DearHive

    Thread Starter gdmi

    (@gdmi)

    Hey

    Thank you for the extremely speedy response. The update you released fixed the default behavior to work as intended.

    As to the pdf.js, looking through the scripts on various parts of the sites, I only see the pdf.min.js (version 2.0.38) being used, but I didn’t encounter any other scripts that appear to be calling pdf.js. It should be mentioned that I have not seen the error on my own pcs, only colleagues.
    Elementor does call the webpack, but a brief search didn’t reveal any PDF.

    Plugin Author DearHive

    (@dearhive)

    Hi,

    The issue arises when there is different versions loaded by different plugins. Need to pinpoint which plugin is loading the pdf.worker.js. It is registered as a service.

    Thread Starter gdmi

    (@gdmi)

    Yea, I understood from the previous reply. I missed being specific, about that the one I saw was from dearPDF, not any other (at least in the debugger).
    The update also appears to have fixed this, as I went to look at the other people pc’s there problem only persisted until after clearing cache (noticed it has a cached worker), so seems like both issues was from what I can judge fixed by the speedy update. Very impressive.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘A sudden problem causing it to not respect the default setting +’ is closed to new replies.