Hi @niwin, kudos on doing some serious troubleshooting there! Sorry our folks ghosted you on this thread after Eliot’s initial reply.
I think the source of this mix-up is probably the fact that Eliot introduced the concept of the Taxonomy loop shortcut which can be useful and succinct, but kind of obscures what’s going on. If you’re just starting out, that obscuration can make it a little tough to figure out what’s going on and troubleshoot it. I’d recommend playing around with the Loop
tag syntax rather than the Taxonomy
tag for now.
It seems like what you’re trying to do with <If check="{Taxonomy teknik}">
is to check if a taxonomy term loop exists and, if so, display the term(s). I see that Eliot suggested that syntax, but if I’m understanding the docs right, the Taxonomy
tag is a “shortcut for creating a taxonomy term loop” so you couldn’t just use Taxonomy teknik
as-is. Since Eliot suggested it, I imagine it’s an undocumented feature, but I couldn’t help with that since only Eliot knows how that works haha!
In any case, I’d ignore that shortcut for now and take a look at the Loop
tag documentation, specifically the feature that allows you to check whether a loop exists. Using that non-shortcut syntax, you’d end up with a conditional part of your template that probably looks something like this:
<If loop exists taxonomy=portfolio-category post=current>
<Loop>
<Field title />
</Loop>
<Else />
Do something else.
</If>
What I’m doing there is instead of just directly looping through the taxonomy terms as you mentioned you were able to successfully do with <Loop taxonomy=portfolio-category post=current>
, I’m instead passing that same information to the If
tag to first check if the loop returns anything and if it does, then I actually start the loop and display stuff, and do something else if there’s no data in the loop.
Hope that helps get you back on track with this!
By the way, if you need help with other issues down the road, another option is to make a post on the official L&L forum. It’s a much more active community so you might get faster support there on future support requests.