Skip Navigation

[Resolved] Types Beta Relationships – Add intermediary post type optional?

This thread is resolved. Here is a description of the problem and solution.

Problem:
Why is there an option to include an intermediate post type when creating relationships with the betas of Types and Views that include the new post relationships workflow?

Solution:
If you want the relationship itself to store custom fields they need to be saved somewhere, and an intermediate post reflecting the connection between two other posts is the best place to do it.

For example if you have doctors and patients as custom post types in a many-to-many relationship, where patients are able to see different doctors and doctors obviously treat many different patients, then relationship effectively records appointments. And you would want the date and time etc. to be recorded for these appointments.

This support ticket is created 6 years, 9 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
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by GTD9219 6 years, 9 months ago.

Assisted by: Nigel.

Author
Posts
#606611

I know this is beta, but I assume it will be in the final, and I'm just curious.

In the Types beta Relationships wizard, what is the purpose of the checkbox to "Add intermediary post type"?

What happens if you uncheck that option when creating a relationship? Can you offer any additional guidance for understanding how to make decisions related to this?

#606676

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

The question revolves around whether you want to have custom fields that belong to the relationship rather than to the posts themselves.

Say you have doctors and patients as custom post types in a many-to-many relationship, where patients are able to see different doctors and doctors obviously treat many different patients. The relationship effectively records appointments.

Well, in such a scenario you will need to record info about the appointments, the date and time at least.

There needs to be somewhere to store such data.

For that, Types can create an intermediate post type which can then have custom fields.

There is no reason to create an intermediate post type unless you want the relationship itself to have custom fields as in the above example, rather than just the connected post types themselves having their own custom fields.

Does that make sense?

#606888

Yup... Thanks! It would be helpful and save yall time if some of those instructions were embedded in tooltips or something for the wizard.

yall rock.