Problem: I would like to give my site visitors the ability to use a checkbox in a custom search View that filters based on whether or not the post has child posts.
Solution: This filter is not built-in to Views, but you can set up a custom field on the parent post type that stores a 1 if child posts exists and stores nothing if no child posts exist. That custom field value can be managed automatically with code.
add_action( 'toolset_association_created', 'toolset_number_child_posts', 10, 5 );
add_action( 'toolset_before_association_delete', 'toolset_number_child_posts', 10, 5 );
function toolset_number_child_posts( $relationship_slug, $parent_id, $child_id, $intermediary_id, $association_uid ) {
// add a 1 if child properties exist to facilitate filtering by existence of child post
if( get_post_type($parent_id)=='developments' ) {
// get most recent property post
$property_args = array(
'numberposts' => 1,
'post_type' => 'property',
'orderby' => 'post_date',
'order' => 'DESC',
'toolset_relationships' => array(
'role' => 'child',
'related_to' => $parent_id,
'relationship' => 'developments_property'
),
);
$properties_query = new WP_Query( $property_args );
$properties = $properties_query->posts;
if(isset($properties[0])) {
// set the checkbox custom field value here using update_post_meta
update_post_meta( $parent_id, 'wpcf-has-vacant-properties', 1);
}else {
delete_post_meta( $parent_id, 'wpcf-has-vacant-properties');
}
}
}
function toolset_count_child_properties_on_save( $post_id ) {
if( get_post_type( $post_id ) == 'developments' ) {
toolset_number_child_posts( 'developments_property', $post_id, null, null, null );
}
}
add_action( 'save_post', 'toolset_count_child_properties_on_save', 1000);
Problem: I have a form that creates child posts, and I would like to link them to a parent post in the new relationships system. How can I set a post relationship between two posts using the Post Relationship API?
Solution: This feature is not going to be available immediately when Types 3.0 is released, and unfortunately we do not have a public API available yet. If you need to set post relationships programmatically, I do not recommend upgrading.
Problem: I'm trying using the Post Relationship panel of the Custom Post Type editor to connect to an existing standard Post, but I see the titles of another Custom Post Type called "Offices". I'm using the new Types 3.0-RC2.
Solution: In this case, it appears that the Property Hive plugin has a post type "Offices" that uses the label "Posts", so the Post Relationship was actually set up using the wrong post type. Creating the Post Relationship again using the proper Posts post type solved the problem.
Problem: The $current_page syntax does not appear to work as expected in the new Views 2.6-RC. Shortcodes using id="$current_page" show information about the current post in the loop, not the current page.
Problem: I have a custom search View that includes a select field filter. The label for this element is not connected to the select field using a "for" attribute, so the field is not optimized for accessibility.
Solution: We have a feature request in place to improve the accessibility of select fields in a custom search View, and in the meantime you can nest the control inside the label element. This is valid HTML and is more accessible than before.
Problem: After upgrading to Access 2.4.3.3, I am no longer able to use the Custom Fields editor screen in wp-admin. My site uses the M2M betas.
Solution: There appears to be a compatibility issue with Access 2.4.3.3 and the M2M betas. For now you can either install the stable Types and Views (no M2M) or downgrade to Access 2.4.3.2.
Nous documentons les problèmes connus et leurs solutions dans Toolset erratas. Pour gagner du temps, vérifiez d’abord dans cette rubrique si le problème auquel vous êtes confronté est un problème connu. Cette liste est volontairement courte. À chaque publication d’extensions de Toolset, nous nous efforçons de résoudre tous les problèmes connus.
Politique d’assistance
Le personnel Toolset vous guidera volontiers pour utiliser correctement les extensions Toolset, vous fournir les informations dont vous avez besoin, vous aider à résoudre les problèmes et vous conseiller quant aux meilleures pratiques.
Merci de veiller à ce que chaque ticket d’incident ne référence qu’un seul incident.
