Problem: I am trying to create a Layout for Search Results, but the Layout doesn't appear on the front-end of the site when I use a 3rd-party search tool.
Solution: Check the Layout applied to the Search results archive, and be sure to insert a WordPress Archive cell. Then check the URL parameters. The 3rd-party search tool is adding some parameters that seem to cause problems.
Problem: I have a View of child posts that I would like to filter by the value of a custom field on their parent post.
Solution: There's not a good way to filter based on parent post custom fields, so it's necessary to automatically set a custom field on the child post to match the field on its parent. You can use the following code:
function copy_parent_gender_field ( $post_id ) {
// when parent narrator post type is saved, copy its gender field to child audio posts
$post_type = get_post_type( $post_id );
if ( $post_type == 'narrator' ) {
$gender = get_post_meta( $post_id, 'wpcf-gender', true );
$audio_args = array(
'numberposts' => -1,
'post_type' => 'audio-sample',
'meta_query' => array(
'relation' => 'AND',
array(
'key' => '_wpcf_belongs_narrator_id',
'value' => $post_id,
'compare' => '=',
'type' => 'NUMERIC'
)
)
);
$audios = get_posts( $audio_args );
foreach( $audios as $audio ) {
update_post_meta( $audio->ID, 'wpcf-gender', $gender );
}
}
}
add_action( 'save_post', 'copy_parent_gender_field', 100 );
Problem: I have a View that loops over child posts and outputs each child post's taxonomy terms. I end up with quite a few duplicates I would like to remove from the list of terms.
Solution: In order to break apart the taxonomy terms, you must use spans and separators in the wpv-post-taxonomy shortcode like this:
jQuery(document).ready(function(){
var seenGenre = {};
// loop over spans
jQuery('.genre-string').each(function(index,item) {
var txt = jQuery(item).text();
var $div = jQuery(item).closest('div');
// if genre has been seen, remove this span
if (seenGenre[txt] || seenGenre[txt + ', ']){
jQuery(item).remove();
}else{
seenGenre[txt] = true;
}
// now reexamine the parent div and see if it should be removed for lack of content
if($div.text() == ''){
$div.remove();
}
});
});
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.
