Support Forum
Support › MB Custom Post Type › Title on Custom post is a must?Resolved
I have created a Field Group "Insect" with + 10 custom fields
I have created a Custom Post Type "Insect"
I have connected Field Group to "Settings/Location/Post types" = "Insect"
I have unticked the Custom Post Type "Supports" (selection to the right) so it only supports "Revisions"
I would like NOT to use post "Title"
Alternatively, I would like to use one of my custom fields as "Title" instead.
Reason is I want users to register Insects (and since these do not have unique names like "John" or "Claire" it does not make sense to have a field called "Title") - Seems WP requires "Title" to be filled in.
Is there a solution/alternative?
Thnx!
Hi Robert,
There are 2 things here:
Post title support:
I've just checked and seen that you can disable all features, except revisions, and here is my screenshot:
Use a custom field for post title
See this tutorial. It uses a custom field for post content, you just need to replace post content with post title.
Looks good "It uses a custom field for post content, you just need to replace post content with post title."
But since I have several Field Groups and this only applies to one of them, how do I filter that?
Additionally:
What is this and is this free to change? ...very confusing it is called "Title" too.
//Aakerman
I also prefer to work in the Admin interface (the Builder) since I need to test and change fields often in the beginning.
I can dabble with PHP and think I've found answers..but it is a bit challenging to understand, where code should go, how to handle relationships, how to handle existing fields in WP and also making this into a decent UX.
The Wysiwyg solution above does not solve Frontend registration. Nor does it populate into Custom table.
Any ideas or hints?
//Aakerman
Hi Robert,
But since I have several Field Groups and this only applies to one of them, how do I filter that?
You need to repeat the same hooks for other post fields. Note that: only for post fields (post title, post content, etc.), not all custom fields.
The Wysiwyg solution above does not solve Frontend registration. Nor does it populate into Custom table.
I'm not clear about this. It's about post content. What did you mean for frontend registration and custom table?