I worked on an example today, and I think that I got it working. Check this screenshot hidden link
Because of some limitations, and because it will need custom code, I used a different approach. These are the limitations:
- You are using the "wp_show_posts" shortcode to display the 3 posts. This way, we can pass the child's post to the views that we will use. You need to use a Toolset view instead of "wp_show_posts".
- We can't have 3 levels of nested values such as:
[wpv-view name="view1" parent="[wpv-post-id]" child=[wpv-view name="view2" parent="[wpv-attribute ="child"]" ]]
So, here how I implemented it:
1. Create a view that will display the posts hidden link
The view does not have any filters. It displays the posts, and we need to use it instead of the "wp_show_posts" to pass the child post(BATH venue) ID as an attribute
[wpv-view name="ts-posts" child="5067"]
2. Create a view to display intermediary posts related to a post from a shortcode attribute. Check this screenshot hidden link
hidden link
3. Custom code to change the view's query arguments. The code will get search for the intermediary post of the child post, and do the intersection:
add_filter( 'wpv_filter_query', 'get_intermediary_posts_by_subject', 30, 3 );
function get_intermediary_posts_by_subject( $query_args, $view_settings, $view_id ) {
// Execute this code only for my view id(7273)
if ( $view_id == 7273 ) {
// get the child post ID from the shortcode attribute of the parent view
$child_id = (int) do_shortcode( '[wpv-attribute name="child"]' );
// return the query arguments for an incorrect post ID
if ( !( $child_id > 0 ) ) return $query_args;
// get the intermediary posts from the child post
$intermediary_posts = toolset_get_related_posts( $child_id, 'post-venue', array(
'query_by_role' => 'child',
'limi' => -1,
'role_to_return' => 'intermediary'
));
// Perform the intersection with the posts returned by the view(from parent post)
$query_args['post__in'] = array_intersect( $intermediary_posts, $query_args['post__in'] );
}
// return the query arguments
return $query_args;
}
4. Use the view inside the loop of the first view(step 1) and pass the child and parent IDs:
[wpv-view name="ts-intermediary-post-for-a-post-venue" parent="[wpv-post-id]" child="[wpv-attribute name='child']"]
You can see that we get the parent from the current post in the loop using the wpv-post-id shortcode. And we get the child from the view's shortcode attribute "child" using the wpv-attribute shortcode.
5. Use the view inside the page(Elementor) and pass the child post(venue) ID to it:
[wpv-view name="ts-posts" child="5067"]
Please note that steps(2,3) may be enough, and will allow us to use this directly:
[wpv-view name="ts-intermediary-post-for-a-post-venue" parent="2528" child="5067"]
This way, you can build the page using Elementor(3columns) and display each post without using a view(steps 1,4,5).
Regarding the content box field, I am sorry, but still don't understand what is meant for. But, I don't think that it is a good practice to use a custom field as a template or design for displaying. Custom fields are meant to store data, content templates are mean for the "how to display the data".
I hope this helps. Let me know if you have any questions.
