In 6.5.2, we were able to have pages in a sub-folder of the site that would build and show the managed navigation tree…even though they weren’t connected to the tree (navon had been removed from submenu slot of parent).
Not the case anymore with 6.7. The same scenario above produces pages with no managed nav present on the page.
It also breaks one other functionality we rely on (breaks it on those pages, anyway)…we use $nav.self.depth to determine depth of the page in the site and could modify the template accordingly. This doesn’t work anymore if the navon in that folder isn’t linked into the main site tree/Navtree. The value of $nav.self.depth for all of these pages returns 0 (zero).