• Resolved elaborate

    (@azinfiro)


    It looks like there’s an issue with displaying filters for product attributes that have been created (2) when editing a prodct directly as opposed to (1) creating the attribute separately and adding it to a product afterwards.

    To anyone who isn’t familiar, there are two ways to create a product attribute:

    1. On the Products -> Attributes admin page.
    2. On the Products -> All Products admin page, when editing or creating a new product.

    The issue mirrors a problem with WooCommerce’s own “Filter by Attribute” Gutenberg block, where you can add filters that have been created when editing a product directly (2), but they won’t display on the resulting page. With the “Filter by Attribute” Gutenberg block, however, you’ll see a warning on the Gutenberg preview that there are no products matching the attribute.

    It’s not straightforward to troubleshoot the issue, so it might be good if this plugin could prevent the user form adding filters for product attributes created when editing a product directly (2) in the first place, since the filter won’t be displayed anyway.

    Alternatively, maybe the plugin could display a warning when the user attempts to do this, similar to how the “Filter by Attribute” Gutenberg block behaves.

    • This topic was modified 1 month ago by elaborate. Reason: Broken blocks
    • This topic was modified 1 month ago by elaborate. Reason: Added images
    • This topic was modified 1 month ago by elaborate. Reason: Broken editor
    • This topic was modified 1 month ago by elaborate. Reason: Editor is useless; removed images again
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Nick McReynolds

    (@woobewoo)

    Hello @azinfiro,

    If I understood you correctly, you are talking about local attributes.

    These attributes are created when you create or edit a product. You cannot use these attributes to filter and they are only visible on the product page itself.

    “maybe the plugin could display a warning when the user attempts to do this”

    Unlike Gutenberg, the filter is not integrated so deeply into the WordPress Admin Panel and we do not participate in any way at the stage of adding Attributes to the Product, and it would not be correct to interfere in any way so deeply.

    As for creating an Attributes filter in our interface, there is no clear idea at what point to issue such a warning. Since there is no way to understand that the user would like to add a local attribute to the filter. And showing a warning to everyone would be annoying.

    However, if you have ideas on how to implement this correctly, we will be happy to hear them.

    Thread Starter elaborate

    (@azinfiro)

    Thanks for responding, and thanks for using the correct term. I wasn’t aware they’re called local attributes.

    I think you might have misunderstood me. It sounds like you assume I’m asking for some sort of integrating between your plugin and the WooCommerce product creation process. That’s not the case.

    Your plugin already displays local attributes within your plugin’s admin panel. Local attributes are available when selecting which attributes to tie to a produt filter. I’m suggesting you either (1) stop listing local attributes as options when creating a product filter; or (2) display a warning if for some reason you can’t exclude them.

    Plugin Author Nick McReynolds

    (@woobewoo)

    Hi,

    I have clarified the information regarding local Attributes at the moment.

    I was wrong.

    The Pro version of the plugin supports Local Attributes and allows you to build filters with them. Such Attributes are displayed with an asterisk at the end in the list of Attributes when creating a filter.

    The free version of the plugin does not allow you to use Local Attributes in filters, and does not display Local Attributes when creating a filter.

    If this does not work for you, please contact our support team
    https://woobewoo.com/contact-us/
    We’ll check what’s wrong.

    Thread Starter elaborate

    (@azinfiro)

    The free version of the plugin does not allow you to use Local Attributes in filters, and does not display Local Attributes when creating a filter.

    That’s odd. I was able to select local attributes on the free version when initially setting up filters, and I did not notice any asterisks when doing so.

    I only realized I was dealing with local attribtues because the filter did not display those attributes on the rendererd page, as I described above.

    I’ve since removed those specific local attributes, and I can’t replicate the issue when adding new ones. I’ll keep an eye on it and report back if I figure out how to replicate it.

    Thanks for looking into the issue.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.