Plugin broken after update

  • Resolved Ralf Klis

    (@rklis)


    6 years, 9 months ago

    Hi there,

    I see you struggle with MPDF setup and there’s quite a few issues but none of the solutions worked for me.
    Tried: changing file permissions, disabling all plugins, changing to twentyseventeen, removing and reinstalling the plugin. All (in the latest version) returns the below:

    Fatal error: Uncaught MpdfException: Can't open file /vagrant/content/uploads/woocommerce-pdf-invoices/mpdf/ttfontdata/dejavusanscondensedB.GSUBGPOStables.dat in /vagrant/content/plugins/woocommerce-pdf-invoices/vendor/mpdf/mpdf/classes/otl.php:297 Stack trace: #0 /vagrant/content/plugins/woocommerce-pdf-invoices/vendor/mpdf/mpdf/mpdf.php(16209): otl->applyOTL('Please print ou...', 255) #1 /vagrant/content/plugins/woocommerce-pdf-invoices/includes/abstracts/abstract-document.php(193): mPDF->WriteHTML('<table class="c...') #2 /vagrant/content/plugins/woocommerce-pdf-invoices/includes/abstracts/abstract-invoice.php(319): BEWPI_Abstract_Document->generate('F') #3 /vagrant/content/plugins/woocommerce-pdf-invoices/includes/woocommerce-pdf-invoices.php(363): BEWPI_Abstract_Invoice->generate() #4 /vagrant/wp/wp-includes/class-wp-hook.php(286): BE_WooCommerce_PDF_Invoices->admin_pdf_callback('') #5 /vagrant/wp/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #6 /vagrant/wp/wp-includes/plugin.php(465): WP_Ho in /vagrant/content/plugins/woocommerce-pdf-invoices/vendor/mpdf/mpdf/classes/otl.php on line 297
Viewing 3 replies - 1 through 3 (of 3 total)
  • maximvanmaanen

    (@maximvanmaanen)

    6 years, 8 months ago

    Hello Ralf,

    Could you go to the mpdf folder and tell me if it has any files in it or not? you should be able to find this at wp-content\plugins\woocommerce-pdf-invoices\vendor\mpdf

    Thread Starter Ralf Klis

    (@rklis)

    6 years, 8 months ago

    the files are there, the only solution for me that worked was getting the plugin from git repo and compiling it myself (composer install)

    maximvanmaanen

    (@maximvanmaanen)

    6 years, 6 months ago

    The issue at hand was isolated to permission issues. This is only an issue when the plugin is directly grabbed from our github page. If you do so, please run Composer as stated above to sort out the permissions.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Plugin broken after update’ is closed to new replies.