Hey friendlyfire3!

There’s actually a couple different overhauls in the works. First, if you’re using the trunk, the relate data is no longer held in a separate wp_relationships table, but now in the respective meta tables. With that, the relationships were also opened up beyond just post-to-post; it’s now possible to relate users, posts, and comments in any combination (e.g. user-to-user, comment-to-comment, post-to-user, etc.).

Next, not available yet but was just finished internally, we finished a relate_query system (much like meta_query) that will support any combination of conditions. I’m pretty excited about it. 🙂

As for your scenario, I assume you’re using the WP-API v2 plugin? Keep in mind that WP 4.4 only has the core for the api, and none of the endpoints, yet. From there, all you need to do is provide the post_has/post_belongs arguments to the filter in the endpoint. Whatever you put in there is passed directly to the wp_query, like you would normally use.

Hope that helps!

I’m not the one that sets the timelines, but I believe it’s safe to say Q1. Still, don’t hold me on that, just take it with glib optimism. 🙂

Whenever you use the id endpoint, the api simply grabs the post with that id, no questions asked. It always returns one post. So whenever you want one or more posts, use the /wp/v2/posts/ endpoint, as that’s the equivalent of using get_posts (which is where post_has/belongs are useable).

So it would be something like this: site.dev/wp-json/wp/v2/posts?filter[post_has=1]

Make sense?

@friendlyfire3: I’m sure about the endpoint. Try using a standard wp_query argument (e.g. post__in) in the filter to make sure filter is working as expected. If another argument is working fine, let me know.

Hey friendlyfire3!

Interesting. I’m wondering if the api isn’t loading Piklist. Admittedly I haven’t tested this yet, and I won’t be able to write any proper unit tests until the standard endpoints are written in (I believe) 4.5.

Can you please try a couple things for me?

First, see if this works: http://site.dev/wp-json/wp/v2/posts?filter[suppress_filters]=0&filter[post_has]=1

If that doesn’t work, please try adding this to your theme/plugin:

add_filter('rest_query_vars', function($valid_vars) {
  $valid_vars[] = 'post_has';
  $valid_vars[] = 'post_belongs';
  return $valid_vars;
});

I’m thinking the api isn’t applying the arguments are they’re not being permitted.

Hope this helps!

Hey friendlyfire3!

Awesome! I’m glad that worked! That code won’t be necessary in the next version of Piklist, so let’s modify it so you don’t have any issues when upgrading Piklist in the future:

add_filter('rest_query_vars', function($valid_vars) {
  return in_array('post_has', $valid_vars) ? $valid_vars : array_merge($valid_vars, array('post_has', 'post_belongs');
});

Hmm.. So you’re hoping to create the relationships yourself between two posts? I want to make sure I understand you correctly. You’d have an “active post” of some sort, then select other posts that it’s related to, and somehow apply the new relationships via the API?

Hey friendlyfire3!

Hmm.. I’m afraid this puts you into a bit of a more complicated issue. You see, the GET endpoint you’re using uses the wp_query, which Piklist hooks into. So it’s a simple matter of using the post_has/belongs arguments in the query, and you’re good to go.

Creating a relation, on the other hand, is unfortunately more complicated, and in more than one way. Like I said earlier, in the version you’re using Piklist stored the relationships in a wp_relationships table. But, since then, it’s changed to the respective meta tables. Now, if you upgrade from one to the next, there’s an upgrade script that runs and stores all your existing relationships into the new form — nothing lost.

So here’s your options to get this working:

• First, keep your current version of Piklist and create a custom POST endpoint that receives two post ids — the owner and one being owned, and have it use the Piklist_Form::relate function to make the relationship. The biggest downside here is that when you do upgrade to a newer version of Piklist, you’ll have to change your code to the next option.
• Second, upgrade to the latest in trunk (which is in beta), and use the post meta endpoint to add the relationships (until we’re able to add some of our own custom endpoints). To create a relationship, you simply add a meta value to the post that <u>belongs</u> to the other. The key would be __post_relate and the value would be the id of the owner. Simple as that.

Glad to see that you’re pushing Piklist to what it can do. Sorry we’re not quite caught up with API stuff, yet. 😀

Sure! It’s an edge case. But it’s a cool one. 😉

Unless I misunderstand you, that’s already happening.

Let’s say I have two posts types, the standard blog post type, and an event post type. Now let’s say I want to be able to mark related blog posts whenever I create an event. What we have now is that for every event it has one or more posts; conversely, a given post belongs to one or more events.

So given that, you would retrieve in each direction like this:

// Note: suppress_filters needs to be false as by default get_posts suppresses custom filters

$related_posts = get_posts(array(
  'suppress_filters' => false
  'post_type' => 'post',
  'post_belongs' => $event_id
));

$related_event = get_posts(array(
  'suppress_filters' => false
  'post_type' => 'event',
  'post_has' => $post_id
));

Is this what you’re talking about?