Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

Review WooCommerce Blocks and ensure they work with the new Block Based widget area coming to WordPress 5.7 #3228

Closed
nerrad opened this issue Oct 1, 2020 · 4 comments
Assignees
Labels
focus: blocks Specific work involving or impacting how blocks behave. priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: cooldown Things that are queued for a cooldown period (assists with planning).

Comments

@nerrad
Copy link
Contributor

nerrad commented Oct 1, 2020

WordPress 5.6 WordPress 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

@nerrad nerrad added focus: blocks Specific work involving or impacting how blocks behave. type: wp dependency type: cooldown Things that are queued for a cooldown period (assists with planning). labels Oct 1, 2020
@nerrad nerrad changed the title Review WooCommerce Blocks and ensure they work with the new Block Based widget area coming to WordPress 5.6 Review WooCommerce Blocks and ensure they work with the new Block Based widget area coming to WordPress 5.7 Oct 20, 2020
@Aljullu Aljullu self-assigned this Dec 2, 2020
@nerrad nerrad added the priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. label Dec 5, 2020
@Aljullu
Copy link
Contributor

Aljullu commented Dec 11, 2020

Posting this comment that will serve as a summary of my in-progress work.

Set up

  • You need to install Gutenberg, ideally the latest version in master.
  • The widgets editor can be accessed from Appearance > Widgets.
  • There is an alternative view from Appearance > Customize > Widgets, but according to this post, it will change dramatically.

Known issues

Currently, 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

Widget name Works in editor? Works in frontend?
Product Search 🗸 🗸
Product Tag Cloud 🗸 🗸
Product Categories 🗸 🗸
Products 1 🗸
Products by Rating 1 🗸
Recent Viewed Products 🗸 🗸
Products by Rating 🗸 🗸
Recent Product Reviews 🗸 🗸
Active Product Filters 2 🗸
Filter Products by Attribute 2 🗸
Filter Products by Price 2 🗸
Filter Products by Rating 2 🗸
Cart 3 🗸

Issues found

1 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.
2 WC Core filter widgets are invisible when previewed in the widgets editor. That's because they are only visible in the shop page, but it looks quite confusing for users.
imatge
3 In WC Core Cart widget, only title is visible when previewed.
imatge

Testing WooCommerce Blocks in the new widgets editor

Widget name Works in editor? Works in frontend?
Featured Product 1 🗸
Featured Category 1 🗸
Hand-Picked Products 1, 2 🗸
Best Selling Products 2 🗸
Top Rated Products 2 🗸
Newest Products 2 🗸
On Sale Products 2 🗸
Products by Category 1, 2 🗸
Products by Tag 1, 2 🗸
Products by Attribute 1, 2 🗸
Product Categories List 🗸 🗸
Reviews by Product 1 🗸
Reviews by Category 1 🗸
All Reviews 🗸 🗸
Product Search 🗸 🗸
All Products 1, 3, 6 🗸
Filter Products by Price 1, 6 🗸
Filter Products by Attribute 1 🗸
Active Product Filters 1, 6 🗸
Cart 🗸 4
Checkout 🗸 4, 5

Issues found

1 SearchlistControl has some style conflicts (woocommerce/woocommerce-admin#5901):

Widget editor Post/page editor
imatge imatge

2 Product grid images are skewed (#3553).

imatge

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 1 to 2, the grid of the All Products block in the sidebar gets updated too, but the pagination components is still marking 1 as the current page. A similar issue happens when interacting with the sort select: product grid is updated in both components but the select is not synced.

4 Coupon code input and button have different heights (#3575):
imatge

5 After completing an order, the shortcode is shown (WordPress/gutenberg#27793):
imatge

6 It can only be added in one widget area.

Testing WordPress Core blocks in Storefront

Widget areas Works in editor? Works in frontend?
Sidebar 1 🗸
Below Header 🗸 🗸
Footer Column 1 🗸 🗸
Footer Column 2 🗸 🗸
Footer Column 3 🗸 🗸
Footer Column 4 🗸 🗸

Issues found

1 Cart button styles make it look disabled:
imatge

Other issues

  • Several core widgets have their block equivalent. As a user, it's not clear what's the difference between them. In some cases, they are almost the same (Product Search), but in some others, they work completely different (ie filters: the widgets work in the Shop page and the blocks work with the All Products block).

@nerrad
Copy link
Contributor Author

nerrad commented Dec 15, 2020

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.

@nerrad
Copy link
Contributor Author

nerrad commented Jan 3, 2021

@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.

@Aljullu
Copy link
Contributor

Aljullu commented Jan 4, 2021

@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.

@Aljullu Aljullu closed this as completed Jan 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
focus: blocks Specific work involving or impacting how blocks behave. priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: cooldown Things that are queued for a cooldown period (assists with planning).
Projects
None yet
Development

No branches or pull requests

3 participants