Hi Sara!

Glad you figured it out! I felt like it had to be something simple, as you were doing everything correctly as far as I could tell.

Happy coding! 🙂

Bummer, I was hoping it was as simple as that.

So, to wrap my head around this, it looks like you’re creating a custom REST API endpoint, correct? Are you extending any of the existing endpoints (i.e. WP_REST_Posts_Controller)?

Does that exact query work outside of the REST API? Have you checked the output of the function via XDebug or something to see if the query is working but something else is the issue?

Wanted to throw in here that I took this opportunity to improve the Relationship documentation, per our discussion: https://piklist.github.io/docs/tutorials/relationships/working-with-field-relationships/

Hi @Sara!

Happy to help you with this. 🙂

First, did you happen to see this in the documentation? https://piklist.github.io/docs/tutorials/relationships/working-with-field-relationships/

Let’s break down your first query:
'field' => 'city_event',
You shouldn’t need this. If you do need it for some reason then the relate field isn’t working.

  'choices' => piklist(get_posts(array(
    'numberposts' => -1,
    'post_type' => 'city',
  )),
  array('ID', 'post_title')),

What’s happening there is that get_posts() is retrieving an array of WP_Post objects that contains all of your city posts. From there, the piklist() function is “plucking” the array, meaning that it’s creating a new array from the WP_Post array wherein the new array key is the ID and the value is the post_title. For a relate field to work it needs the value stored (key) to be the object ID, and the post_title is so the user knows what they’re looking at when selecting an option.

'relate' => array( 'scope' => 'post' ),

This is the “magic” line that sets the field up as a relate field. The scope here would either be ‘post’, ‘user’, or ‘comment’, based on what you’re connecting to. Since you’re connecting two posts, the scope would be ‘post’. If you see 'scope' in the context of the root field parameters, that’s for non-relate fields and most times doesn’t need to be worried about.

Here’s a working example of how I would structure what you’re doing:

piklist('field', array(
  'type'      => 'select',
  'label'     => 'Accociated City'
  'choices'   => piklist(get_posts(array(
    'post_type'   => 'city',
    'numberposts' => -1
  )), array('ID', 'post_title')),
  'relate'    => array(
    'scope'     => 'post'
  ),
  'attributes'=> array(
    'multiple'  => 'multiple',
  )
));

—

$related_events = get_posts(array(
    'post_type' => 'event',
    'numberposts' => -1,
    'post_belongs' => $post->ID,
       'suppress_filters' => false,
       'relate_query' => array(
          array(
            'id' => $post->ID,
            'relate' => 'belongs'
           ))
     ));

For this, you did get just a bit mixed up. Here’s what it should be structured like:

$related_events = get_posts(array(
  'post_type'        => 'event',
  'numberposts'      => -1
  'suppress_filters' => false,
  'relate_query'     => array(
    array(
      'id'    => $post->ID,
      'relate'=> 'has'
    )
  )
));

First, I put 'suppress_filters' in the root level parameters where it belongs.

Next, I changed 'relate' to 'has'. The reason is that since the city selection is on the event page, the event has the cities, not the other way around. And since we’re querying an event, we’re saying we want to limit the events by which cities the queried event has.

Hope this helps! I think the example in the docs should help, too!

Hi @dameer!

We just fixed this issue which will be in the next version of the 0.10 beta. We’re also pretty excited because in fixing this bug we got to do some really good optimization with revisions. It’s the little things. 🙂

Thank you for reporting!

Also, if this code is using the pre_get_posts hook, keep in mind that given the current restrictions, it will change the arguments of every single query that isn’t admin-side. You probably will want to do more things such as $query->is_post_type_archive('product').

To be clear, files should be set to 644 and directories to 755 as file permissions.

Hi @curiousprem!

While I can’t give you a specific date, I can say it’s our top priority to get 0.10 out, as it’s our most secure version, yet. The more people that help by creating issues and, especially, pull requests, the faster 0.10 will be released!

Thanks for checking out Piklist!