You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a newly setup webshop that automatically setups for High performant orders, Myparcel does not work anymore.
Reproduction steps
setup new webshop with high performant orders enabled
setup myparcel
see that metaboxes on order details and barcode columns are not rendering.
Relevant log output
No response
Additional context
From WooCommerce 8.2, released on October 2023, High-Performance Order Storage (HPOS) is officially flagged as stable and will be enabled by default for new installations.
I would expect such a big new feature would be supported by this plugin after being stable and default for so long. I just wasted so much time debugging this.
The text was updated successfully, but these errors were encountered:
Very sad indeed. I updated to 4.23.0 and read what's new, I first saw the word HPOS and was happy, only to find out it adds a warning it doesn't work with HPOS. How could it not have a warning before and still not work with HPOS? 😞
Unfortunately, we do not support HPOS with version 4.23. However, we do support HPOS with our beta plugin, which you can download via our GitHub page (v5.0.0-beta.8)
This beta version is a completely new plugin, which is why we are cautious about making this version live. Over the past few months, we have been working hard to make this beta as stable as possible.
We encourage you to test the beta plugin and share any feedback with us so we can further optimize the plugin.
Plugin version
4.2.22
WooCommerce version
8.9.2
WordPress version
6.5.4
PHP version
8.2
What went wrong?
With a newly setup webshop that automatically setups for High performant orders, Myparcel does not work anymore.
Reproduction steps
Relevant log output
No response
Additional context
https://woocommerce.com/document/high-performance-order-storage/
I would expect such a big new feature would be supported by this plugin after being stable and default for so long. I just wasted so much time debugging this.
The text was updated successfully, but these errors were encountered: