PDFs slow to generate

Hi! I’m sorry to hear that. There haven’t been any changes in the PDF generation process for quite some time, and no other reports of this so far either. Is there enough free disk space on your hosting? Could you try ‘clear temporary files’ in the status tab, then try again?
Also, is this for single exports or bulk exports? Which version did you use when it was working ok?

Let us know and we’ll do our best to help!
Ewout

Hi Ewout, yes did try emptying temporary files..
it takes about 25 seconds on a single export and times out on a bulk export

I got the following from the debug log

2018/02/06 21:58:35 [error] 1392#1392: *959989 FastCGI sent in stderr: “PHP message: id was called incorrectly. Order properties should not be accessed directly. Backtrace: do_action(‘wp_ajax_generate_wpo_wcpdf’), WP_Hook->do_action, WP_Hook->apply_filters, WPO\WC\PDF_Invoices\Main->generate_pdf_ajax, WPO\WC\PDF_Invoices\Documents\Bulk_Document->output_pdf, WPO\WC\PDF_Invoices\Documents\Bulk_Document->get_pdf, WPO\WC\PDF_Invoices\Documents\Bulk_Document->get_html, WPO\WC\PDF_Invoices\Documents\Order_Document->get_html, WPO\WC\PDF_Invoices\Documents\Order_Document->render_template, include(‘/plugins/woocommerce-pdf-invoices-packing-slips/templates/Simple/invoice.php’), do_action(‘wpo_wcpdf_after_item_meta’), WP_Hook->do_action, WP_Hook->apply_filters, wooevents_add_event_meta, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
PHP message: id was called incorrectly. Order properties should not be accessed directly. Backtrace: do_action(‘wp_ajax_generate_wpo_wcpdf’), WP_Hook->do_action, WP_Hook->apply_filters, WPO\WC\PDF_Invoices\Main->generate_pdf_ajax, WPO\WC\PDF_Invoices\Documents\Bulk_Document->output_pdf, WPO\WC\PDF_Invoices\Documents\Bulk_Document->get_pdf, WPO\WC\PDF_Invoices\Documents\Bulk_Document->get_html, WPO\WC\PDF_Invoices\Documents\Order_Document->get_html, WPO\WC\PDF_Invoices\Documents\Order_Document->render_template, include(‘/plugins/woocommerce-pdf-invoices-packing-slips/templates/Simple/invoice.php’), do_action(‘wpo_wcpdf_after_item_meta’), WP_Hook->do_action, WP_Hook->apply_filters, wooevents_add_event_meta, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
PHP message: id was called incorrectly. Order properties should not be accessed directly. Backtrace: do_action(‘wp_ajax_generate_wpo_wcpdf’), WP_Hook->do_action, WP_Hook->apply_filters, WPO\WC\PDF_Invoices\Main->generate_pdf_ajax, WPO\WC\PDF_Invoices\Documents\Bulk_Document->output_pdf, WPO\WC\PDF_Invoices\Documents\Bulk_Document->get_pdf, WPO\WC\PDF_Invoices\D

2018/02/06 21:59:40 [error] 1392#1392: *959989 FastCGI sent in stderr: “rate_wpo_wcpdf’), WP_Hook->do_action, WP_Hook->apply_filters, WPO\WC\PDF_Invoices\Main->generate_pdf_ajax, WPO\WC\PDF_Invoices\Documents\Bulk_Document->output_pdf, WPO\WC\PDF_Invoices\Documents\Bulk_Document->get_pdf, WPO\WC\PDF_Invoices\Documents\Bulk_Document->get_html, WPO\WC\PDF_Invoices\Documents\Order_Document->get_html, WPO\WC\PDF_Invoices\Documents\Order_Document->render_template, include(‘/plugins/woocommerce-pdf-invoices-packing-slips/templates/Simple/invoice.php’), do_action(‘wpo_wcpdf_after_item_meta’), WP_Hook->do_action, WP_Hook->apply_filters, wooevents_add_event_meta, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0” while reading response header from upstream, client: 86.171.60.159, server: store.voiceinamillion.com, request: “GET /wp-admin/admin-ajax.php?action=generate_wpo_wcpdf&document_type=invoice&order_ids=46684x46677x46675x46671x46667&_wpnonce=da704f27eb HTTP/1.1”, upstream: “fastcgi://unix:/run/php/php7.0-fpm.sock:”, host: “store.voiceinamillion.com”, referrer: “https://store.voiceinamillion.com/wp-admin/edit.php?post_type=shop_order”

Those are generated by wooevents_add_event_meta (and triggered in the PDF Invoice context because it also includes that meta via the wpo_wcpdf_after_item_meta action hook). That wooevents_add_event_meta function appears not to be compatible with WC3.0

I’m not sure if that’s what’s causing this though…

Its version 2.1.4 , I’m more than happy to upgrade to premium version
Regards
Robert

Version 2.1.4 is the latest version (january 29th), are you saying it was working ok with this version but then started slower all of a sudden? My question was about the version you were using when it was still fast!

Free version is just as fast as the paid extensions…

Ewout

No, I believe the problem started in the last week….so since the upgrade

Our member of staff that uses the pdfs works for us on Tues & Thurs, she noticed this on Thursday 1st Feb

Still having a problem; and it started to crash the site as the PDFs waiting to be generated were backed up…it was showing a spike on the load at over 15…

We had to remove the back up before starting our server again

I tried the option to open in the browser rather than download a pdf, this opens almost instantly however it takes around 30 secs to load the barcode before it can be printed….I think the barcode may be causing the issue….is there any way I can disable that, maybe adding a piece of code

Regards

Robert

Having checked the url https://www.barcode-generator.org …it seems this is definitely the issue; as this URL takes a long time to load. (25 secs or more)

How do I remove the barcode option on both the packing slip and the invoice.

It would seem, checking the logs, that this site https://www.barcode-generator.org has some issues and intermittently loads faster..I guess depending on usage.

Barcode-generator.org is not used by this plugin, so it must have been added to your template or with a code snippet. But that sounds like you may indeed have found the culprit! Not related to the update after all ??

let me know if removing the barcode indeed fixes the issue!

Ewout

Hi Ewout

It was lurking within wooevents plugin, which also creates a pdf and includes a barcode…I am not convinced that wooevents is compatible, so have disabled for now; and the problem on the pdfs has now resolved.

Looking at the dates, I think it must have started on a recent wordpress core upgrade.

Thanks for your help..
Robert

Have now marked as resolved