Karol Manijak

Hi @mstudioeu,

I checked in the code and this item is combination of two translated strings:

• first there’s “Billing address” and “Shipping address” (in here)
• then there’s “Add %s” and “Edit %s” where the %s is replaced with the above (in here)

Seeing “Add адрес за фактуриране” means the “Billing address” has Bulgarian translation (here) but the “Add %s” translation is missing in here. It was apparently rejected so feel free to apply a better version!

Hope that helps, thanks!

Hi @agueda92,

Thank you for this suggestion!

As per Support Guidelines, Product Dependencies is a free plugin that is developed and supported on a voluntary basis. So please be aware there are no plans to work on or develop the plugin further.

Thanks!

Hi @wpdesigner4,

Thanks for providing the SSR and describing the error. Can you share the steps to reproduce the problem? When does the error occur?

Also, I see similar problem reported in GitHub issues (example). Can you confirm you don’t have some custom code that may integrate with WooPayments or WooCommerce?

Thanks,

Hi @kdimitrov,

We did deactivate all the plugins and theme as Xthemos ask us to do. And no the problem was not fixed. In the?Appearance > Customizer > WooCommerce > Product Catalog?If we change the number of products we get the desired result for the first page but if we change the page we get a lower number of products.

In this scenario, after disabling plugins and theme, can you tell us:

• which theme did you use?
• what did you use to display products? Was it a classic template, shortcode, or a block (and if so, which one?) If those terms sound unfamiliar you can share a screenshot of what you see when editing Appearance > Customizer > WooCommerce > Product Catalog.

I cannot reproduce the issue you mentioned but maybe I’m trying with a bit different setup so more details would be helpful.

Thanks!

Hi @ecabral,

I’m glad you like Raconteur theme!

Likewise, I can follow the same steps for the custom template. However, changing the width directly in the custom template will apply to the entire site (!).

Depending on a specific outcomes (and blocks you use in your custom template) there may be a bit different path to achieve it. But here are some general advice that may help:

1. You can wrap your content in “Group” block and then use an “Align” option in Toolbar settings to change between “None” or “Full width”. Some other themes offer also “Wide width” option but but it’s not available on Raconteur:

I’ve tried adding some additional CSS to the page template (with the assistance of my buddy GPT 4o, as I’m a noob in CSS…), but didn’t manage to target the right class.

2. You can assign a custom CSS class to the block from the Editor. That may be helpful to target the right class.

• Focus on a wrapping block,
• Open Inspector Controls (sidebar on the right),
• Expand “Advanced” tab
• Provide “Additional CSS classes”

I hope that may be helpful. Otherwise, feel free to share more details on your use case so we give you more specific advices:

• What’s the width you want to achieve (narrow the content or make it wider)?
• What are the blocks you use in your template?

• This reply was modified 1 month, 1 week ago by Karol Manijak.

So overall my shop now works much better. I am looking forward to these new faster filters you mentioned ??

@nullkohol, I’m so glad you gave it a try and it works for you! ?? If you have any feedback about the block, don’t hesitate to share it.

Looking through your documentation and at the template parts, I noticed this Template Part called “filter overlay”. I get a warning that my WordPress instance does not support this. How can i find out why?

“Filter overlay” template part is an unfinished feature exposed there by accident. It will be hidden in WooCommerce 9.2 until it’s finished and ready to use (PR). It’s related to the new filters I mentioned but they still require some work and polishing. Sorry you found it and got a warning.

but as long as it does not support front-end filtering, it’s not what we are looking for. I don’t like to use something that is already legacy/deprecated, but we need the functionality.

@nullkohol, can I confirm you mean filtering products without the page reload? This indeed is not the case between “Filter by *” and Product Collection block. We’re working on a new set of filter blocks based on Interactivity API which are server-side rendered as well (no additional requests on the frontend as the current filters) and won’t require a page reload with Product Collection to filter products.
Here’s the issue summarising new filters work.

Unless you mean that Product Collection doesn’t work with filters at all. Because that shouldn’t be the case. In that case, do you mind sharing a steps to reproduce? There’s a limitation in which Product Collection cannot be filtered on custom pages which was intended change, however eventually, we decided to allow filtering on pages as well (PR). That change will be available in WooCommerce 9.2 scheduled for August 13.

Hi @nullkohol! In addition to previous responses, I’d like also to recommend switching to the Product Collection block instead. Product Collection block offers bigger flexibility than All Products and is server-side rendered which means it renders faster as there’s no need for that many requests on the client-side. Also, we’re actively developing Product Collection while not putting much effort into All Products block.

We’re planning to hide All Products block from inserter (you can read about it more in Announcing the Product Collection Block). There’s just last extensibility bits missing in Product Collection block that we want to cover in Product Collection before that.

Check out the Product Collection documentation for more information. Don’t hesitate to share feedback after trying out the block as well!

Hi @khoavo,

Thanks for taking the time to kick off this discussion and share all the information.

it breaks my site and also instantly max out my web hosting CPU RAM memory (1 GB) to the max of 100%, causing overload on the server

I noticed some other users are experiencing the same issue (503 error, etc) when they installed WC v8.5.1

Do I understand correctly you were getting 503 errors on your site? Were there any other error details available while the site was broken?

My WordPress Theme Developer and my Web Hosting Technical Team did a thorough debugging & troubleshooting, and they determined that it’s not related to the WordPress Theme, nor can they figure out why WC v8.5.1 crashes the site and sucks up all the CPU RAM Memory on the shared web hosting server.

During the investigation, have you found any error logs even if they might seem unrelated to the issue?

Thanks!

Hi @nirb!

Can you explain in more detail what you mean by “main category”? As far as I know WooCommerce Core doesn’t provide a feature to set a category as main, so that may be added by some plugin. If so, we recommend reaching out to the plugin developer directly for further help.

I don’t have the “set as main” button that I have on other sites

But to verify it, it would be helpful if you could provide a screenshot of the expected outcome from the sites where it appears correctly.

Thanks!

The “Use same address for billing” box is uncheck in the editor. I then update but it goes back to being checked and is checked by default on the frontend.

Sorry to hear that! It matches the bug described in the provided issue #6603. My recommendation is to follow the issue for updates on providing the fix.

Thanks!

Hi @princejammy!

Thanks for raising this! I assume you’re using Checkout block and this is where you’d like to uncheck the billing address “Same as Shipping Address” by default? Correct me please if I’m wrong.

I found an issue in WooCommerce blocks that I think describes a similar problem: https://github.com/woocommerce/woocommerce-blocks/issues/6603. Can you confirm that solving this issue would satisfy your needs?

If so, I’d recommend following that issue for further updates. In the meantime, I also mentioned this thread in the issue for the developer’s awareness.

Thanks!

Hi @knockdownshooter!

There’s a similar issue reported in the WooCommerce Blocks repo:?https://github.com/woocommerce/woocommerce-blocks/issues/10847. Can you confirm the issue is similar and that you’re using WooCommerce Shipping & Tax?

If so, I’d suggest following the issue for further updates.

Thanks!

Hi @uriahs-victor!

They do not work for the products by category block. Is this intentional?

I double-checked that and I can confirm Filters don’t seem to work with Products by Category block, which I don’t think is intended.

This block is not actively developed and it wouldn’t probably fit the development roadmap to fix it, however, I would like to recommend you Product Collection (Beta) block instead! This block is newer and more flexible than Products by Category.

While being in the page editor:

1. Add Product Collection (Beta) block.
2. In the Inspector Control click three dots next to “Filters” and choose “Taxonomies”.

3. That will allow you to filter products by Categories

Product Collection will display only products from chosen categories and Filters will work with block as expected.

Please just remember, that nested categories won’t be included when choosing a parent category. Ss an example, let’s say I have categories structured like this:

• Clothing
  • Hoodies
  • T-Shirts

Choosing “Clothing” won’t automatically include “Hoodies” and “T-Shirts” but I need to choose them separately.

Please let me know if that works for you!

Thanks!

yes it’s the exact same error and behavior as per the issue you linked

In that case, I commented on the issue mentioning that you experienced the same problem. Also, considering there’s already some movement in the issue: https://github.com/woocommerce/woocommerce-blocks/issues/10847, I suggest following it for further updates until it gets resolved.

I’ve disabled shipping and tax for now and setup a manual tax instead.

I’m happy you were able to work around this!

Thanks!