duup

Yes, that worked. I can now download the UBLs again.

Now we have to wait for the new subscription renewal to see if that other issue is fixed too. thx!!

I have to come back. It was working for the reported UBL problem, but since then we get an error whenever a subscription renews.

“An error has occurred while processing a recent subscription related event. For steps on how to fix the affected subscription and to learn more about the possible causes of this error, please read our guide here.”

When I look at the log, then i just see

2025-03-12T10:48:09+00:00Error scheduled action 2303644 (subscription payment) failed to finish processing after 300 seconds Additional context{ “action_args”: “subscription_id: 296575” }2025-03-12T12:26:47+00:00Error scheduled action 2303979 (subscription payment) failed to finish processing after 300 seconds Additional context{ “action_args”: “subscription_id: 285399” }

Then the email that we get probably says more:

WordPress version 6.7.2 Active theme: Child Theme for Divi (version 1.0) Current plugin: PDF Invoices & Packing Slips for WooCommerce (version 4.2.0-rc.1) PHP version 8.2.27 Error Details ============= An error of type E_COMPILE_ERROR was caused in line 19 of the file /home/u174197727/domains/ourdomain.com/public_html/wp-content/plugins/woocommerce-pdf-invoices-packing-slips/vendor/sabberworm/php-css-parser/src/CSSList/CSSBlockList.php. Error message: Cannot declare class WPO\IPS\Vendor\Sabberworm\CSS\CSSList\CSSBlockList, because the name is already in use

Apparently the UBL is regenerated when you click to open it. So a new version of the plugin, might generate a different UBL file I have experienced. I’m comparing a order from January to the same order from February, and for our billing system, the UBL is incorrect and not completely processed.

The UBL sent in January looks like

 <cac:AccountingCustomerParty>
  <cbc:CustomerAssignedAccountID></cbc:CustomerAssignedAccountID>
  <cac:Party>
...
  </cac:Party>
 </cac:AccountingCustomerParty>

Then non-working version of the February renewal looks like this

 <AccountingCustomerParty>
  <cac:AccountingCustomerParty>
   <cbc:CustomerAssignedAccountID></cbc:CustomerAssignedAccountID>
   <cac:Party>
   ...
   </cac:Party>
  </cac:AccountingCustomerParty>
 </AccountingCustomerParty>

And this last notation is failing at our accounting platform due to the extra level. They say that the last version of the UBL is not compliant as proper UBL notation. How to correct this? And who needs to correct something?

And please explain too how to get the image of the product please.

Ah ok. No problem. Thanks for the info!

Thanks Ewout,
We have it set to generate the invoice on completion, but question.
Could this action (where we want to export orders) generate the ‘missing’ documents when we check all statuses?

https://snipboard.io/bUScmH.jpg