breadcrumbs messes up menu hierarchy in 1.9.1
Posted: Sun Nov 28, 2010 2:15 pm
In 1.9 there was an issue with page hierarchy in the {menu} tag (specifically the parameter number_of_levels didn't work properly), which was subsequently fixed in 1.9.1. Not quite.
It works fine until one also uses the {breadcrumbs} tag in a template. As soon as I add breadcrumbs to a template, the hierarchy gets messed up again.
Here's an example:
works as expected in 1.9.1, but as soon as I introduce the {breadcrumbs} tag to the template, it behaves as in 1.9, i.e not correct.
fmenu is very simple:
Without {breadcrumbs}, items 4.1, 4.2, 4.3, 4.4 and 4.5 get printed as they should be, but with {breadcrumbs} also in the template, 4.1, 4.1.1, 4.1.2, 4.2, 4.2.1, 4.2.2 etc get printed.
It works fine until one also uses the {breadcrumbs} tag in a template. As soon as I add breadcrumbs to a template, the hierarchy gets messed up again.
Here's an example:
Code: Select all
{menu template="fmenu" start_element="4.1" show_root_siblings="1" number_of_levels="1"}fmenu is very simple:
Code: Select all
{if $count > 0}
{foreach from=$nodelist item=node}
<li><a href="{$node->url}">{$node->menutext}</a></li>
{/foreach}
{/if}