This was actually a quite serious problem since there are at least 
several places in IMP alone where loops inside of loops are required - 
and without if statements it is impossible to accomplish this.  This 
has been implemented in HEAD and Horde 3.1.0.

I finally had a look into this, and this isn't going to change. The 
code that sets things up needs to be responsible for setting any 
fields that you want to test against to false or array().



Why? Because Template doesn't look for what's in the template; it 
takes the data you give it and puts it into whatever it finds. So if 
you don't tell it about an index, it won't go find it.



So just set 'actions' => array() or => false, and this will work fine.

It is, and I found this annoying already too. I think the Template 
code needs to be fixed to support IFs for array members.

To better illustrate what I have on my mind I'll show you some code 
from Agora.



------- threads.php -----------

/* Set up the template tags. */

$template = &new Horde_Template();

$template->set('threads', $threads_list, true);



------ templates/threads.html ---------

  <loop:threads>

  <tr>

   <td class="<tag:threads.class /> nowrap">

    <tag:threads.link /><tag:threads.message_subject /></a>

    <span class="small">

     [<loop:threads.actions><divider:threads.actions>, 
</divider:threads.actions><tag:threads.actions 
/></loop:threads.actions>]

    </span>

   </td>



You can note, that if threads.actions doesn't exist, you only see [, ] 
in generated html code. And we cannot check it with 
<if:threads.actions></if:threads.actions> because template engine only 
can check top level array members for this, e.g. threads.



Hope that's understandable :)