The issue here is that the user has a button on their parent post that can be used to navigate to the child post. This button is passing the url to the child page.
Solution:
In this case we can just use the shortcode.
[wpv-post-title id="[wpv-search-term param='parent_post_id']"]
Now this will only work if the parent id is being passed in the url
Problem:
The client has a set-up where, from a parent post, a user can add a child post via a link to a front-end Toolset Form.
The particular requirements for this project are that only a logged-in user should be able to see and submit the child post form. Guest users should see a login/register form instead, and then continue to see and submit the child post form.
Solution:
There are two problems here.
The first is that guest users who register are not automatically logged in, they would register and be redirected to a log-in page, and then the flow would be interrupted.
The second is that, even if we add code to automatically log in users who register and then present them with the child post form, the URL parameter that identifies the parent is lost.
Problem: I would like to use the same View in multiple places on the same page, but I want to avoid unique IDs.
Solution: Use wpv-attribute to help generate that unique ID. For example, let's say you use the same View in two places on the same page. Add the placement attribute, and set some unique value for each View:
Problem: I have two custom post types in a M2M relationship, Persons (parent) and Project (child). I have added a custom field to the relationship, and I would like to sort a View of related Project posts using the custom field value. I would like to place that View of related Projects inside another View of Persons, to create a list of all Persons and their related Projects.
Solution:
- Make sure the intermediary post type is set to be visible. Go to Toolset > Post Types and edit the intermediary post type. Set the status to "Publish" and check the Options panel to be sure publicly_queryable, show_ui and show_in_menu are checked.
- Create a View of Projects. In the Loop Output area, insert a shortcode to display the post title.
- Create a View of Persons Projects (the intermediary post type). Set up a post relationship filter. Choose the correct M2M relationship and "related to the current post in the loop". Sort by the custom field value as needed.
- In the Loop Output area of the View insert a shortcode to display the custom field role information.
- Just after the role information, insert another post title shortcode. This time use the Post Selection tab in the popup to select the related Person post as the source of the title. This will display the related Person's name.
- Now insert the View of Persons Projects inside the Loop of the View of Projects, and insert the View of Projects somewhere to test it out on your site.
Problem:
How to Order child posts by “Custom Date Field” while having many-to-many relationships for custom post types?
Solution:
Orderby Custom Field works fine for normal posts or custom posts (non-relational posts). But the same solution is not possible with built-in options of Views for many-to-many relational data, so the orderby Custom date field and query filtering is being done by the following code. Please note that you will need to modify this code to add your post types, custom fields and other data to make it work for your site or setup:
I have created a custom shortcode [display_related_session_posts] and added following code in theme’s functions.php file and now the order is working good:
function display_parent_post_order_by_date_field( $atts, $content = '' ) {
extract( shortcode_atts( array(
'speaker_id' => '',
), $atts ) );
$child_args = array(
'post_type' => 'speaking-slot',
'numberposts' => -1,
'order' => 'ASC',
'meta_query' => array(array('key' => '_wpcf_belongs_speaker_id', 'value' => $speaker_id))
);
$child_posts = get_posts($child_args);
$parent_ids = array();
foreach($child_posts as $child) {
$parent_ids[] = get_post_meta($child->ID, '_wpcf_belongs_session_id', true);
}
$session_args = array(
'post_type' => 'session',
'posts_per_page' => -1,
'meta_key' => 'wpcf-start-date-time',
'orderby' => 'meta_value',
'order' => 'ASC', // We can change order from here ASC/DESC
'post__in' => $parent_ids,
);
$the_query = new WP_Query( $session_args );
// The Loop
$post_contents = '';
if ( $the_query->have_posts() ) :
while ( $the_query->have_posts() ) : $the_query->the_post();
$post_contents .= do_shortcode($content);
endwhile;
endif;
// Reset Post Data
wp_reset_postdata();
return $post_contents;
}
add_shortcode( 'display_related_session_posts', 'display_parent_post_order_by_date_field' );
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
