How to Show

834 Posts

MarkG Reply #1, 18 years ago

How do I set Wayfinder to display the "Not in Menu" container items?

IE This page has all the documents listed but not the title of the containing "folder"

http://httpwix.s.customers.ilisys.com.au/help-utilities/site-map-3

Call

[!Wayfinder? &startId=`63` &ignoreHidden=`0` &level=`3` &parentClass=`show` &parentRowTpl=`wfParentRow` &outerTpl=`wfOuter` &innerTpl=`wfInner` &rowTpl=`wfRow` !]

63 is the id of the container name I want to display.

The ignore hidden bit will display Not in Menu items in the folder/container but not the name of the container itself.

Thanks

Content Creator and Copywriter

☆ A M B ☆
24,524 Posts

sottwell Reply #2, 18 years ago

To show the start document there’s a parameter &displayStart=`1`. Specify how it’s displayed with the &startItemTpl parameter.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

834 Posts

MarkG Reply #3, 18 years ago

Thanks Susan,

but Wayfinder still seems like total voodoo to me.

I tried the &displayStart=`1` and nothing happened.

As for

Specify how it’s displayed with the &startItemTpl parameter.

I just don’t know what that means or how to do it.

I just want the start to appear.

Content Creator and Copywriter

1,390 Posts

kongondo Reply #4, 18 years ago

@markg

~~The parameter &displayStart will not work without &startItemTpl .~~
EDITED TO CORRECT ERROR. Yes, it will work with wayfinder’s in-built default startItemTpl if you don’t specify your own. See post below

Read the stuff below (this is in the zipped wayfinder documentation which you can find at the top of the page of wayfinder 2 in the wiki) for more info on how this works.

*&displayStart - This parameter must be used in concert with the &startItemTpl parameter.

* If the &displayStart parameter is set to TRUE (i.e. = 1), then WayFinder will need a template for displaying information from the starting document. (i.e. &startItemTpl)

* Note that, if &displayStart parameter is set to TRUE, then WayFinder will place the output of &outerTpl (which contains the entire menu structure!) into the [+wf.wrapper+] placeholder of the &startItemTpl, so be sure to include this placeholder in your custom template!

* If (and only if) the &displayStart parameter is TRUE, then the &startItemTpl template will be used. When it’s used, the &outerTpl template will be placed in the former’s [+wf.wrapper+] placeholder.

* If the &displayStart parameter is not TRUE, then the &startItemTpl template is not used, and the &outerTpl template provides the outermost container for WayFinder’s output.

*The default &startItemTpl template is:
<h2>[+wf.linktext+]</h2>[+wf.wrapper+]
You can create yours though...

So, bottom line is: when displayStart is set to true (i.e.=1) then &startItemTpl is king and will form the outermost structure of your entire menu. The two work in concert.

It was all confusing to me too...until I read the document I’ve mentioned above.

cheers/k

Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder

834 Posts

MarkG Reply #5, 18 years ago

Kogondo,

thanks, but as I said total voodoo.

As I and hundreds of others have said many times, we’ve read the Wayfinder documentation over and over and we just don’t get it.

Or rather, we understand what’s being said, we just don’t know what it means or how to implement what’s being said.

EG I typed in

 &displayStart=`1` &startItemTpl

and I get nothing.

What makes it more confusing is that I already have another Wayfinder menu that displays all of the Not In Menu containers and doesn’t use the &displayStart=`1` &startItemTpl code.

[!Wayfinder? &startId=`0` &level=`3` &parentClass=`show` &ignoreHidden=`1` &parentRowTpl=`wfParentRow` &outerTpl=`wfOuter` &innerTpl=`wfInner` &rowTpl=`wfRow` !]

That gives me a complete sitemap, but I want to reduce it to individual sections.

I thought if I could just tweak this one, then it would give me what I wanted, but obviously I’m completely wrong.

I can set the start id to the right section, but it won’t display the start container as I originally said.

Sorry to rant but I just find Wayfinder endlessly frustrating to try and understand.

grin

Content Creator and Copywriter

1,390 Posts

kongondo Reply #6, 18 years ago

I feel you mark grin

OK, 3 things

1. In your example above

&displayStart=`1` &startItemTpl

You haven’s specified the chunkfor &startItemTpl. Is this the way you specified it? If yes, I don’t think it should be empty.

Maybe you could post your chunks here for the menu that doesn’t work so that we could have a look at them? (including your &startItemTpl chunk since this cannot be empty if your are using &displayStart).

2. In addition, I believe you still have to specify the &outerTpl in your snippet WF call even if you use &startItemTpl, unless I misunderstood the documentation??

3. Just a random thought:

The documentation says that:

You can have WayFinder start anywhere you want in the tree by setting the &startId parameter to the ID of the document one level above where you want the listing to start.

And that’s why, am sure you know, setting a &startId =`0` shows everything in your tree menu, except for document 0 which we know there isn’t anyway.

Anyway, using this logic, your menu should work if you set the &startId to the document one level above document 63 in your case, or? Just wondering..

Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder

834 Posts

MarkG Reply #7, 18 years ago

Kogondo,

I think I need to go back and start again with Wayfinder.

At the moment I only have one chunk ’cos that’s all Wayfinder needed in the menu examples that came with it.

I’ve used the Ultimate Drop Down menu and it’s working fine see here: http://httpwix.s.customers.ilisys.com.au

I was just ecstatic that that even worked.

I’ve avoided delving deeper into wayfinder ’cos I never could get my head around the whole wayfinder chunks business anyway.

I never seemed to be able to get them to work, and it’s always hard to understand something when you can’t get it to work.

As for your suggestions:

You are right that I need to specify the &startItemTpl chunk, but as I’ve said there isn’t one at the moment.

Re setting the start level one level above, I don’t think that will work as the level above is the Home page and that will presumably show everything.

Content Creator and Copywriter

1,390 Posts

kongondo Reply #8, 18 years ago

Quote from: markg at Sep 25, 2008, 11:18 PM

I think I need to go back and start again with Wayfinder.

I think that’s a good idea. It will be valuable in the long run...

I’ve avoided delving deeper into wayfinder ’cos I never could get my head around the whole wayfinder chunks business anyway.
I never seemed to be able to get them to work, and it’s always hard to understand something when you can’t get it to work.

Been there, done that....At least two things helped me (apart from the help from the forums of course). First, I read and re-read the documentation. Secondly, I looked at the WF chunks studying what the placeholders were for. I took pen and paper and "replaced" the placeholders with the html elements they represent and it all made sense to me. As for the parameters, there’s lot’s that I still don’t understand fully what they are for. grin

Hope it works out for you....

Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder

834 Posts

MarkG Reply #9, 18 years ago

OK, just read the documentation again and remembered why I get so frustrated with it.

There’s just not enough explanation to help some of us figure it out.

I created a new chunk called &startItemTpl with <h2>[+wf.linktext+]</h2>[+wf.wrapper+]
inside the chunk.

And then placed it in my call as &displayStart=`1` &startItemTpl=`&startItemTpl`

Nothing.

Don’t know if it’s right, wrong there’s something missing or what, I just end up in a dead end.

Any pointers gratefully accepted.

Content Creator and Copywriter

MODX Staff
12,272 Posts

Ryan Thrash Reply #10, 18 years ago

&startItemTpl=`startItemTpl`

... lose the extra ampersand inside the parameter value. wink

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

How to Show "Not in Menu" items