So does that mean that we need to improve the internal docs?<br><br>Currently MENU_VISIBLE_IN_BREADCRUMB says "Internal menu flag -- menu item is visible in the breadcrumb"<br><br>-Randy<br><br><div class="gmail_quote">
On Sun, Oct 3, 2010 at 11:12 AM, Daniel F. Kudwien <span dir="ltr"><<a href="mailto:news@unleashedmind.com">news@unleashedmind.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">> I don't understand this. breadcrumbs have always been messed<br>
> up for MENU_CALLBACK items, but so here's the question: How<br>
> do you get items to appear in the breadcrumb trail without<br>
> making them MENU_NORMAL_ITEM and having them appear in navigation?<br>
<br>
</div>The difference is that MENU_CALLBACK items are really just invisible<br>
callbacks now; i.e., plain router items, not having any kind of menu link.<br>
<br>
For edge-cases like the given example, in which you have a router path that<br>
does not contain any dynamic path argument placeholder (%), you want to use<br>
'type' => MENU_VISIBLE_IN_BREADCRUMB.<br>
<br>
We actually discussed whether we need a new constant, but since a new<br>
constant would be identical to MENU_VISIBLE_IN_BREADCRUMB, it would just<br>
have another name.<br>
<br>
sun<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Randy Fay<br>Drupal Module and Site Development<br><a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>+1 970.462.7450<br><br>