Tangible

Thank you for the issue description – the screenshot was very helpful.

It was indeed a compatibility issue with PODS. This will be fixed in the next version release, hopefully soon.

If you have any further questions or feedback, please feel free to join our discussion forum.

Hi!
This is definitely possible! I would approach it this way:

<Loop field=archive_term><Set term_id><Field id /></Set></Loop>
<Loop type=project taxonomy=project_type terms="{Get term_id}" taxonomy_2=featured terms_2=featured orderby=date order=desc>
  <div>
    <a href="{Field url}">
      <div class="fl-post-image">
        <Field image size="large" />
      </div>
      <div class="fl-post-text">
        <h2 style="margin-bottom: 0;"><a href="{Field url}"><Field title /></a></h2>
        <p><Field sub_head /></p>
      </div>
    </a>
  </div>
</Loop>

The rest of my response is just explanation, so you can just go ahead and copy-paste that code block and it should work 😀

The Loop tag gets the archive context by default if you just write <Loop></Loop>, but as soon as you add other attributes like your taxonomy filtering that context breaks down. So your instinct to open a project loop with terms=current was correct, however that doesn’t seem to work in my testing. (If you try it on your end again let me know if it works!)

Because the default Loop context on an archive is the posts in it, you need to open a separate loop to access the current term fields like title, ID and custom fields. You can use <Loop field=archive_term> on archives for this purpose. Inside my archive_term loop I saved the term ID as a variable to pass to the main loop using Set and Get

The part you were getting wrong is that your nested loops are unnecessary, as you can use up to three taxonomy filters on a single Loop. You’ll find the taxonomy attributes for the post Loop documented here.

Aside from that, nested Loops only inherit context if you tell them to, so your example could maybe have worked if you passed include="{Field id}" to the inside Loop (assuming the filter priorities work in the specific way we need them to, I haven’t actually tested it):

<Loop type=project count=1 taxonomy=project_type terms=current orderby=date order=desc >
  <Loop type=project include="{Field id}" taxonomy=featured terms=featured>
  <div>
    <a href="{Field url}">
    <div class="fl-post-image">
      <Field image size="large" />
    </div>
    <div class="fl-post-text">
      <h2 style="margin-bottom: 0;"><a href="{Field url}"><Field title /></a></h2>
      <p><Field sub_head /></p>
    </div>
    </a>
  </div>
  </Loop>
</Loop>

Hope that helps!

Please visit our discussion forum if you have any other questions!

Our reply was held for moderation 🙁 check back in a bit

This plugin seems to do a good job of finding your CCS!

Yes they can! For example:

<Loop type=taxonomy_term taxonomy=category>
  <If loop type=post taxonomy=category terms="{Field id}">
    <h2><Field title /></h2>
    <ul>
      <Loop type=post taxonomy=category terms="{Field id}">
        <li><a href="{Field url}"><Field title /></a></li>
      </Loop>
    </ul>
  </If>
</Loop>

In this example, the outer Loop is listing categories with their titles as headings. The If statement is testing whether a post loop exists for the taxonomy term, and the inner Loop is getting those posts as a list of linked titles. In the example the Loop context is being passed to inner loops via terms="{Field id}".

Does that answer your question?

I’m glad you figured this one out!

This reminds me of fetching the current logged-in user’s information. What in CCS was…

[user avatar]

…in L&L it becomes:

<Loop type=user id=current><Field avatar /></Loop>

There’s been some internal debate about this syntax and whether we should provide some shortcuts.
I’ll let Eliot explain the reasoning behind it and future plans there in more detail when he has a moment.

Although L&L has been in the repository for a few months, it’s mostly been used internally at Tangible and hasn’t been publicized in any way until this past week.
We’ve got a lot of content and improvements in the pipeline that we were hoping to get out before making a public announcement, but since we jumped the gun a little it’s a good time to let us know which specific examples you’d like to see first so we can prioritize what you’re most interested in seeing!

Hello! Yes, it is possible to loop direct children of the current post, or query the parent post.

The post loop has a field called parent, which can used like this:

<Loop field=parent>
  <Field title />
</Loop>

Similarly, there’s a field called children.

<ul>
  <Loop field=children>
    <li><Field title /></li>
  </Loop>
</ul>

These and other fields are documented here: https://loop.tangible.one/tags/loop/post

Please visit our dicussion forum if you have any questions.

• This reply was modified 4 years, 6 months ago by Tangible.

This question was answered on our forum: https://discourse.tangible.one/t/how-to-get-image-srcset/257