Sitemap, want children and parents to show but not parents as links...

Hello,
Seems like a simple issue and I can’t seem to get it after reading through the help files.

I have a simple Wayfinder sitemap being generated using [[Wayfinder? &startId=`0` &showDescription=`1`]] which basically just goes through and looks at whatever is "shown in menu" and lists it.

The problem is that I have the pages set up in a folder structure eg. Products >> Baseball / Basketball / Football and the products acts only as a container and aren’t content pages.

When I set the products folder page to published and "show in menu" it shows up in the sitemap like I want with the correct alias "products" however it is also clickable and goes to a blank page. If I disable either "show in menu" or "published" then all the children pages don’t show up in the Sitemap no matter what code I use in Wayfinder.

How in Wayfinder can I show "Products" in the sitemap but not have it clickable as a link?


Any Ideas?
Thanks

If the product items (Baseball, Football, etc) ARE NOT containers themselves (i.e. you only have a 2 level hierarchy - parents and children [products & product items]), one way to do this would be to create a chunk for the containers, i.e. products in your case. This chunk would be the &parentRowTpl. Then you would simply remove the <a> tags from the template as follows:



The children will use &rowTpl by default or innerRowTpl if you have this specified and will still be clickable. Hope this helps...

cheers/k

btw: what parameter is this &showDescription?

You could set the snippet call [!FirstChildRedirect!] into the content of the Products container. Products would remain clickable, but redirect immediately to the first child document (Baseball).

Quote from: ottogal at May 05, 2009, 06:20 AM

You could set the snippet call [!FirstChildRedirect!] into the content of the Products container. Products would remain clickable, but redirect immediately to the first child document (Baseball).

Wow I didn’t know about this at all, very neat. Thanks!

Quote from: kongondo at May 05, 2009, 03:51 AM

If the product items (Baseball, Football, etc) ARE NOT containers themselves (i.e. you only have a 2 level hierarchy - parents and children [products & product items]), one way to do this would be to create a chunk for the containers, i.e. products in your case. This chunk would be the &parentRowTpl. Then you would simply remove the <a> tags from the template as follows:

<li[+wf.classes+]>[+wf.linktext+][+wf.wrapper+]</li>

The children will use &rowTpl by default or innerRowTpl if you have this specified and will still be clickable. Hope this helps...

cheers/k

btw: what parameter is this &showDescription?

Thanks for the help. There is only 2 levels and the top level is the only container as you mentioned.

Bit confused by the chunk. What would be in the chunk that is inserted into the products page? So If I have a chunk, lets say {{parentChunk}} that is used for all the parent pages (which are the only containers) what is inside the chunk?

The &showDescription as far as I know uses the description instead of an alias

Thanks

@Visim,

Sorry, I should have been clearer. I was referring to a WF template chunk. So, create a chunk the normal way and give it a name, e.g. containers. Inside this chunk you would have the code......



Then you would tell WF that you want to use this chunk as the parentRowTpl like so



You can add other parameters to you WF call as you wish. WF will use the chunk "containers" for all parent level documents, in your case these would be the parent documents you refer to as "Products"

Which version of WF are you using, btw?

cheers/k

Quote from: kongondo at May 05, 2009, 11:42 AM

@Visim,

Sorry, I should have been clearer. I was referring to a WF template chunk. So, create a chunk the normal way and give it a name, e.g. containers. Inside this chunk you would have the code......

<li[+wf.classes+]>[+wf.linktext+][+wf.wrapper+]</li>

Then you would tell WF that you want to use this chunk as the parentRowTpl like so

[[Wayfinder? &startId=`0` &parentRowTpl=`containers`]]

You can add other parameters to you WF call as you wish. WF will use the chunk "containers" for all parent level documents, in your case these would be the parent documents you refer to as "Products"

Which version of WF are you using, btw?

cheers/k

Pure genius kongondo! Thank you very much.   I am using Wayfinder 2.0.

I sometimes struggle to wrap my head around certain concepts of using wayfinder and chunks even though I read through the documentation a number of times. Most of the examples are in regards to dropdown navs and not items such as sitemaps.

I also downloaded your guide the other day, I have so much to learn as I come from a designer and not developer standpoint.

Thanks again!

Glad I could be of help. Best wishes!

cheers/k