-
Notifications
You must be signed in to change notification settings - Fork 219
Filter by Attribute does not display attirbutes for imported XML products #9108
Comments
There's issue in WC Core re that: woocommerce/woocommerce#25698 |
cc @nielslange This issue affects our E2E test env (playwright). Any thoughts about how to fix it? We run the command to generate the table too:
|
Adding a bit more context: When I encountered this issue, I made an attempt of switching to CSV in a fork here, as the lookup table population works fine when data is imported through WooCommerce importer (using CSV). But then I found out WP importer supports only WXR (XML) files as per docs:
Also, the regeneration of lookup tables takes a while to complete (ref: p1681913867082209/1681818021.792209-slack-C02FL3X7KR6) |
Same here 😅
Gotcha! |
Thanks for reaching out, @gigitux. I'll look into this issue. |
@gigitux I looked into this issue, but I'm unable to reproduce it. At woo-test-environment, we're also adding attributes, before regenerating the product lookup table. @kmanijak Besides the testing steps that you listed above, can you give me additional steps on how to reproduce this issue? For example, on my end, I do not see the Product Template: |
Apologies @nielslange, I meant Product Catalog not Product Template 🤦 I updated testing steps |
No problem, @kmanijak. I've just looked closer into this issue, but I'm still unable to see the problem. Here's what I did:
Here's what I see on my end:
Could you try running the following command in your terminal: wp woo-test-environment teardown && wp woo-test-environment setup --blocks This tears down the current environment and sets it up again. Maybe the good old "have you tried turning it off an on?" also helps in this case. 🤔 |
I see why is that and again this is actually a missing information in Steps to Reproduce, which I took for granted. The whole thing is because the Filter by Attribute (and some other filters) have been updated recently in this PR, but that wasn't released yet and is scheduled for 10.1.0. That means it happens only on If I'm not mistaken, we can use any of the ZIP files from the PRs that were merged later 🤔 (TIL a lot about how to write better testing steps and describe issues better. Sorry for the trouble and I'm updating the issue description again 🙇 ). |
@gigitux regarding:
While I don't have all the details regarding your issue on Playwright, I suspect it might be the same we had with our current infrastructure: the tests were also failing on Puppeteer, as the process for creating and populating the new product meta-lookup table is deferred (triggered via a scheduled action) out-of-the-box: we managed to fix this limitation by enabling direct updates: See @albarin's PR: https://github.com/woocommerce/woocommerce-blocks/pull/9029/files |
@nefeline Thanks for point the PR! I will check it and implement it in Playwright too! 🙇 |
Description
Under certain synthetic circumstances Filter by Attribute shows "There are no products with selected attributes":
Filter by Attribute (and some other filters) have been updated recently in this PR, but that wasn't released yet and is scheduled for 10.1.0 (April 24). That means it happens only on
trunk
since that PR was merged. If you visit this issue later, then this version might've been released already so the issue could be reproduced there.Steps to reproduce
woo-test-environment
which imports the products hereMore details
This happens if products are imported through WP Importer (e.g. via
woo-test-environment
) and{prefix}_wc_product_attributes_lookup
is not correctly propagated. All works fine if products/attributes are added manually or imported manually as CSV.It may require update in WC Core do ensure the method that populates the table is triggered after the data import.
The text was updated successfully, but these errors were encountered: