Thank you, but no, doesn’t work.

I think this is not the problem here because ‘scope’ is a piklist term that will be used to finally store the realtion in the corresponding meta table. As you see in my post the ‘scope’ => ‘post’ results in saving the relation correctly in the postmeta table. Piklist should do it in the same way with ‘scope’ => ‘user’ and save the data in usermeta.

No solution? Is there a bug tracker somewhere?

regards
Steffen

Thanks Jason for the answer.
It makes things clearer now for me but not clear enough (the ‘we need no field parameter’ part, later). If I understand relationships right in 0.9.9.x they are not bidirectional in the sense that piklist would make two database entries for the relationship. Instead there is only one entry in a meta table (postmeta or usermeta) which links the IDs and the use of the parameters you mention ‘user_has’,’user_belongs’, ‘post_has, ‘post_belongs’ etc.

What confused me was that there were two entries in the postmeta table in my first post-to-post example and I expected the same for the post-to-user relationship. The code for this is from the demo /piklist/add-ons/piklist-demos/parts/meta-boxes/field-relate.php and there IS a field parameter.

A search for ‘relate’ => array in the piklist folder gives three results:
/piklist/add-ons/piklist-demos/parts/meta-boxes/field-relate.php
/piklist/add-ons/piklist-demos/parts/meta-boxes/field-relationship.php
/piklist/parts/fields/post-relate.php

In field-relate.php and post-relate.php are ‘field’ parameters, in field-relationship.php not.

Now following the demo field-relationship.php I see there are 3 fields of ‘type’ => ‘group’ with no ‘field’ parameter.

Based on this here is my test post-to-user code with a field of type ‘group’ that works:

piklist('field', array(
	'type' => 'group',
	'scope' => 'user',
	'label' => __('DJs', 'rf'),
	'relate' => array(
		'scope' => 'post'
	),
	'fields' => array(
		array(
			'type' => 'checkbox',
			'field' => 'ID',
			'choices' => piklist(
				get_users(array(
					'orderby' => 'display_name',
					'order' => 'ASC'
				)),
				array('ID', 'display_name')
			)
		)
	)
));

This way I get entries in the usermeta table (links the selected user IDs to the Post ID).

But how should the code look in a non ‘group’ field type? Transforming to this does not work:

piklist('field', array(
	'type' => 'checkbox',
	'scope' => 'user',
	'label' => __('DJs', 'rf'),
	'relate' => array(
		'scope' => 'post'
	),
	'choices' => piklist(
		get_users(array(
			'orderby' => 'display_name',
			'order' => 'ASC'
		)),
		array('ID', 'display_name')
	)
));

No database entries.

So an example of how to use the ‘relate’ parameter in an ordinary field would be very helpfull.

Sorry, no. Does not work. Get no database entries. This is the full code:
1. post types in own plugin

add_filter('piklist_post_types', 'rf_post_types');
function rf_post_types($post_types)
{
  $post_types = array_merge($post_types, array(
    // post type for shows:
    'rf_show' => array(
      'title' => 'enter show name...',
      'menu_icon' => plugins_url('radiofrei/images/rf-menu-icon.png'),
      // labels
      'labels' => array(
        'name' => 'Shows',
        'singular_name' => 'Show'
      ),
      // wordpress features
      'supports' => array(
        'title',
        'editor',
        'revisions'
      ),
      // columns in admin
      'edit_columns' => array(
        'title' => 'Shows'
      ),
      // frontend - backend
      'public' => true,
      // slug
      'rewrite' => array(
        'slug' => 'shows'
      )
    ),

    // post type for episodes:
    'rf_episode' => array(
      'title' => 'enter episode name...',
      'menu_icon' => plugins_url('radiofrei/images/rf-menu-icon.png'),
      // labels
      'labels' => array(
        'name' => 'Episodes',
        'singular_name' => 'Episode'
      ),
      // wordpress features
      'supports' => array(
        'title',
        'editor',
        'comments',
        'revisions'
      ),
      // columns in admin
      'edit_columns' => array(
        'title' => 'Episode'
      ),
      // frontend - backend
      'public' => true,
      'has_archive' => true,
      // slug
      'rewrite' => array(
        'slug' => 'episodes'
      )
    )
  ));
  return $post_types;
}

2. Metabox for rf_episode

<?php
/*
Title: Related Shows
Post Type: rf_episode
*/
piklist('field', array(
  'type'      => 'select',
  'template'  => 'field',
  'choices'   => piklist(get_posts(array(
    'post_type'   => 'rf_show',
    'numberposts' => -1,
    'orderby'     => 'title',
    'order'       => 'ASC'
  )), array('ID', 'post_title')),
  'relate'    => array(
    'scope'     => 'post'
  ),
  'attributes'=> array(
    'multiple'  => 'multiple'
  )
));

I see all my shows and can select one/multiple but after saving no selection(s) and no database entries.

Yes, this works, it’s the same like the first field in my first post where I wrote that this works. It works bidirectional in the sense that I get two entries in the postmeta table:

– one that links to the selected post ID of post type ‘rf_show’:
post_id: 528
meta_key: my_relate
meta_value: 38

– and the second that links back (comes from the ‘relate’ parameter):
post_id: 38
meta_key: __relate_post
meta_value: 528

Maybe I’m not precise in my question. My point is that using the same code for a post-to-user relationship I get only one entry in the database. The ‘relate’ parameter does nothing in this case (look my second field in the first post). I get no back-link entry in the database.

Jason said, that I don’t need the back-link, which is true, but it’s confusing that the post-to-post and post-to-user relationship differs on this point. Following this approach (we need only one meta entry) the ‘relate’ parameter is unnecessary.

Then Jason said we should omit the ‘field’ parameter if we use the ‘relate’ parameter, but this
does not work.

So I think I use the following ‘classical’ approach without the ‘relate’ parameter but with a ‘field’ parameter:

piklist('field', array(
    'type' => 'select'
    ,'field' => 'my_relate'
    ,'template'  => 'field'
    ,'label' => 'Relate Posts'
    ,'choices' => piklist(
      get_posts(array(
        'post_type' => 'rf_show'
        ,'numberposts' => -1
        ,'orderby' => 'title'
        ,'order' => 'ASC'
      ))
      ,array('ID', 'post_title')
    )
    ,'attributes'=> array(
      'multiple'  => 'multiple'
    )
  ));

Regards

Hi Jason,

yes, there is no __relate_post entry in the database and I’m looking directly in the mysql database. I get the __relate_post entry only as long as I give a ‘field’ parameter.

Ok, it’s closer but not finnished.

I have these data:
——————
CPT: rf_shows
name Sendung1
id: 20

CPT: rf_episode
name: Folge1
id: 38

User
name: Hans
id: 2

With this code:

<?php
/*
Title: Sendeplanung
Post Type: rf_episode
*/

piklist('field', array(
  'type'      => 'checkbox',
  'label'     => 'Shows',
  'relate'    => array(
    'scope'     => 'post'
  ),
  'choices'   => piklist(get_posts(array(
    'post_type'   => 'rf_show',
    'numberposts' => -1,
    'orderby'     => 'title',
    'order'       => 'ASC'
  )), array('ID', 'post_title'))
));

piklist('field', array(
  'type'      => 'checkbox',
  'label'     => 'DJs',
  'relate'    => array(
    'scope'     => 'user'
  ),
  'choices'   => piklist(get_users(array(
    'orderby'     => 'display_name',
    'order'       => 'ASC'
  )), array('ID', 'display_name'))
));

I get in wp_postmeta:

post_id: 20
meta_key: __relate_post
meta_value: 38

and in wp_usermeta:

user_id: 2
meta_key: __relate_post
meta_value: 38

Thats OK. But I did not see the user checked in post editor although the database entry is correct (look at the attachment).

Is my use of post-to-user relationship wrong?