[Resolved] Displaying Grandparent Post-Link on Grandchild Post

[Author]

Posts

[KentS9937]

I'm doing something very similar to the article at https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/displaying-fields-of-grandparents/. I'm trying to display the Post-Link field of the grandparent on the grandchild post.

Based on this support article https://toolset.com/forums/topic/displaying-grandparent/#post-590115, I think I need to include "id=$field-slug" when inserting the content template.

Following these instructions I tried inserting content template with the following.

[wpv-post-body id="$post-link" item="@property-in-a-city.parent" view_template="country-information"]

This isn't working. Can you advise if I'm on the right track to include the id="$field-slug"?

Thanks

[Nigel]

Hi Kent

That forum post pre-dates the updates to how post relationships work in Types 3 and you had better stick to the documentation to avoid mixing the two approaches. In particular, you no longer use the id attribute to refer to the parent post slug, you use the item attribute.

You have lifted this straight out of the documentation

[wpv-post-body id="$post-link" item="@property-in-a-city.parent" view_template="country-information"]

which is based upon the post types and relationships of the example, and presumably yours are different (unless you are exactly trying to reproduce what is in the docs).

Use the Fields and Views button to insert the shortcodes, and the Post Selection tab in the GUI to specify the source when it is anything other than the current post.

The documentation describes displaying grandparent fields in a View, but you may want to display then directly in the template for grandchild posts.

The basic steps are
- create a Content Template (not assigned to any post type) to hold the fields of the grandparent you want to display.
- imagine that the starting point for *this* template is the parent post. Use the Fields and Views button to insert the required fields, and the Post selection tab to specify that the source is the parent post from the "grandparent-parent" relationship (which, if this is the parent, will be the grandparent).
- now edit the template for the grandchild posts. Insert the Content Template you just made (again, with the Fields and Views button), and use the Post selection tab to specify that the source is the parent of the current post from the "parent-grandchild" relationship.

So, starting from our grandchild post, we insert a Content Template where we specify that the source is the parent post, so that the template "thinks" its context is the parent. So when the fields inside are told to display fields from the parent, it is the parent of the parent.

[KentS9937]

Thanks for your quick reply. What you described is what I first attempted. It wasn't working so I started looking for tips in the support forum. I now understand I was referencing an outdated solution. I'll go back and double check my relationships and content template. Thanks for your help.