Are you on version 1.3.1? We had an issue with the logic regarding public taxonomies in the 1.3.0 and it should be fixed in 1.3.1.
If you’re still having problems with 1.3.1, then I request more details about what you’re trying to do so that I can better aid in debugging what’s going on.
I am on 1.3.1 (interestingly you didnt update your About CPT in 1.3.1, it still says 1.3.0 🙂
What i’m doing is creating a CPT, not public. I just want it to be used internally and we’ll pull from it selectively.
Then I create a new tax and want to attach it to the CPT, but the CPT does not show up in the “attach to cpt” checkbox fieldgroup. When i go back and make the CPT public, then it does show back up there. Make sense?
Ahh. That’s nothing related to the 1.3.0 release. It’s been something that’s been around for a long while.
See https://github.com/WebDevStudios/custom-post-type-ui/blob/master/inc/taxonomies.php#L248-L272
We default and fall back to just public taxonomies in case the user somehow doesn’t return the good value. Changing the return value to be the following should get you covered there.
add_filter( 'cptui_get_post_types_for_taxonomies', '__return_empty_array' );
The latter function is legit from WordPress core and does what it says. Providing an empty array to this filter should return all of the post types, regardless of public or not.
The code line above would go in your theme’s functions.php or some custom plugin you may have for customizations.
