Thank you for clarifying a lot of these tags for me. I’ve been using plugins to acheive my subnavs, but if I can do it without, that would be fantastic. thanks again!

here is what i used:

<txp:section_list default_title=’<txp:text item=“home” />’ include_default=“1” wraptag=“ul” break=”“ form=“navbuild” />

navbuild form:

<txp:if_different>
<li<txp:if_section name=’<txp:section />’>
<txp:if_individual_article>class=“active”<txp:else />class=“active”</txp:if_individual_article></txp:if_section>>
<txp:section link=“1” title=“1” /></li>
</txp:if_different>

<txp:if_section name=’<txp:section />’>
<txp:article_custom section=’<txp:section />’ form=“navbuildlinks” wraptag=“ul” class=“subnav” />
</txp:if_section>

navbuildlinks form:

<li<txp:if_article_id> class=“active”</txp:if_article_id>><a href=”<txp:permlink />”><txp:title /></a></li>

Thanks for helping me with this!

An intelligent way to tackle Section, Landing and Article nav with pure TXP. And I can’t believe how timely it was me finding it, after I’d just decided to use Static pages for landing pages — your solution uses precisely this. Hurrah! Most grateful to you.

AND I’m a fan of DL too (not that ULs aren’t excellent too for nav ;)

Cheers!

I seem to have a weird problem with TXP, immediately following the appearance of the nav.

To test it, I add before and after, the section command so the page I am viewing reports the section I am on, like this:

BEOFRE: txp:section

txp:output_form form=“nav”

AFTER: txp:section

The section changes, the BEFORE one reports correctly, and the AFTER always reports the last section in TXP.

I have tried hard to find/fix this, even just creating a vanilla install of 4.0.7, but the problem persists.

It seems that in my line that brings the nav into my page:

txp:section_list form=“nav_build” etc…

if I include the form=“nav_build” attribute, then it goes wrong — even if I include it but then have nothing in the subsequent forms (empty them). So I don’t think your code is wrong.

Sorry this is vague and don’t feel you have to reply, I am just itching to use this nav solution and would love to work out the problem. I am wondering if it is a 4.0.7 problem(?) — although I can’t believe it is…

Thanks again in advance for the post in the first place, whether you have time to reply or not.

Cheers, -Alan

This problem I noted above is a bug in 4.0.7, about to be fixed in 4.08., I think.

Cheers, -Alan

See: http://forum.textpattern.com/viewtopic.php?pid=198217

1) The reason for the complexity is because the navigation is completely dynamic. It has to sniff out a lot of stuff in order to display the correct info. You can always hard-code nav links to avoid all of the conditionals.

2) Jonathan’s new tip is nice, but my solution is simpler :) …

txp:section list=“first,group,of,multi-article,sections”
txp:section name=“single-article-section” title=“1” link=“1”
txp:section list=“second,group,of,multi-article,sections”

Not very elegant, but it works like a charm, and allows me to retain explicit control of the order of the sections.

A question, maybe dummy. As far as the section list goes, the order of items is quite obvious. Since I am not TxP heavy user (just need this navigation, really), is there a way to sort (by title, for instance) the list of articles in sections? I mean the way these are displayed beneath the section names inthe navigation. Thanks in advance.

Another thing: why does my navigation show the article id in the url? Like this: /services/08/gutter-cleaning ? :-)

I’ve tried to extend the navigation by a third layer: sections/categories/articles

The problem I’m now struggling with is that whenever I navigate through section/category/article, my navigation is completely resetted. The categories fold again and my article list vanishes. I suppose that’s because the category isn’t handed over in the article url. Is there a workaround that or can I achieve building a 3-level navigation without using categories?

Thanks,
Sebastian

For instance:

• ABOUT
  - principals
  - history
  —- 1900-1955
  —- 1955 to present
  - news & press
  —- industry news
  —- company press

Side NOTE: I actually cant get “sticky” to work at all. Whenever it is used content disappears (e.g. if an article is set to “sticky” through the article tab, that article will not be displayed on the live site and is also removed from the article listing)

Any help, guidance or direction, would be greatly appreciated.
Thank you in advance

Whilst it’s essential to show the user where they are in your site structure, simply adding a class imparts nothing semantically. Neither does linking to the page you’re currently on in the same structure.

Personally, if the publishing platform I’m developing for will allow it (and Textpattern looks good enough to do it), I swap out the current page’s A tag in side navigation for an EM element.

By all means, keep the “current” class declaration in there if it helps programatically. But relying on non-semantic element attributes to imply location isn’t as broadly useful as using a meaningful element.