For example, I still want to be able to choose the number of posts that are queried. I create a relationship between my testimonials and services so I can show testimonials that are related to a specific service on a service page. I still need to be able to choose the number of testimonials I query even when querying from this relationship (among many other examples)…
I have a custom post type of event and locations. The two are related via a mb relationsship.
How to show the events of locations?
First div loop → for locations - here you can set how many posts you want to show
Second div loop → mb relationship event - location
Now if you add a dynamic heading for the post title it shows you the events for all locations
If you would disable the second loop it would only show the locations. If you enable the second mb loop it shows you the events name related to the locations.
I prefer how Oxygen gets the relationship. It’s simply a post query with post__in filter of the relation field.
But the problem of bricks now is: 1. Post query’s post__in filter does not support dynamic data. 2. Bricks gives a dedicated relationship query. But this query, like you said, has no additional options.
I have also come to a use case where I need the additional parameters in order to achieve my full desired outcome. I am getting the proper data outputted, however, I would like to: change the order, and exclude the current post.
Another vote for me for this feature as well! I have posts with hundreds of relationships so can’t purely show all the related posts. I need to be able to easily set the number of posts per page.
Same here. New to bricks. Using Metabox relationships or ACF relationships on query loop looses the rest of query settings. Such a let down. Why is this so hard to implement?