Release: 2.6.0 #2554
Release: 2.6.0 #2554
Conversation
|
Size Change: +64.3 kB (3%) Total Size: 2.06 MB
ℹ️ View Unchanged
|
Co-authored-by: Albert Juhé Lluveras <[email protected]>
|
This is the result of the bundle change of files from the latest 2.5 release to master, this only includes *-frontend.js files
This is a full list of all files that existed or didn't exist. All Files
|
|
Follow-up tasks for after the release is tagged and published to wp.org
|
Testing Notes and ZIP for testingZip File for testing: Cart and Checkout BlocksAll Products
Specific changes to test for in this release.
Filter blocksThese blocks are used in tandem with the All Products block to provide filtering options on the content rendered by the All Products block. They include:
These blocks can be tested by adding them to the same page as the All Products block as the selected values in these blocks affects the products displayed by the All Products block.
Specific changes to test for in this release.Testing the price filter block with various settings around taxes and prices One fix in this release for this block is that when the price display setting (including or excluding tax) for WooCommerce differs from the price entered setting (prices input including or excluding tax), the displayed prices for filtered results from the entered Price Filter block might appear to be a mismatch (when it's querying based on the prices saved to the database). With this release, this is fixed so that no matter how WooCommerce is configured for displaying or saving prices respective to taxes, the displayed products will have prices matching the expected range set via the price filter block. To test:
And/Or labelling in Active Filters block
Dropdown display style to Attribute Filter block This release introduces a dropdown display style for the Filter Products by Attributes block (for both AND and OR type queries). Expected result:
To test:
**Add option to display an "apply filter button" for the Filter Products by Attribute block
All Product Grid based blocksAll of these blocks share a common ancestor for the PHP side registration, so it's good to test them together. These blocks include:
Specific changes to test for in these blocks for this release:
Other blocksThere are a number of other specific focuses for testing for changes in this release for other blocks: Featured Product BlockIn this fix, when a product is changed for an existing featured product block, the link in the button updates to the page for the new product. Note, if there is a custom url applied when the product is changed, this will be replaced by the url to the product (that's expected). To test:
Product Categories BlockSupport was added for showing category images in the Product Categories block. The following expectations:
|
… released versions
…r All products and Filter blocks
There was a problem hiding this comment.
Tested and didn't see any show stoppers or regressions. I followed the testing instructions and mostly tested in Safari and Firefox. I used an ephemeral site, set up the page content using Woo core 4.1.1, then upgraded to Woo blocks 2.6.0 rc1 (and deactivated plugin to test various upgrade / downgrade scenarios).
I noticed one issue, though this might not be a problem. With the Filter by Attribute block, the new Dropdown mode is available for both Query Types (Or and And). It works correctly, so this seems fine to me. (Testing instructions said it should only be available for Or.)
Also saw one other issue not introduced in this release, haven't logged an issue for it yet. With All Products, on mobile, with sale products, the sale badge is 100% width sometimes:
@Aljullu can you comment on this. Was there a follow-up pull that enabled support for "And" that got missed in the changelog or is it something already available in the 2.5 release branch? |
* Delete orders using delete method in batches of 20 * Batch size to variable * Tweak conditional for unit tests * Force delete of draft orders rather than trash
|
2.6.0 is released and follow-ups around documenting changes in process are handled in this pull. |
This is the release pull request for
v2.6.0of the WooCommerce Blocks plugin.Communication
X-WC-Store-API-Nonceheader (and nonce!) to our store endpoints that adds CSRF protection. This is particularly important for Cart and Checkout related write requests for a session.Note: For folks that have been testing the beta and release versions of the cart and checkout blocks, it's possible that they could experience this reported issue for the new orders list table in the WC-Admin. If this happens, the only way to fix currently is to manually delete orders in the
wc_order_statstable that don't have corresponding orders in thewp_poststable by executing this query (note if this is a db you care about, as a safety precaution you will want to backup first):The above query assumes
wp_is the prefix for tables in the db - change that to whatever the prefix is if it's different. You can also replaceDELETE statswithSELECT stats.*if you want to see what would be affected first.Impacts for this release on merchants
Blocks with a changeset
Besides the above notables, here's a list of other blocks that are impacted by changes in this release.
Quality
Note: Our automated test coverage is still being improved.
What this means practically is that a lot of heavy lifting is being done by manual testing for now.
Current REST API is internal only. The public API surface for integrations etc has not changed. The public API surface for payment method integrations is still subject to change.
Have you considered the impact of the changes in the release on other extensions and backward compatibility?
Does the release include a changelog entry in the readme.txt?
Please provide a link to testing instructions for this release. See here
Have you reviewed impacts to performance (bundle sizes, query time etc)?
Note: As noted by @senadir here, there is some impact to bundle sizes for frontend js built for the All Products and Filter blocks. We are aware of this impact which is caused by some dependencies pulling in DashIcons and have a potential fix that is not ready for this release. The target is
2.7.0for having this fixed so that when the feature plugin is updated in WooCommerce core this impact is not included there.