Plugin Contributor
Ewout
(@pomegranate)
It looks like debug output is enabled on your site. I see that you’re using a very old version of WooCommerce (2.6, from 2017) and suspect this may be an incompatibility somewhere.
Disabling debug output is the quickest fix here. If you want to see the full error, you could temporarily add this to the URL of the PDF: &debug=true&output=html
I have not activated the “Enable debug output” option. And i dont get any url to the pdf, it just downloads.
Plugin Contributor
Ewout
(@pomegranate)
PHP is printing error messages which means that either WP_DEBUG is enabled our it is enabled in PHP itself. The setting in our plugin can also enable this, but there are many more ways. Normally errors like this shouldn’t display at all on a live site and I recommend looking into this because it may reveal (otherwise harmless) errors on other locations in your site too.
If the PDF downloads directly, you can switch to “Open in a new tab” in the general settings.
Yes i changed that but it still just downloads the PDF. Assuming that i am supposed to do this from orders and then click the invoice under “actions”?
I now changed to html and added the debug line and then i got this error:
Notice: Undefined variable: tax_data_key in /nas/content/live/ismokeking/wp-content/plugins/woocommerce-pdf-invoices-packing-slips/includes/documents/abstract-wcpdf-order-document-methods.php on line 619
I have the same problem. I get a very weird font on my invoices since the last update.
Please check the screenshot: http://carrotsun.eu/invoices.png (personal information hidden due to privacy policy).
I also get white screen of death if i manually try to create an invoice.
Plugin Contributor
Ewout
(@pomegranate)
@boutzamat your issue is completely unrelated to the issue above. It looks like the fonts were not correctly installed, try “Reinstall fonts” on the status tab of the plugin settings. If you still get a white screen of death, try adding &debug=true to the URL and open a new thread on this forum.
@ismokeking thanks for reporting the error. This is indeed an incompatibility with the 2017 WooCommerce version and has been fixed for the next release. For now, the quickest way to resolve this is to make sure error display is disabled on your site. If you don’t know how to do that, contact your host and they should be able to do this for you. Apologies for the inconvenience, because WooCommerce 2.6 is hardly used anymore our testing program for it is not as extensive.
Thank you, i will look in to this with my host then. This was a very good and quick support i have to say!! 🙂
@pomegranate i degraded to version 2.4.7 and everything works as intended again.
I will try to upgrade again, and run the “reinstall fonts” function.
Thank you!
Plugin Contributor
Ewout
(@pomegranate)
@boutzamat that sounds plausible – each update or downgrade should trigger the fonts installation procedure again automatically. Please open a new thread if you have any issues with 2.4.8.
