Meta Box

EDIT: as for the New > Relationships submenu, a Contributor cannot actually create a new relationship. It leads to a page with the only option to add a Title and Submit for Review. So at least they're not able to create new relationships -- but it's also a completely useless and potentially confusing menu, so I'd love to remove it

Views already offers the {{ author.ID }} variable, why can't I use that? I tried it and it makes the whole page break.

That said, to verify the code is working in the first place I replaced UserID with the value 7 (user ID of the author of a post I'm testing the View on) and it's still not showing anything...

Are you sure the code you provided is sound?

Peter,

I appreciate your answer, unfortunately it's not working.

Would it be an issue with from: UserID ? I wonder if it should be something else since I need providers connected to the post author, not the current logged in user visiting the page.

Here is the View I created with your input:

{% set args = { post_type: 'licensee', relationship: {
	id: 'user-provider',
	from: userID
} } %}
{% set posts = mb.get_posts( args ) %}
{% for post in posts %}
	
<a href="{{ post.url }}">
<div class="mb-container related-provider provider-related-to-user">

<div class="provider-logo">
{% set field = attribute( post, '_thumbnail_id' ) %}

{% for item in field %}
	<img src="{{ item.medium.url }}" alt="{{ item.medium.alt }}">
{% endfor %}
</div>

<div class="provider-name">
<span>{{ post.title }}</span>
</div>

</div>
</a>

{% endfor %}

"Exclude from search" worked! thank you

Nevermind, I found how to do it by checking off "Public queryable" in the Advanced options for that taxonomy.

Peter, it works thank you so much! I've been struggling with this for weeks!

Can you clarify what you mean by "You can pass object ID or full object"? I understand object ID, but what is "full object"? Do you mean the object ID, and any content field within it?

Hi Peter,

I'm not sure how to find/share the code for the query, it is generated by the GenerateBlocks Pro plugin. That's why I don't know how to pass relationship parameters to it, and the documentation is not helping me (I see the documentation, I just don't know how to use it for my use-case).

However I can share the code I'm currently using to filter the query based on a custom field (using Metabox' "Post" custom field to mimic a relationship):

add_filter( 'generateblocks_query_loop_args', function( $query_args, $attributes ) {
   
    if ( ! is_admin() &&
        ! empty( $attributes['className'] ) &&
        strpos( $attributes['className'], 'only-provider-events' ) !== false
    ) {
        return array_merge( $query_args, array(
            'meta_query' => array( 
        array(
            'key' => 'event_host', 
            'value' => get_the_ID(), 
            'compare' => '=',
        )
    )
        ) );
    }
 
    return $query_args;
 
}, 10, 2 );

Can I tweak this code snippet to pass relationship parameters?

If I can get this to work, I'll be happy to go publish the solution on the GeneratePress/GenerateBlocks forums, as I know I'm not the only one struggling with this.

Thank you Peter, even just that is incredibly more useful than the documentation.

And to clarify, I would put this code in my template file, right?