|traversal||# Posted on August 22, 2013 at 10:04 am|
That’s a really tricky problem to solve, since the method of storage for taxonomy terms is very different to the way that WordPress stores post and taxonomy term relationships. You can setup a related term field in MasterPress, but this will store the data for that in post meta, so any standard WordPress queries on terms won’t just “work” as it’s a completely different database query behind the scenes. There are ways in the MasterPress UI to run queries around those field types, but those aren’t standard term queries in WordPress.
Probably the only way this could work better is to allow a custom UI for assigning taxonomy terms that replaces the standard WordPress UI.
To that end, what is it about the MasterPress field UIs specifically that you would like to see? Is it the selection interface that you like more than the built-in taxonomy UI?
Masterpress 1.3.6 is a compatibility release. It resolves an edge case with shared fieldsets not working for MySQL 8 when the fieldset is limited to more than 1 post type or taxonomy or excluding any post types or taxonomies.