There’s a new version of the WooCommerce Blocks plugin. Version 3.4.0 is now available on WordPress.org and GitHub.
This release is mostly a fix release with a few notable bug fixes and a performance fix.
Fixed issue with shopper saved payment method overriding default selected new payment method. With this bug if a shopper had a saved card for Stripe but selected a new payment method and left the default selected payment method option (that might not be Stripe depending on what order your store payment methods are configured in), then Stripe would be attempted for making the purchase instead of the payment method selected.
Fix broken Cart and Checkout Block sidebar layout in some themes. We discovered that some Storefront child themes didn’t define box-sizing: border-box; for some elements, so we implemented a change that helps with more consistent Cart and Checkout display in those themes.
Improve performance of Checkout block. Some browser environments (in particular Firefox mobile) exhibited significant lag with the checkout block interactions. In this release we implemented some improvements to component structure and implementation that dramatically improves performance.
Remove hard-coded wp-login.php url. Rather than using a hardcoded path for the login link in the checkout block (when configured to show), we switched to using wp_login_url for generating this link. This exposes a login_url filter for stores that want more control over where shoppers login to the store.
Fix an issue with COD not showing when first enabled. Some WooCommerce blocks users were sharing with us about not seeing the COD payment method as an option with the blocks when enabled. We finally tracked down why that was happening and fixed in this release.
More automated tests added. This isn’t reflected in the changelog but I thought it’s worth mentioning that every release we’re increasing our automated test coverage of the blocks and critical flows to help surface problems quicker as we iterate on the blocks.
Changelog
Bug Fixes
- Ensure shopper saved card is used as default payment method (default was being overwritten in some circumstances). (3131)
- Fix Cart & Checkout sidebar layout broken in some themes. (3111)
- Fix product reviews schema date fields to use new (WP 5.5)
date-timeformat. (3109) - Use wp_login_url instead of hardcoding login path. (3090)
- Fix an issue with COD not showing when first enabled. (3088)
- Fix JS console error when COD is enabled and no shipping method is available. (3086)
performance
- Create
DebouncedValidatedTextInputcomponent. (3108)
refactor
- Merge
ProductPriceatomic block and component. (3065)
Develop with WooCommerce 
6 replies on “WooCommerce Blocks 3.4.0 release notes”
so include this in a woocommerce update , whats your point
On Tue, Sep 15, 2020 at 9:26 AM Develop with WooCommerce wrote:
> Darren Ethier posted: ” There’s a new version of the WooCommerce Blocks > plugin. Version 3.4.0 is now available on WordPress.org and GitHub. This > release is mostly a fix release with a few notable bug fixes and a > performance fix. Fixed issue with shopper saved payment meth” >
LikeLike
I’m not sure what the question is about specifically? These are release notes for the WooCommerce Blocks plugin released on WordPress.org.
LikeLike
Hi! I’ve been following these new cart and checkout blocks closely. They are really fantastic!
However, from the first version of these blocks I see that some headers do not work correctly.
By default they show a style, but hovering or clicking changes the style.
The headings are:
– Order summary (at checkout)
– Cart code (in cart and checkout)
You can see a demo here: https://compralibros.co/carrito/?add-to-cart=804
LikeLike
Hi there,
That behaviour is not something I’m able to reproduce on sites I test with. I suspect it’s either your theme or some custom code that is modifying the heading styles for these blocks.
LikeLike
Hi Darren! Thanks for answering.
The theme I use is GeneratePress Premium + GenerateBlocks.
Could you review what may be causing this?
Thank you!
LikeLike
For accessibility, those heading are actually a
<button>and not<h3>.Your theme seems to style buttons like this, causing this behavior. You can contact the theme developer for a fix there or try to fix it using CSS.
LikeLike