for loop broken?

[ophian]

I am testing upcoming Smarty 3.1.28-dev with the Sept 15 codebase. And found a smarty bug or changed behaviour, since the 3.1.27 release works well with it, without any error or notice for the image directory loop not being interlaced (stairs) any more.

    <ul id="library_dirs" class="option_list">
    {foreach $folders as $folder}
        {if ! $folder@first}
            {if $folder.depth > $priorDepth}
                <ul>
            {/if}

            {if $folder.depth < $priorDepth}
                </li>
                {for $i=$folder.depth+1 to $priorDepth}
                    </ul></li>
                {/for}
            {/if}

            {if $folder.depth == $priorDepth}
                </li>
            {/if}
        {/if}

        {$priorDepth=$folder.depth}

        <li>
            <div class="clearfix {cycle values="odd,even"}">
                <span class="folder_name"><span class="icon-folder-open"></span> {$folder.name}</span>
            </div>
    {/foreach}
    </li>
    {for $i=1 to $priorDepth}
        </ul></li>
    {/for}
    </ul>

I assume its the for not being read again... or such... (The code looks a bit strange, but it worked, though.;-) )
Array looks like

[0] => Array
        (
            [name] => trendy
            [depth] => 1
            [relpath] => trendy/
            [directory] => 1
        )

    [1] => Array
        (
            [name] => total
            [depth] => 2
            [relpath] => trendy/total/
            [directory] => 1
        )

    [2] => Array
        (
            [name] => total2
            [depth] => 2
            [relpath] => trendy/total2/
            [directory] => 1
        )

    [3] => Array
        (
            [name] => modes
            [depth] => 1
            [relpath] => modes/
            [directory] => 1
        )

etc
@uwetews

[ophian]

No sorry, it seems to be the @first which isn't being read. If I disable the {if !$folder@first} ... {/if} it works.

[ophian]

Again, Its the ! which isn't working. Using not instead is doing well! :)

EDIT I leave that for the WE. Its somehow weird at all.

[uwetews]

Thanks for bringing this up.
The fix is now in the master branch.