Toolset Types to CPT UI Conflict

  • Resolved cosmicfox

    (@cosmicfox)


    6 years, 7 months ago

    Hello,

    I was using Toolset Types to create custom taxonomy and fields. I then switched to CPT UI and ACF.

    I recreated all new taxonomy after switching.

    I have an AJAX filter which filters my WooCommerce products by custom taxonomy, which is now not working. This now doesn’t work with even the default WooCommerce “product_cat” taxonomy created by WC, and it also doesn’t work for custom taxonomy created by CPT UI.

    When I reinstall and activate Toolset types it works again. Otherwise, it shows no results when selecting one of the items in the taxonomy. The wp “get_terms” still shows the fields in the taxonomy, which I have displayed as buttons on my filter, but when I select one it shows no results without Toolset Types enabled.

    I can’t contact Toolset Types as their forums are locked to paying customers.

    This is on a localhost, let me know if I need to upload it to live for review.

Viewing 1 replies (of 1 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    6 years, 7 months ago

    I have to believe something within Toolset Types is filtering in or adjusting queries for you that make it work in this case, however I have no way of confirming. As long as the post types/taxonomies are being registered and are usable as a whole, then CPTUI is doing its programmed task. However, this issue is coming down to using the content created after the fact. Something likely revolving around the ajax filter is the issue. Wish I could be better help.

Viewing 1 replies (of 1 total)
  • The topic ‘Toolset Types to CPT UI Conflict’ is closed to new replies.