MasterPress

Menu

Shared Fieldset not showing on Custom Post Type

This topic is: not resolved

Tagged: 

Viewing 3 posts - 1 through 3 (of 3 total)
Author Posts
September 8, 2014 at 10:16 pm #3524
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?
September 8, 2014 at 11:30 pm #3525
webmaster@gravitant.com
Post count: 1

nevermind figured it out. I had named two fieldsets with the same slug
September 9, 2014 at 9:41 am #3526
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.
Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Latest From the Blog

Ability to deactivate licence domains within MasterPress account management

25th October 2024

We have just rolled out an account management feature which allows licence holders to have better control over the domains that use their licence key. From the MasterPress Account Management page, the list of Active Sites that use your licence now includes a function that allows you to remove a domain from your licence. Simply… 

Plugin Requirements

MasterPress requires a minimum of WordPress version 4.9, MySQL 5.6, and PHP version 5.6.20.

We also recommend that PHP is configured to use a memory limit of 64MB per request (128MB may be required for sites with higher complexity).

This plug-in is not compatible with the WordPress.com hosted service.

Three AM