-
☆ A M B ☆
- 318 Posts
Did the way the hideSubMenus parameter work change in the Revo version? It used to be that when you set hideSubMenus to TRUE, Wayfinder would always display the immediate children of the startid, but it would not display the grandchildren unless you were in that particular part of the structure.
In Revo, it appears that if I set hideSubMenus to TRUE, it hides the children unless you’re actually at startid or one of its decendants. Does that make sense? Not sure I’m explaining clearly - in Evo, it would always display the children, whereas in Revo the children are hidden.
Is this a deliberate change, and if so, how can I change it back?
Edit: NVM, I fiddled around with it and decided I actually like the way the parameter works in Revo better.
-
☆ A M B ☆
- 24,524 Posts
Wayfinder works the same in either version. It’s a matter of using the tpls to structure the menu, then CSS or javascript to style/animate the structure. The only difference is to use [[+placeholder]] for Revo instead of [+placeholder+] for Evo.
The reason why I mentioned it is because of the difference between the two pages.
Do you know of a simple to follow (step by step) tutorial that I can look at?
For I am a little confused about the muddy dog paws web site tutorials. I need some more direction in how and where to use the code. Thanks Susan. Have a great day!
-
☆ A M B ☆
- 24,524 Posts
Maybe I should just add a post to my Dark Side posts about how, exactly, my menu for Pet Shop was made (although it’s no different at all from the original Evo version). I suppose I should start a series of articles on my site - except I still really don’t know what I’m doing yet
Which "code" are you talking about? With a bit of css trickery you can design almost any menu to work just using the default nested unordered lists. In fact, I’m biased in that direction because this was one of my very favorite reference articles before MODx appeared on the scene
http://www.alistapart.com/articles/taminglists/.
-
☆ A M B ☆
- 24,524 Posts
You need five chunks, named cssplay_parentRow, cssplay_outer, etc, as described. Then the Wayfinder snippet as shown at the top of that page will use those tpls to generate the various parts of the menu structure, which get styled using the css files specified in the "cssplay_dropdown" chunk. Those css files are found in the original MODx installation, in assets/snippets/wayfinder/examples/cssplay for Evo and in core/components/wayfinder/examples/cssplay in Revo, so that chunk could actually just link to them where they are. Or you can put them wherever you like, as long as those <link...> tags in the cssplay_dropdown chunk have the correct paths. Or skip the cssplay_dropdown chunk and put the link tags directly in your main site template’s head.
Of course, being MODx, Wayfinder can also use other methods of defining these tpls besides chunks. Check the files in the core/components/wayfinder/configs folder, especially the cssplay-basicdropdown.config.php file. So your Wayfinder call would just have &config=`cssplay-basicdropdown`, and all the rest of the stuff would be in that config file as ordinary PHP variable definitions. Or at least it works that way in Evo, I haven’t used a Wayfinder config file in Revo yet.
We have the easy calls from the template to chunks, titles, etc that just require one word or so. Easy to understand and it takes little space in the template.
What if the Wayfinder call would call to it’s own Wayfinder template where the various information is gathered. One place to adjust and not many small files. I noticed that there seems to be five from what I saw.
My mind is taking a walk when it comes to getting the Wayfinder to work correctly.
I look forward to an easier to use Wayfinder.
-
☆ A M B ☆
- 24,524 Posts
You can always use a config file, with the tpls declared as variables in the one file (there are sample config files with the installation although I’m not sure where those are put in Revo).
