Multiple customs posts type and function add_local_field_groups

[hube2]

Multiple customs posts type and function add_local_field_groups

[Hube2]

This could have something to do with where and when you are adding the field groups in PHP.

In what file is your code?

When is it executed? Are you using a specific hook?

[psntr]

The field groups in PHP are in a file called bones.php which is directly called in the beginning of my functions.php

So in the bones.php I have all the functions hook. For the ACF field group I have this:

function my_acf_add_local_field_groups() {
if( function_exists('acf_add_local_field_group') ):
…
endif;
}

After that, in my functions.php I called the file containing my hooks:

require_once( 'library/bones.php' );

After the require_once, I have this function:

function rt_launch() {
require_once( 'library/custom-post-type.php' );

  // launching operation cleanup
  add_action( 'init', 'rt_head_cleanup' );
  // A better title
  add_filter( 'wp_title', 'rw_title', 10, 3 );
  // remove WP version from RSS
  add_filter( 'the_generator', 'rt_rss_version' );
  // remove pesky injected css for recent comments widget
  add_filter( 'wp_head', 'rt_remove_wp_widget_recent_comments_style', 1 );
  // clean up comment styles in the head
  add_action( 'wp_head', 'rt_remove_recent_comments_style', 1 );
  // clean up gallery output in wp
  add_filter( 'gallery_style', 'rt_gallery_style' );
  
  // Init ACF
 add_action('acf/init', 'my_acf_add_local_field_groups');
}
add_action( 'after_setup_theme', 'rt_launch' );

Below that group, there is other functions as such as:
add_image_size
update_option (size of some thumbnails)
$wp_customize->remove_section

—
Basically it's called after_setup_theme, as the hook is in my rt_launch function. What do you think?

[Hube2]

this is how it appears to me

On the Exhibition post type you have a relationship field name "artist_related", but on the Artist page you ave a field named "exhibition_related". If these two fields need to be bidirectional with each other then they are not named the same.

Exhibition and Work share a field named "artist_related", these two fields will be bidirectional. I don't think this is what you had in mind.

This means that selecting an "Artist" when updating a "Exhibition" the artist will not be updated because it does not share a commonly name field on the artist post type.

When I create fields to use with this plugin I try to name them using the post types that will be related.

for example, looking at your field setup you need 4 fields (7 actually counting the fields for each post type):
exhibition_to_work (used on the exhibition and work post types)
exhibition_to_artist (used on the exhibition and artist post types)
work_to_artist (used on the work and artist post types)
work_to_work (uses only on the work post type)

Sorry, I should have seen that in the OP. I didn't look at the fields you set up as carefully as I should have.

[psntr]

I took your comments in account and renamed the field accordingly. And now it works both ways!
You were right, I was a bit confused on how to use the field name for the relationship, but it's quite clear now.

Thank you for your help!