Try passing false to the “Show Metabox Callback” field for the taxonomy. I can’t quite recall what I labeled it as, but it should be there if you’re on version 1.6.0.
There is an option called “Metabox callback”, however it is a text field to title the function name. I cannot find an option to make this “False”
Thanks!
That would be the field to use. Just have it save the value of “false” anyway. I may need to update it to reflect that you can use that value to disable/not show. Worth a try, for sure.
Hey Michael,
False changed how it displays, but it’s still essentially there (see difference between Sizess and Statess, ignore the typo because these are duplicate taxonomies). Would you have an idea when you plan to do the next update?
Thank you,
Mark Lisek
Snapshot of view
Hey Michael,
False changed how it displays, but it’s still essentially there (see difference between Sizess and Statess, ignore the typo because these are duplicate taxonomies). Statess has “False” on that meta field, whereas Sizess is blank. Would you have an idea when you plan to do the next update?
Thank you,
Mark Lisek
Snapshot of view
Not sure why it’s doing a “partial” removal, as I just tested it locally and it worked with removing completely. My taxonomy is “genre” in this example.
With the metabox: https://cloudup.com/cL6xB0gB2qh
With the callback set to false: https://cloudup.com/c8oHCRt1pE8
No set deadline at the moment for a next release, but this is what we have tasked up for it at the moment.
https://github.com/WebDevStudios/custom-post-type-ui/milestone/47
Subject to change if something else comes up that needs priority or is a good quick fix.
I realized I wrote “False”, which resulted in a partial removal. I changed it to “false” and it worked! Thank you so much for your help, you rock!
Interesting. I just tested that myself, and it’s getting considered to be a function name when capitalized like that, but one would also anticipate that WordPress core would handle a detail like that as well.
I’m going to open a partial bug for this one, where we handle potential variations of “false” being typed in.
Thanks for chiming in with this request, as it has helped unearth things we can do to improve the plugin 😀
