You can’t separate opening and closing tags like that. Try this:

{if segment_2 == "tag"} 
  {exp:tag:entries weblog="{my_weblog}" orderby="date" sort="asc" limit="15"} 
    <!-- all my fields --> 
    {title}
    {summary}
    {body}
  {/exp:tag:entries} 
{if:else}
  {exp:weblog:entries weblog="{my_weblog}" orderby="date" sort="desc" limit="15"}
    <!-- all my fields --> 
    {title}
    {summary}
    {body}
  {/exp:weblog:entries}
{/if}

What’s this Solvay Tag module?

o :-( That’s a shame. Although {title}{summary}{body} look a small piece of code above, in practice it’s much longer.

I would like to avoid double code for maintenance reasons.

Is it an idea to make a separate template for the {title}{summary}{body} tags and to include it here. It would then look like this:

{if segment_2 == "tag"} {exp:tag:entries weblog="{my_weblog}” orderby=”date” sort=”asc” limit=”15”} <!– all my fields –>

include <my posting template>

{/exp:tag:entries} {if:else} {exp:weblog:entries weblog="{my_weblog}” orderby=”date” sort=”desc” limit=”15”} <!– all my fields –>

include

{/exp:weblog:entries} {/if}

The question is: what would be the syntax of the #include line?

@Brendon: The Solvay Tag Module is a separate Module you can buy (about $30 dollars I remember). It’s very handy to tag your postings and to generate a tag cloud automatically.

I would like to avoid double code for maintenance reasons.

Use a sub template, then, why don’t you?

The question is: what would be the syntax of the #include line?

{embed=termplate_group/template}

The Solvay Tag Module is a separate Module you can buy (about $30 dollars I remember).

Actually, the company’s name is “Solspace” (Disclaimer: I do some support work for them.)

Hi Ingmar,

Thanks again for your help but this doesn’t seem to work as the subtemplates are not allowed to carry tags.

This implies the attached result.

The tags in de subtemplate do not seem to be rendered.

So the story continues…:-s

Erwin

btw: I’m using 1.4.2 (upgrading after the summer by someone else). I understood that were recently some bugs with this behavior which makes me hopefull for a solution in my version..

Thanks again for your help but this doesn’t seem to work as the subtemplates are not allowed to carry tags.

Of course they are. What you can’t do, however, is do something like

{exp:weblog:entries}
{embed=includes/template}
{/exp:weblog:entries}

… and have tags in “template” that rely on an opend {exp:weblog:entries}. As I’ve said, you can’t separate tags like that.

Oh yes, and you definitely should upgrade to 1.6. A few things changed, among them how variables are handled for embedds.

Tx again.

But this would imply that there is no solution for my wish. I always have to enter the tags:

<!-- all my fields --> 
    {title}
    {summary}
    {body}
  {/exp:tag:entries}

(which are in reality 2 A4 pages) 3 times: for tags, for search of for standard listings (incl archive and categories).

So sub templates are probably not the answer for my wish.

But it isn’t a strange wish, isn’t it? Just repeat a piece of intelligent code..

Hi Ingmar,

Just to explain further. I am actually looking for the solution of the following problem:

If View = Standard/Achive/Category 40 lines of code elseif View = Search 40 same lines of code elseif View = Tag 40 same lines of code endif

This explanation might further illustrate the issue im dealing with

I am sorry, my position hasn’t changed. I don’t why embedded templates should not work, especially with embedded variables that 1.5 (I think) brought.

or, and i can’t recall if 1.4 had this, use php on input to process the segment 2 conditionals rather than ee tag conditionals.