Hierarchical Default Setting

Hi,

I know that we do set a couple of things to not match default values from WP Core. However, for the most part, we try to default to the matched values that Core does use, and in this specific example, that would be hierarchical false.

Part of the problem is that it’s hard to decide what is “best defaults” for most users, as there’s so many potential use cases.

It sounds like part of your suggestions include a settings page (or something else) that CPTUI’s creation pages would follow whenever viewing the “Add New ___” tab. Correct?

Yes. A settings page for CPT UI that I could set some defaults like Hierarchical “True”.

Another suggestion from a UI standpoint is the settings page is so long, getting back to the top is a lot of “mousing”. Maybe use some tabbing or other UI design to compact the settings so that the page is shorter and we can get to the Save etc. easier (with less ‘mousing about ?? )

Thanks for listening.

Just for comparison, the Metabox CPT creator defaults to “Hierarchical”.

Noted on Metabox CPT making that decision.

I’m leaning towards no on switching that default, especially since we do have established default behaviors with this for many years. However, I’m not against the idea of maybe adding more visual help around that field.

I know we have the help text but people may not necessarily be reading that. So perhaps in larger text to the right, have it say “(Like posts)” or “(Like pages)” depending on which value is set.

For what it’s worth, we do auto-check the “page attributes” spot in the “supports” section when someone changes that hierarchical field to true, without absolutely forcing that to be used.

What do you think of the idea of adding a “back to top” UX, to help with scrolling?