Changelog

There’s a new version of WooCommerce Blocks available! Version 5.1.0 is now available on WordPress.org and GitHub.

This release includes better error reporting for incorrectly registered payment methods and some improvements to the emitEventWithAbort event emitter. There is also a bug fix related to email and phone field values being cleared unexpectedly with certain shopper behaviour. Read on for more details!

Better error reporting for incorrectly registered payment methods.

When a payment method registers using the payment methods extensibility interface, the feature plugin has some error checking to ensure that the dependencies the plugin lists for its script are actually available during the registration. Without this error check, it’s possible for incorrectly registered payment methods to prevent the loading of any checkout scripts due to the mechanism used internally for managing the loading order of various checkout scripts.

With this release, there are some improvements to the error message logged (PHP error logs and console log) when a payment method doesn’t have all its dependencies registered including:

• Clarifying this is specific to Cart and Checkout blocks loading process.
• Only loading the payment methods API interface when Cart and Checkout blocks feature is on (via the feature plugin).

Improvements to emitEventWithAbort

This is more of a internals update that impacts various event emitters using this function (onPaymentProcessing, onCheckoutAfterProcessingWithSuccess, onCheckoutAfterProcessingWithError). If you are a developer authoring a payment method that uses any of these events, your implementation should be unaffected by these changes. It’s mostly to prevent potential bugs where there are multiple payment methods in use by a store (that all implement observers for these events). You can read more about the change in this pr.

Fix for unexpected email and phone field value loss.

There was a bug that surfaced when shoppers filled out the email and phone field and then unchecked the “Use same address for billing” option. The email and phone values would be cleared.

This is fixed in this release so that any previously entered values are preserved when toggling this checkbox.

Changelog

Enhancements

• Improve error message displayed when a payment method didn’t have all its dependencies registered. (4176)
• Improvements to emitEventWithAbort. (4158)

Bug Fixes

• Fix issue in which email and phone fields are cleared when using a separate billing address. (4162)

There’s a new version of WooCommerce Blocks available! Version 5.0.0 is now available on WordPress.org and GitHub.

This release mostly contains behind the scenes refactors (as we gradually convert the JavaScript code to TypeScript), but also adds support for Batching in the StoreAPI, and fixes a visual bug with customer addresses on the cart page.

Dev Notes

Class Deprecations

Two internal classes (Automattic\WooCommerce\Blocks\Assets and Library) have been deprecated in this release, with functionality being moved to AssetsController and BlockTypesController.

Since these were internal bootstrap classes we don’t anticipate any external usage, but noting that these classes will be removed in a future release of Blocks.

Checkout Event Changes

The Checkout event onCheckoutBeforeProcessing has been renamed to onCheckoutValidationBeforeProcessing to more clearly articulate its coupling to the validation happening when the Checkout form is submitted. 

onCheckoutBeforeProcessing will be deprecated formally in the future.

Shared Settings Deprecation

Blocks offered a filter hook named woocommerce_shared_settings which could be used to change, add, or remove settings that are passed from the server to the client. This is now considered deprecated—a warning will be logged to the browser error console if used.

We recommend instead using the Asset Data Registry directly, so for example:

use Automattic\WooCommerce\Blocks\Package;
use Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry;
Package::container()->get( AssetDataRegistry::class )->add( $key, $value )

Doing this reduces the risk of conflicting or overwriting data, unlike the filter which allowed any setting to be modified leading to unintentional side effects.

Changelog

Enhancements

• Added support to the Store API for batching requests. This allows multiple POST requests to be made at once to reduce the number of separate requests being made to the API. (4075)

Bug Fixes

• Prevent parts of old addresses being displayed in the shipping calculator when changing countries. (4038)

Refactor

• Rename onCheckoutBeforeProcessing to onCheckoutValidationBeforeProcessing.
• Switched to rest_preload_api_request for API hydration in cart and checkout blocks. (4090)
• Introduced AssetsController and BlockTypesController classes (which replace Assets.php and Library.php). (4094)
• Replaced usage of the woocommerce_shared_settings hook. This will be deprecated. (4092)

There’s a new version of WooCommerce Blocks! Version 4.9.1 is now available on WordPress.org and GitHub.

This release includes some additional guards when entering Elementor Editor in a PHP 8.0 website, and such, it only effects websites in an environment with those conditions.

A similar update will be shipped in WooCommerce 5.2.1