Some characters are not displaying after upgrading to PDF Embedder 4.8.0

  • Resolved rigurucc

    (@rigurucc)


    5 months, 3 weeks ago

    Hello,

    After upgrading to version 4.8.0, some embedded fonts are no longer displaying. The PDF files uploaded to the media library themselves are fine and display correctly with a different PDF embedding plugin. Downgrading to version 4.7.1 resolves the issue, and the fonts display correctly.

    When I checked the console, I saw the following error:

    Error during font loading: The CMap "baseUrl" parameter must be specified, ensure that the "cMapUrl" and "cMapPacked" API parameters are provided.

    Thanks!

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

    (@slaffik)

    Thank you for the detailed report!

    We will investigate the problem and fix it in the next version of the plugin, most likely later today.

    Plugin Author Slava Abakumov

    (@slaffik)

    As a quick fix you can open the wp-content/plugins/pdf-embedder/assets/js/modules/pdfEmbedder.js file, and modify line 78, so instead of this:

    var loadingTask = pdfjsLib.getDocument( params);

    It has this:

    var loadingTask = pdfjsLib.getDocument( params, cmapURL );

    Or you can download this zip (which has only this change ^) and upload it on top of the current v4.8.1.

    Thread Starter rigurucc

    (@rigurucc)

    Thank you for your prompt response. ??
    However, the issue has not been resolved. I uploaded the zip file, but the same error message continues to appear in the console, and some characters are still not displayed.

    If necessary, should I send you the PDF file?
    (In that case, since it cannot be made public, please let me know where I should send it.)

    Plugin Author Slava Abakumov

    (@slaffik)

    Hm, that’s strange. Do you use any caching or JS optimization plugins? If yes, could you clear the cache?

    If that doesn’t help, please reach out via this form: https://wp-pdf.com/contact/basic/

    Plugin Author Slava Abakumov

    (@slaffik)

    We will include that fix in the upcoming 4.8.2 anyways.

    I’m closing this thread though as I haven’t heard from you for the past 2 days.

    Thread Starter rigurucc

    (@rigurucc)

    I apologize for the delayed response.
    I am not using any cache plugins or JS optimization plugins.
    Since the issue wasn’t resolved, I contacted you through the form.
    Thanks for all your help!

    Thread Starter rigurucc

    (@rigurucc)

    I am reporting that the issue was resolved after updating to version 4.8.2.
    Thank you!

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