Custom Taxonomy CPT assigned to WooCommerce Breaks Taxonomy

@ryandgetz sorry Ryan, but that is not really the fix. If it fixed the issue for you great, but I never did any of that. This is a bug in woocommerce, and it acts completely unstable, until it starts working again. For me, I added the taxonomy another day and it started working. Strangely patch was issue the day, so clearly they changed something.

Ofcourse, Ryan here offers more solutions and help then Woo offers. If what you said is true, that this is fixed by woo itself, it is really screwed up that Woo wouldn’t support a built in feature. Given that they won’t even document a solution for their many other customers, this is why I wont be using this product much in the future. They don’t seem to be interested in solving the problems of their customers. Which as a software company, makes them pretty useless.

Imagine a world where bugs can stop people from selling items. Then imagine a company who ignores bugs. I wonder what will happen when the people selling products have customers who can’t buy products because some tech support guy wouldn’t look into issues due to “custom” software. Also, this is wordpress, anyone who has any plugins are “custom” which are everyone. So this support is useless.

• This reply was modified 5 months, 2 weeks ago by John Kostly.
• This reply was modified 5 months, 2 weeks ago by John Kostly.
• This reply was modified 5 months, 2 weeks ago by John Kostly.
• This reply was modified 5 months, 2 weeks ago by John Kostly.
• This reply was modified 5 months, 2 weeks ago by John Kostly.

Hello ?? @johnkostly1,

This is a bug in woocommerce, and it acts completely unstable, until it starts working again

I understand how frustrating it can be coming across a bug when trying to add custom taxonomies.

As my colleague had earlier suggested, should it be happening when using a default theme like Twenty Twenty-Four or Storefront with only WooCommerce as the active plugin in your store, please feel free to submit an issue via GitHub — by clicking on the green New issue button up-top, in the page linked here.

They don’t seem to be interested in solving the problems of their customers. Which as a software company, makes them pretty useless.

We are sorry to hear about your experience with taxonomies and the support you received. As you have a third-party theme and several active plugins in your store, we recommend troubleshooting the issue with having only Twenty Twenty-Four or Storefront with only WooCommerce as the active plugin to see if the issue persists.

This way, we’ll be able to rule out any possible conflicts between your theme and any active plugins in your setup, as this forum is dedicated to provide support for the WooCommerce core plugin.

Also, this is wordpress, anyone who has any plugins are “custom” which are everyone. So this support is useless.

We take your feedback seriously and are willing to support you, however, our hands are tied to only support the WooCommerce core plugin and as you’ve mentioned, most merchants have several plugins to enhance their stores. In that case, we always recommend trying to replicate the issue with a default theme and only have WooCommerce as the active plugin.

Once you are able to replicate the issue on a default theme with WooCommerce, you can then report the same on GitHub so that our developers can pick it from there and implement solutions to the bug.

I hope this helps.