bladeke

Same here – at some point, the “Print DPD labels” options was added back to the plugin so the selection in dropdown appeared again in WooCommerce 8.6.1 orders page but now when you select “Print DPD labels” it ends with a critical error:

Error details
===============
In file /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-content/plugins/woo-shipping-dpd-baltic/admin/class-dpd-admin.php?real 201 appeared an E_ERROR. Error message: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-content/plugins/woo-shipping-dpd-baltic/admin/class-dpd-admin.php:201
Stack trace:
#0 /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-content/plugins/woo-shipping-dpd-baltic/admin/class-dpd-admin.php(993): Dpd_Admin::http_client(‘createShipment_’, Array)
#1 /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-content/plugins/woo-shipping-dpd-baltic/admin/class-dpd-admin.php(604): Dpd_Admin->order_shipment_creation(Array)
#2 /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-content/plugins/woo-shipping-dpd-baltic/admin/class-dpd-admin.php(486): Dpd_Admin->do_multiple_print_parcel_label(Array)
#3 /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-includes/class-wp-hook.php(324): Dpd_Admin->handle_orders_bulk_actions(‘/wp-admin/edit….’, ‘dpd_print_parce…’, Array)
#4 /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘/wp-admin/edit….’, Array)
#5 /www/apache/domains/https://www.tupsunupsu.ee/htdocs/wp-admin/edit.php(222): apply_filters(‘handle_bulk_act…’, ‘/wp-admin/edit….’, ‘dpd_print_parce…’, Array)
#6 {main}
? thrown

Wow, that’s embarrassing ?? I thought I went through the settings but clearly missed the tag field somehow. Replaced with G4 tag and now it’s gone! ?? Thank you very much!

Hey!

That’s the thing – there is no plugin, it’s simple REST API integration and two webhooks. I’ve contacted the hosting provider and they confirmed no maintenance or any other activity impacts any webhooks or actions on the website itself. I’m simply stunned here…

Hi Zubair,

I determined this because each webhook has its creation date:

Veebikonksu tegevused (webhook actions)
Loodud (created) 23. veebr. 2023 @ 10:22
Uuendatud (updated) 8. m?rts 2024 @ 07:46

What I see on that day: fatal_errors log:

2024-02-23T15:20:04+00:00 CRITICAL Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function “adminNoticeUADismissHandler” not found or invalid function name in /www/apache/domains/www.tupsunupsu.ee/htdocs/wp-includes/class-wp-hook.php:324 Stack trace: #0 /www/apache/domains/www.tupsunupsu.ee/htdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #1 /www/apache/domains/www.tupsunupsu.ee/htdocs/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #2 /www/apache/domains/www.tupsunupsu.ee/htdocs/wp-admin/admin-ajax.php(188): do_action(‘wp_ajax_pys_not…’) #3 {main} thrown failis /www/apache/domains/www.tupsunupsu.ee/htdocs/wp-includes/class-wp-hook.php real 324

And then there’s the webhook_delivery log which contains update requests for 2000+ orders.

Hi! Has this been fixed?

Hi Afzal,

Thank you for getting back to me!

• No changes made to the site that day
• Three plugins automatically updated that day:
  • Back In Stock Notifier for WooCommerce | WooCommerce Waitlist Pro 5.2.1
  • PixelYourSite 9.5.0.1
  • PixelYourSite 9.5.1
• Any access is given in the form of admin user – I’ve checked the logs for 22.02-24.02 and no activity from any of the admin users that relate to any changes in WooCommerce configuration – only adding products and product images.

I will upgrade to 8.6.1 once I’ve tested it on the offline shop first. This recent database structure change for orders really messed up our business, that’s why I had to rollback, but will definitely upgrade soon.

Hi Sandip! Ticket #7663147 created in Woo.

Thanks!

I went with the plugin upload method though. Luckily I can confirm the orders can be opened again now, will keep monitoring the system, but so far it seems that 8.4.0 is fine, indeed!

Disable WooCommerce plugin –> upload 8.4.0 contents and overwrite existing 8.5.2 –> start WooCommerce plugin

Will this do the trick then or do I have to change something additionally? ??

• This reply was modified 1 year, 1 month ago by bladeke.

I’ve followed the instructions mentioned on the Woo link earlier, but still the orders are not opening. I’ve enbaled the compatibility mode with the legacy mode also activated, but no changes visible.

Can I simply upload WooCommerce 8.4.0 plugin folder and overwrite existing 8.5.2 and not break my site? I really need to work with the orders…

I think I know what it is. I noticed that now when I try to open any order, it’s opened as a post and this fails somehow. There’s a new feature called “High-performance order storage” (WooCommerce –> Settings –> Advanced –> Features) which seems to implement a new database structure. But apparently I have 7 plugins that are not compatible with this feature and I’m guessing it messes everything up therefore. I cannot disable these plugins since they are essential to our business.

https://woo.com/document/high-performance-order-storage/#section-7

It says you can enable the compatibility mode, I’ve just done it, waiting for the sync to complete. Hopefully this fixes it!

I was on 8.5.0, didn’t rush to upgrade to 8.5.1 and as it turned out, it had major issues so dodged one there. But now noticed there’s 8.5.2 without any significant changes (seemingly at least) so I updated today, now I cannot open any order in the list:

2024-01-29T14:14:21+00:00 CRITICAL Allowed memory size of 402653184 bytes exhausted (tried to allocate 20480 bytes)

even after increasing the memory to 1024M

2024-01-29T14:20:07+00:00 CRITICAL Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes)

Basically we cannot work on any of the customers’ orders until this gets fixed.

My database was restored to the state from this morning. Noticed that indeed Pop Up builder had an update which seems to be the culprit. Without the update to it, AST works fine without any additional code needed.

Thank you very much for the tip!!

I’m still waiting for the database restore from ISP…

Well, this broke my functions.php and it’s empty now, hence the site is down. Trying to restore the original file… :S