Categories
WooCommerce Blocks Release Notes

WooCommerce Blocks 6.3.2 Release Notes

A new version of WooCommerce Blocks has been released!
Version 6.3.2 is now available for download from GitHub and WordPress.org.

Wait! What happened to version 6.3.0 and 6.3.1? Don’t worry. You did not miss them. After releasing version 6.3.0, we noticed a few hiccups, which we addressed in two minor releases.

Changes

With WordPress 5.9 around the corner, we started converting classic WooCommerce templates, such as the single-product.php template, into block templates. These new block-based Store Editing Templates will eventually enable merchants to fully customize their templates with blocks in themes optimized for Full Site Editing.

As an intermediary step towards this goal, this first iteration of the feature renders the existing WooCommerce templates while allowing customization by adding additional blocks around them.

Let’s take a look at the new Store Editing Templates:

In addition, we addressed various bugs and improved the accessibility of the WooCommerce Blocks plugin.

Changelog

Enhancements

  • Add placeholder text when modifying product search input in the editor. (5122)
  • FSE: Add basic product archive block template. (5049)
  • FSE: Add basic taxonomy block templates. (5063)
  • FSE: Add single product block template. (5054)
  • FSE: Remove the do_action( 'woocommerce_sidebar' ); action from the LegacyTemplate.php block. (5097)
  • Fix duplicate queries in product grids. (5002)
  • FSE: Add abstract block legacy template for core PHP templates. (4991)
  • FSE: Add render logic to BlockTemplateController. (4984)
  • Improve accessibility by using self-explaining edit button titles. (5113)
  • Improve readability of terms and condition text by not displaying the text justified. (5120)
  • Improve rendering performance for Single Product block. (5107)
  • Improve the product images placeholder display by adding a light gray border to it. (4950)
  • Deprecate the __experimental_woocommerce_blocks_checkout_update_order_from_request action in favor of woocommerce_blocks_checkout_update_order_from_request. (5015)
  • Deprecate the __experimental_woocommerce_blocks_checkout_update_order_meta action in favor of woocommerce_blocks_checkout_update_order_meta. (5017)
  • Deprecate the __experimental_woocommerce_blocks_checkout_order_processed action in favor of woocommerce_blocks_checkout_order_processed. (5014)

Bug Fixes

  • Fix ‘Country is required’ error on the Cart block when updating shipping address (5129)
  • Fix label alignment of the product search in the editor. (5072)
  • Fix sale badge alignment on smaller screen. (5061)
  • Fix state validation to compare state codes, and only validate if a country is given (5132)
  • FSE: Fix missing is_custom property for WooCommerce block template objects. (5067)
  • Make order note block removable (5139)
  • Replace incorrect with correct text domain. (5020)
  • Scripts using wc-settings or script that depend on it would be enqueued in the footer if they’re enqueued in the header. (5059)

By Niels Lange

Moving bits & bytes around the globe for WooCommerce.

5 replies on “WooCommerce Blocks 6.3.2 Release Notes”

How do template overrides work into this? Pretty much all the big agencies use template overrides as opposed to just using hooks to create layouts that match their designs. Can the blocks html be overriden? Does the use of overrides preclude the use of blocks?

Like

With WordPress 5.9 and WooCommerce 6.0, it will be possible to overwrite the WooCommerce templates directly within Appearance » Editor. Merchants can then rearrange the various blocks of the WooCommerce Blocks plugin according to their needs. In addition, themes can overwrite these templates.

That said, it’s not possible to rearrange elements of the blocks currently. For example, the checkout block shows the Contact information, Shipping address, Billing address, Shipping options and Payment options on the left-hand side and the Order summary on the right-hand side. At the moment, it’s not possible to adjust the order of these sections or to move any of these sections to the other side.

The current blocks are build based on research on what converts best to maximize the revenue of merchants. That does not mean that we don’t consider the option of enabling developers to rearrange blocks according to their needs in the future. However, as by now, this is not possible.

Please also allow me to highlight that the WooCommerce Blocks plugin is currently a feature plugin to explore how WooCommerce can utilize the block editor in the future. Nonetheless, thanks for raising this question, and we’ve added this topic to our internal board for potential future developments.

Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.