Thank you for contacting us and I'd be happy to assist.
This is possible and you'll create a view for Review posts, with a post-relationship query filter, to show only posts related to the parent "Career" post, whose ID is passed through the view's shortcode attribute "wpvrelatedto".
( screenshot attached )
After that, you'll be able to pass on the current "Review" post's parent "Career" post ID ( i.e. [wpv-post-id item='@career-review.parent'] ) in the view's shortcode used on the single "Review" page, like this:
And just to confirm, this will show the Reviews from other Careers that share the same tag as the Review's Parent where the View is placed? Sorry, that might sound confusing.
Sorry about the confusion, as I originally thought you only wanted to show those Review posts, which share the same parent Career post. But now, I realize that you need to get the tags (taxonomy terms) attached to the parent Career post and then show all the Review posts which share the same tags (taxonomy terms).
Note: please change "tag" and "career-review" with the actual slugs of the target taxonomy and the relationship.
After that, just as suggested in the last message, you'll create a post view for Reviews posts, but this time add a taxonomy filter, that expects the target term slugs in the shortcode attribute.
( screenshot attached )
The view's shortcode with the shortcode attributes would look like this:
"I realize that you need to get the tags (taxonomy terms) attached to the parent Career post and then show all the Review posts which share the same tags (taxonomy terms)."
You're almost right except we need to go one more level deeper.
I want to show all Review posts whose Parent posts have the same tags as the Review's Parent where the View is placed.
For example,
Review A - Parent post's tag is Fitness.
Review B - Parent post's tag is Business.
Review C - Parent post's tag is Health.
Review D - Parent post's tag is Fitness.
Review E - Parent post's tag is Fitness.
In this example, I want to display Review A, D, and E because their Parent post's tag is Fitness.
This tag worked in showing the slug tag of the parent post:
You're correct and for this requirement, we'll have to go one more level deeper using nested views.
1. In a single Reviews template, you'll first need a parent view that gets the "Career" posts, where the tag slug value is passed through the shortcode attribute.
2. And, inside the loop of the parent view, you'll nest another view that shows the "Review" posts, related to the parent "Career" coming from the current loop item.
This means that the parent view will be using the "taxonomy filter" and the nested child view will be using the "relationship" filter.
Here's what I did.
1. Parent view - hidden link (Get Career posts with tag slug value passed through shortcode)
2. Parent view loop with child view in the loop - hidden link (Nest Review posts via the Child view)
3. Child view - hidden link
4. Child view loop with the review content HTML - hidden link
That "no items found" message is expected when the parent view is cycling through a career post, which doesn't have any related child review.
To avoid that message, please make sure that no content is added between the "[wpv-no-items-found]....[/wpv-no-items-found]" tags, in the Loop editor section of both these views.
There should be a cleaner way to do this. Even after I removed the content in the wpv-no-items-found]....[/wpv-no-items-found], there are still gaps in my content as shown in the screenshot.
The variance in the number of results in expected, because the available data items based on the set criteria will vary with each review post.
The parent view "(CAREER REVIEW) Related Posts" is set to show '4' career posts with a certain tag. But it is possible that 4 careers posts with certain tags are not always available.
Then the child view "(CAREER REVIEW) Related Posts Child" is set to show '1' review post, related to the parent view's career post. But, it is possible that a certain career post has no related review post.
Summarizing it, based on these two views, you'll get a fixed number of results '4' ( 4 x 1 ), only in an ideal situation where:
a) there are 4 career posts available with a certain tag
And
b) Those 4 career posts also have at least 1 related review post attached to them, which are different than the currently viewed review post.
( the currently viewed review post will be excluded by the child view, because of the option "Don't include current page in query result" )
As for the gaps in the layout, you can share an example link for the review post where this can be seen and I'll be able to guide you accordingly.
