Skip Navigation

[Resolved] Intermediary Post Type naming convention

This support ticket is created 6 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 2 replies, has 2 voices.

Last updated by Stephen Vaughan 6 years, 5 months ago.

Assisted by: Beda.

Author
Posts
#912498

I notice that when you use an intermediary post type with the option to show it in the menu, posts that get created are listed like so:

Intermediary Post Type: Parent-Post-ID - Parent-Post-ID

If possible it might be bette if they were listed as:

Intermediary Post Type: Parent-Post-Name - Parent-Post-Name

It would make it easier to identify specific posts where you need to track down an intermediary field that needs amending.

#912921

I assume that was decided so to make it easier to know their ID as that is what you would use in Code, or elsewhere, not the Title, which may be the same for several posts.

Would you not agree that it is cleaner for this "technical" intermediary object to show an ID, which reflects the "technical" usage of this Post Type?
You will rarely display or even reference to these posts, in the new relationship, but rather query and edit directly the related posts.

#912926
Intermediary-Post-Link.jpg

Ok, I see what you mean, if you need to work programatically with IDs, they are more specific and some end users could actually enter the same title twice by accident.

How about if on the post relationship meta box (see my screenshot) the column for the intermediary post type had a link to open the post for editing the field or even a pop up with the field for editing. Not sure if any of this is technically possible so will leave it with you ant the dev team.