Creating tertiary (3rd level, stand alone) autonav that displays only parent and children?

Permalink
I'm stuck on an issue I can't resolve. I am working on a site which has a nav that can be multiple levels deep, sometimes even five. What I am trying to do is this:

I want to be able to drop an autonav block on a page that will show all the sub-items under that page (this is sort of like a tertiary nav, separate from the main nav). However, when a user clicks on one of the sub-items, I want this nav to still display all the sub items.

In other words, is there a way to configure the auto nav to display the child items of a section when they are on the parent page OR any of the child pages? Also, I don't want to have to create multiple versions of this so is it possible to do this without referencing the page ID?

Example:

FAQ's
-- faq1
-- faq2
-- faq3

I'd like the nav to look like that on the FAQ's parent page and on the faq1, faq2, faq3 pages but also look the same on:

Other Page
-- Other Page1
-- Other Page2
-- Other Page3

I'm totally perplexed on how to make this happen. It seems like the nav disappears when you are on a child item because it is looking one level below. Or, the nav doesn't display the right items when you are on the parent page.

 
jvansanten replied on at Permalink Reply
Here's some doc on the Autonav which illustrates its flexibility:http://www.concrete5.org/documentation/using-concrete5/in-page-edit...

The "Display Pages" is the parameter you want to work with.

Depending on precisely how your pages are set up, the "Beneath a Particular Page" may work. Alternatively, "At the current level" or "At the level above" may also work.

Sub-Pages -- likely "Relevant Sub-Pages"

Sub-Page Levels -- likely "Display All"

HTH
hollyb replied on at Permalink Reply
I don't these will work though, will they?

"Beneath a Particular Page" requires you to specify a specific page ID. I want to avoid this because this needs to be used on many different pages.

"At the current level" won't work because when a user is on the parent page, you won't be able to see the child items.

"At the level above" clearly won't work.

Unless I am not understanding you, I don't think any of these solve the problem.
jvansanten replied on at Permalink Reply
I understand better -- you're wanting to put this alternate menu in the page type rather than in the page proper so that it works automatically in all situations.

I agree, I don't think that AutoNav offers that flexibility. And, honestly, I'm not even sure that you can define this requirement in an algorithmic form. If that can't be done, it can't be programmed.

When I have a requirement like this, I just code the menu for that specific page.

Alternatively, you could define separate page types -- where the desired start page is different -- and then use the first alternative I suggested.

HTH