This thread is resolved. Here is a description of the problem and solution.
Problem: I would like to display a View of related posts in an M2M relationship. There is checkbox in the intermediary post type (in the relationship) and I would like to display only those related posts where the checkbox is unchecked.
Solution: This requires some custom code, and it also requires that the View is configured to display the intermediary post type. Add the following code snippet to filter by an unchecked checkbox:
add_filter( 'wpv_filter_query', 'unchecked_ints',99,3 );
function unchecked_ints( $query_args,$views_settings, $view_id) {
global $post;
$field_slug = 'release-artist-checked';
$views = array( 48324 ); /* "Collaborations" */
$ints_args = array(
'query_by_role' => 'child',
'role_to_return' => 'intermediary',
'limit' => 1000,
'offset' => 0,
'args' => [
'meta_key' => 'wpcf-' . $field_slug,
'meta_value' => 1,
'meta_compare' => '='
]
);
$ints = toolset_get_related_posts( $post->ID, 'supporting-artists', $ints_args);
// you should not need to edit below this line
if ( in_array( $view_id, $views ) ){
$query_args['post__not_in'] = $ints;
}
return $query_args;
}
Relevant Documentation:
https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/#toolset_get_related_posts
https://toolset.com/documentation/programmer-reference/views-filters/#wpv_filter_query
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 11 replies, has 2 voices.
Last updated by 3 years, 6 months ago.
Assisted by: Christian Cox.
Hello, it sounds like you want a way to filter out posts that have a value of '1' for this custom field, and only show posts that have no value set for this custom field. There is a quirk in WordPress custom field queries that makes this type of filter a bit more complex than others, because normally if you're testing for a custom field value and a post has no value for that custom field, that post is excluded from the query results. That's exactly what you want to accomplish though - get those posts with no value. So you'll need a small custom code snippet to overcome this quirk. I assume this View is set up to query the intermediary post type. If not, you should select the intermediary post type in the Content Selection area of this View. After that, you should add a Query Filter based on the checkbox field, and configure it as shown in the screenshot here - testing for a Constant value of 1 as a string. This screenshot is from a View built in the Block Editor, but you could do something similar in the legacy editor if you've built your View using the legacy editor experience.
I assume this is the only custom field-based Query Filter applied in the View? If not, I'll need more information about the other custom field Query Filters applied here to give you an updated snippet.
Once you've added the custom field Query Filter, the following custom code can be used to display only those posts with no checkbox checked:
/* ----------------------------------------------------------------
* FILTER INTERMEDIARIES BY UNCHECKED CHECKBOX
* In a View of Ints, only show ints with an unchecked checkbox field
* Toolset Support forum ticket: https://toolset.com/forums/topic/testing-the-value-of-checkbox-in-intermediate-post-for-many-to-many-relationship/
*/
add_filter( 'wpv_filter_query', 'unchecked_ints',99,3 );
function unchecked_ints( $query_args,$views_settings, $view_id) {
$field_slug = 'your-checkbox-field-slug';
$views = array( 123, 456 );
// you should not need to edit below this line
if ( in_array( $view_id, $views ) ){
if( !isset( $query_args['meta_query'] ) ) {
$query_args['meta_query'] = array();
}
$query_args['meta_query'][0] = array(
'key' => 'wpcf-' . $field_slug,
'compare' => 'NOT EXISTS'
);
}
return $query_args;
}
Replace your-checkbox-field-slug with the slug of the checkbox field from wp-admin. Replace 123, 456 with the numeric ID of the View of intermediary posts, or a comma-separated list of IDs if there are multiple similar Views. If you have used the Block Editor to create the View, the numeric View ID will not be obvious. To find the numeric ID in this case, you must enable the legacy View editor experience temporarily. Go to Toolset > Settings > General tab and activate the option "Show both the legacy and Blocks interface and let me choose which to use for each item I build". Reload the page after the option is saved, and you'll find a new Views menu item under the main Toolset menu. Go to Toolset > Views to find a list of all the Views you've created so far, and you'll be able to find the ID corresponding to the View of intermediary posts you created in the Block Editor. After you have that ID, you can deactivate the legacy Views experience if you'd like to continue using the Block Editor exclusively for Views designs.
You can add this custom PHP snippet in your child theme's functions.php file, or you can create a new custom code snippet in Toolset > Settings > Custom Code. Set the snippet to run everywhere and be sure to activate the snippet.
Once you've added the custom code, the View should return only those intermediary posts with an unchecked checkbox. If you'd like to display information about the related post in the View instead of information about the intermediary post, use the dynamic content feature to select the related post as the source of any dynamic content you choose. For example, you could use a Single Field Block to display the related post's title and link instead of the title and link of the intermediary post. Or you could display information from custom fields in the related post if you'd prefer.
Let me know if you have questions about this setup, and I can provide additional guidance.
Your first assumption - regarding the View querying the Intermediate post in the Performing On Relation - is incorrect; the Content Selection is Products ('Albums').
Okay, understood. Regardless of how it was originally configured the instructions are still the same, for technical reasons. In order to filter any View by a custom field, that custom field must be part of the post type being queried in Content Selection. In other words, you cannot filter a View of post type "A" by a custom field in a related post type "B", it won't work for technical reasons related to how WordPress queries are implemented. To filter by a custom field from post type A, the View must be set up to query post type A. To filter by a custom field from post type B, the View must be set up to query post type B. So in your case, the View should be configured to query the Intermediary post type, regardless of the information you want to display in the list of results. So you should select the intermediary post type in the Content Selection area of the View editor. Then in the loop of the View, by default it will display information from the intermediary post type. I take it you would prefer to display information from the related post type instead. So when choosing the source for a block's dynamic content, choose the related post type in the dynamic source fields.
Since new Album-Artist Performing On Relationships will automatically save a '0' as the default if 'Release Artist' is not explicitly checked, I realized the test for empty only applied to my existing records, so I simply edited them with appropriate 0 or 1 values.
We are instructed to advise against using the option that saves 0 when a checkbox is unchecked. That option is known to cause problems in custom search filters, and I suspect it will also cause problems in conditionals. Views will interpret unchecked checkboxes as checked in some circumstances when this option is used, and our developers have determined that this issue must be resolved on the data entry side by using the default setting "When unchecked, don't save anything to the database" (screenshot here). I don't recommend changing that default selection. I wish the developers would remove the option entirely, but for now it is what it is. Erratum post about this issue: https://toolset.com/errata/checkboxes-that-save-0-are-interpreted-as-checked-by-views/
We should be able to get this working with the custom code snippet and a View of the intermediary post type, and avoid the issue mentioned in the erratum post. If you're having trouble getting the correct results, or the display of the related post type is not working as expected with dynamic sources, I will be glad to take a closer look.
Thank you very much for your help and your clear descriptions and directions. I should've paid better attention the first time round.
The View is now for the Intermediate post and your code above installed and activated in Toolset Custom Code section. The first filter is for the 'Performing On' Relationship and the second filter tests the checkbox field in the intermediate post as you described above. This now works properly on the back end, displaying only the albums where the artist is collaborating and not their own albums (screenshot 1). However, on the front end the message "No items found" still shows up (screenshot 2) 🙁
Also, how do I display the 'Release Artist' Relationship for each of the Albums in this View? And more importantly, how do I add an 'Add to Cart' button for the Albums in this View?
New threads created by Christian Cox and linked to this one are listed below:
https://toolset.com/forums/topic/nested-view-inside-view-of-related-posts/
