 webmaster@gravitant.com
Post count: 1
|
I just added a new post type to an existing field set. The fieldset is not showing up on the edit page of that post type — even though other pre-existing field sets assigned to that new post type ARE showing up.
For example: I created a post type called Landing Pages. I assigned the existing field sets named “Banner” and “Benefits” to that post type. “Banner” is showing up on the edit screen for the landing page post type, “Benefits” is not.
Can you give me some idea of why this might happen, or how to debug?
|
|
webmaster@gravitant.com
Post count: 1
|
nevermind figured it out. I had named two fieldsets with the same slug
|
 traversal
Post count: 207
|
Great, I’m glad you were able to figure it out.
When field sets are named the same, field sets have an order of priority like so (ordered from lowest to highest priority):
1. shared field sets
2. post type, taxonomy, and user role field sets
3. template field sets
This allows you to override a shared field set with something more specific for post types, and then be even more specific for templates if you need to.
|
.