Query loops with a "ACF relationship": me wrong or is it a bug?

Hi guys,
I freely admit that I don’t know enough about php, but it is precisely for this reason that I choose, since I discovered it, the Bricks Builder – which I feel much more logical and practical than Elementor pro, my previous builder.
So here’s the question: I am making a single post view template for a post which is related with another cpt (CPT-UI and ACF). I use the “query loop”, associated with “ACF relationship” [see first picture], to retrieve title and featured image of the related cpt and populates a grid with the results [see second picture].
So far so good!
However, when I want to add to feat. images the url-link to the related retrieved posts, I think the easiest way is to choose “post ID” in the feat. image link ref. [see third image] considering that I should always be within my query loop. But I’m wrong: I get this link “https://sitename/id-of-the-actual-post/id-of-the-related-post/” while I expected to have “https://sitename/id-of-the-related-post/”.

Where am I going wrong? I hope myself clear, English is not my cup of tea and even less technical English. If you want to answer me keep it in mind, don’t be too proof :wink:

Thank you
Luca

Schermata 2023-02-26 alle 17.20.37
Schermata 2023-02-26 alle 17.21.48

Not sure I understand you correctly but did you try {post_url}?

Yes I tried, but when the editor said “link rendered as:” (putting the link to itself instead the correct url) [picture] I believed him without verifying with a preview. I am sorry for my levity in not making a check, but I still point out that the indication in the editor can be misleading.
Many thanks for your reply, Aslotta

Schermata 2023-02-26 alle 20.27.27

Yes. The preview link doesn’t show the correct result often times. I noticed this as well. Glad that it works though. :relaxed:

Anyway I really find this builder very pleasant to use, it is very straightforward and leads to being used intelligently very quickly, compared to other builders. I have been using it for a little over 10 days and I am already in the process of adopting it in production. Many compliments!