Does not support filtering by custom taxonomy

Hello @jqz,

Thank you for your feedback, it did point out our omission.

The point is that WooCommerce Product Filter by WooBeWoo supports custom taxonomies.

But there is no mention of this fact in the plugin’s documentation, we will add an article on this topic. Later I will add a link to this thread.

Currently, ACF custom taxonomies are supported for Free users, and CPT UI for Pro users.

Taxonomies are displayed using an attribute filter: https://joxi.ru/MAj0qX3SjDonem

We have added an article, please read: https://woobewoo.com/documentation/filtering-by-custom-taxonomy-compatible-with-acf-and-cpt-ui-plugins/

This doesn’t seem to help. Fields are not taxonomies. And in any case, neither method, including paid options, would appear to cater for hierarchical taxonomies.

Hi,

Please describe in more detail what exactly you want to achieve with custom taxonomies?
Perhaps we can add the functionality you need.

The taxonomy is a standard WordPress hierarchical taxonomy, registered using register_taxonomy() with the $object_type argument set to product, in exactly the same was as the product_cat (product category) taxonomy is registered.

Thus products may be classified by this custom taxonomy as well as product categories and tags.

• This reply was modified 4 years, 6 months ago by jqz.

Hi,

Please contact our internal support team.
We need more information to find the cause of this failure.

I am using a different plugin now for the current project.

To be fair, I tested about half a dozen similar plugins and all but one failed to pick up the custom taxonomy. To clarify, I mean a standard WordPress taxonomy (like proudct category or tag), not a ‘WooCommerce attribute taxonomy’ (which is a WordPress term but not a WordPress taxonomy, AFAICS, using the precise but curious WordPress jargon).

Hopefully that is enough for you to go on to see what is lacking.

I will certainly revisit your plugin for future projects ??

Hi,

So what exactly doesn’t work for you? We have implemented so that all taxonomies are displayed using an attribute filter. What exactly is the problem? Are your taxonomists not in the attribute list?

Please contact our internal support team.
We need more information to find the cause of this failure.

Turns out that custom taxonomies are only supported in the Pro version.