Quote from: Paal_Joachim at Sep 06, 2010, 01:06 PM
What is the easy way to get into Wayfinder? Since that is next on my list since I plan to create the links through Wayfinder.
Create additional pages which I’ll do from the template and then use Wayfinder to create my navigational structure.
The way i did it was to set the pages that i did not want to appear in the wayfinder-menu to ’Hide form menu’ in the individual page settings.
For sections i created folders that contained the subpages for the section.
My travel related site has a structure like this:
(page) Startpage
(page) errorpage (hidden form menu)
(folder) destinations
(page) county1
(folder)country2
(page in folder country2) place1
(page in folder country2) place2
(page in folder country2) place3
(page) county3
(folder) country4
(page in folder country4) place1
(page in folder country4) place2
(page in folder country4) place3
I do it like this since i have just one page for some countries and several places for other countries.
Im calling wayfinder in a chunk with the folowing piece:
[[Wayfinder? &startId=`10` &level=`0` &titleOfLinks=`longtitle` &parentRowTpl=`cssplay_revParentRow` &cssTpl=`cssplay_ultdrop`]]
Where startid equals the id for the folder for destinations (which is what i want to appear in my menu), level is set to 0 for full depth of pages and folders within a destination. I’ve chosen to use longtitle to be used for displaying as linktitles since i want to make more clickpromoting titles rather than the same as the menu title.
I’ve used the
MuddyDogPaws example for css’ing the menu. But it does not support dynamic width of the menu items, which i would like to have as some destinations like Samoa and Fiji is just a few chars, but French Polynesia and Coock Islands requires a wider menu item. But it looks like this is a CSS-nut to be cracked rather than MODX specific.
I would also like to be able to use multiple templates with one mother-template for the overall look and feel, and a sub-template for the destinations that inherits the mother template, but it seems that a template can not be "connected" to a template the way a page can by specifying ’Uses Template:’. I beg a pardon if this is hijacking the topic, but I think this may be relevant and I asked about this in a thread in the templates section and it did not get answered.
Bjorn