 Bart Dabek
Post count: 24
|
Hey Travis… is it me or is this a bit strange… if I create a new post type and want to use your fields to add taxonomies that cannot be done right?
The only way to have a custom taxonomy is to checkoff avialable taxnomies for that particular post type… but that automatically displays the default wordpress list of taxonomies… meaning there is no way to associate a taxonomy on a post type and only use your controls…
What I’m looking for is the ability to do the following..
1. Create a new taxonomy and assign it to a post type
2. Disable default wordpress taxonomy box for that taxonomy
3. The taxonomy would still be listed in the sidebar so we can add additional taxonomies
4. On the post type edit page we would use your field related terms to show that taxonomy so we can make it required and so the user can only choose one taxonomy
Is that possible in the current build?
|
 traversal
Post count: 207
|
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?
|
|
Bart Dabek
Post count: 24
|
Yeah kindda figured that… the main thing is being able to require a taxonomy and only to select 1 specific taxonomy.
But really no worries… I knew this was a long shot.
|
.