Making Wayfinder Dropdown Templates Work with startId=0

Wayfinder dropdown menus often work at one branch level and then break when the same template is moved to startId=0 . The issue is usually not Wayfinder itself, but the assumptions the template makes about parent rows an

Wayfinder dropdown menus often work at one branch level and then break when the same template is moved to startId=0. The issue is usually not Wayfinder itself, but the assumptions the template makes about parent rows and branch depth.

Typical Call

[[Wayfinder?
 &startId=`0`
 &outerClass=`nav`
 &innerClass=`dropdown-menu`
 &parentRowTpl=`parentrow_tpl`
 &innerRowTpl=`innerRow_tpl`
 &level=`3`
]]

Main Lesson

Dropdown markup that works at one section root may not work globally because the top-level branch structure is different. Parent classes, wrappers, and caret markup all depend on where the menu starts.

When Wayfinder is used as a full-site menu builder, template logic should be validated against the real root-level tree, not only against one subsection.

Newer post

Sending HTML Cart Emails with eForm

How to configure eForm for HTML cart emails and inject item table markup into the final report message cleanly.

Older post

Debugging eForm Report Templates That Render Wrong Data

How to diagnose cases where eForm receives a field value but the report template still renders it incorrectly or not at all.