John Huebner

This is normal behavior. There is not check done when a post is deleted to remove any relationship from other fields.

This is the same way that ACF itself works. If you were not using a bidirectional relationship, if you edited post A to create a relationship with post B and then delete post B the relationship would still exist in post A. However, when you get a field ACF will not return posts that have been deleted, or that are in the trash.

Also, when you update the other post ACF should see that the post no longer exists and remove it from the relationship, though I’m not sure if this is the case when in the trash.

If you are getting the value without formatting it get_field('relationship', false, false) you will get the deleted post ID, under this condition it would be up to you to check to make sure each post exists.

I believe I have it fixed. Please test the update and let me know if you still have issues.

If you can add ACF fields to the post type used by events manager and those fields work, then this plugin can be used. But I can’t answer the question or how you would incorporate the fields into the events manager. That would be a question you’d need to ask them. I personally do not have any experience with that plugin.

What you want cannot be done with this plugin and is outside of the intended scope of this plugin.

This plugin will only create the 2 way relationship between the current post and the posts you add in the relationship field. It will not create 2nd level relationships. These would need to be created between those posts by editing posts 2, 3 and/or 4 etc.

This is because of z-index issue. The other plugin is using a z-index of 10000+. I’ll will have to make mine higher.

This plugin does not control who is allowed to edit ACF field groups. It only controls who can see/update specific fields when editing a post or other location where the fields are included.

Who can see or edit field groups is determined by an acf setting. https://www.advancedcustomfields.com/resources/acf-settings/

I just tested this and it is working correctly for me.
This is what I did.

I added a relationship fields on “Post” allows multiple selections
I added a post object field on “Page” that allows 1 selection
Both fields are named “relationship”
I added this code to my functions.php file

add_filter('acf-post2post/overwrite-settings', 'my_overwrite_settings');
function my_overwrite_settings($settings) {
  $settings['relationship'] = array(
    'overwrite' => true,
    'type' => 'first'
  );
  return $settings;
}

I added a page named “Page 1”, saved
I added a post named “Post 1” and I selected “Page 1” in the relationship field and saved it
I reloaded “Page 1” and “Post 1” was set in the post object field
I then added a post named “Post 2” and I selected “Page 1” in the relationship field and saved it
I reloaded “Page 1” and “Post 2” was set in the post object field
I reloaded “Post 1” and “Page 1” was removed from the relationship field.

I am assuming you have the same field names and that they are both at the top level of the field group since you said it was working other than this.

Check your code to make sure you have the same field name and that this field name is what you’re setting in your filter. I actually thought it wasn’t working at firsts because I had a typo when I added the code… it happens.

Do not try to work on and save multiple pages at one time. In the case I mentioned above, If I tried to update a page or post instead of reloading it, the result of the relationships will be based on the last page/post save and what is selected in the relationship/post object field, overwriting anything previously saved.