-
Notifications
You must be signed in to change notification settings - Fork 219
Review WooCommerce Blocks and ensure they work with the new Block Based widget area coming to WordPress 5.7 #3228
Comments
Posting this comment that will serve as a summary of my in-progress work. Set up
Known issuesCurrently, the widgets editor has some known issues that affect our widgets/blocks as well:
So when testing it's important to distinguish what's a Gutenberg bug and what's something specific to WooCommerce. Testing WooCommerce Core widgets in the new widgets editor
Issues found1 Products and Products by Rating have the initial value of Number of products to show set to 5, but after pressing Update, that value is replaced by 1. This change is only visible when looking at the frontend or by reloading the widgets editor screen. Testing WooCommerce Blocks in the new widgets editor
Issues found1
2 Product grid images are skewed (#3553). 3 Having an All Products block in the sidebar and another one in the post can cause unexpected behavior. For example, if you change the pagination in the All Products block in the post content from 4 Coupon code input and button have different heights (#3575): 5 After completing an order, the shortcode is shown (WordPress/gutenberg#27793): 6 It can only be added in one widget area. Testing WordPress Core blocks in Storefront
Issues found1 Cart button styles make it look disabled: Other issues
|
I'm sure you are already planning this Albert, but make sure you surface the WooCommerce core widget issues to Proton. I think that's something we can safely handoff to them to work on and we'll focus on the extensions we own along with Storefront and blocks compatibility with the new feature. |
@Aljullu it looks like most (if not all) of the things you found either have a tracking issue or are already have a fix merged. Can you confirm that? Do we need to keep this issue open or are there other things that should be considered as a part of doing work for Cycle 1? I'm moving this issue to the backlog for now but will pull back into the cycle anything that needs addressed depending on your answer. |
@nerrad yes, it's ok to close this issue. Everything that could be fixed on our end has been fixed and follow-up discussions are taking place in pca54o-KL-p2. |
WordPress 5.6WordPress 5.7 is scheduled to introduce the new block based widget areas in WordPress. For this issue, we will need to test all the WooCommerce blocks in this new UI and ensure they work as expected.We also need to review all WooCommerce widgets that are not converted to blocks yet and ensure they work with the new legacy widget wrapper/mechanism the block widget interface is adding.
(note block widget areas were punted to WordPress 5.7)
To expand this issue a bit (feel free to open a separate issue in Storefront if desired, I added here because I figured we'd be testing this issue in storefront anyways), let's see how WordPress core blocks work in Storefront with widget areas as well. Related, is this issue in the GB repo: WordPress/gutenberg#27458
The text was updated successfully, but these errors were encountered: