Fog Creek Software
Discussion Board




Knowledge Base
Documentation
Terry's Tips
Darren's Tips

Multi-level navigation and file extensions

Hi, everyone!

Is there a way to make a site with multi-level navigation scheme (section, subsection, subsubsection, etc)?

Also, how do I change the generated file's extension to .asp?

Michael
Wednesday, December 05, 2001

Bah, no reply with quote!

> Is there a way to make a site with multi-level
> navigation scheme (section, subsection, subsubsection,
> etc)?

I was wondering about this myself, but it doesn't seem possible. I think the "right way" to do this would be to have a loop construct that returned all the folder names, then loop over them to get each article in turn. That's as opposed to simply using "all" in the loop. Then you just put things in properly named folders and presto.

As to making this fully recursive so you can have any depth, is that something that's really needed?

> Also, how do I change the generated file's
> extension to .asp?

That's easy, open the template, get Properties, and you'll see it.

Maury

Maury Markowitz
Wednesday, December 05, 2001

I'm close, so very close :) My 'workaround' for this involves adding the folder path an article resides in to the About2 section. Then, theoretically, my foreach loop listed below could know what folder the article is being published from, and return icons/name links for each. BUT, where I have placed "HELP" is the issue.

Putting .Extra2 as the help documentation explains I think evalutes to the literal string .Extra2 and putting nested {$.Extra2$} gives a code generation error on publish. Solve this and you with a cookie.

{$ foreach x in (folder "HELP") SortDescendBy .headline $}
  <div style="float:left;width:143px">
      <table width="125">
        <tr><td>
            <a href="{$x.link$}">
              <img src="{$x.extra1$}" border="0">
            </a>
        </td></tr>
        <tr><td align="center">
            <a href="{$x.link$}">{$x.headline$}</a>
        </td></tr>
      </table>
  </div>
{$ next $}

Of course, this doesn't solve much in the long-term because if you want to change the location of an article you then have to go and rewrite the path in the About2 folder. Might an article knowing it's own folder path string be in the works for version two?

Jamie

Jamie O
Sunday, December 09, 2001

The About1 above is my other 'workaround' that has the magicname of the image which is my display icon for the page being linked to.

Jamie O
Sunday, December 09, 2001

*  Recent Topics

*  Fog Creek Home