This thread is resolved. Here is a description of the problem and solution.
Problem: Testing with the beta plugins broke my site.
Solution: Update to the latest versions of all Toolset plugins and migrate all relationships using the migration tool.
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 8 replies, has 2 voices.
Last updated by 6 years, 7 months ago.
Assisted by: Christian Cox.
Oh, okay, I didn't realize I needed to run the migration process. It did detect some conflicts in the functions file. I've attached a screenshot. It looks like it isn't liking the WHERE clause for "meta_key = '_wpcf_belongs_neighborhood_id'" I had to add a few of these functions, but they are very similar.
An example of the full function is:
add_filter('wpv_filter_query', 'parent_neighborhood_has_childs_func', 101, 3);
function parent_neighborhood_has_childs_func($query, $view_settings, $view_id) {
if ( $view_id == 2908 ) {
global $wpdb;
$ids = array();
$metas = $wpdb->get_results( "SELECT meta_value FROM wp_postmeta WHERE meta_key = '_wpcf_belongs_neighborhood_id'");
foreach($metas as $id) {
if(isset($id->meta_value)) {
$ids[] = $id->meta_value;
}
}
$query['post__in'] = array_intersect($query['post__in'], $ids );
}
return $query;
}
Since this is part of a SELECT statement and not a WP_Query argument ( like your site is showing at https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/ ), does this error/notice still apply...or is it just flagging it because it found "_wpcf_belongs"?
