that would be one way to do it. Pre-fuseactions would give you that
functionality.
If I was using a pre-fuseaction I wouldn't have it pass back the nav
or print it out. instead I would have it set a variable.. such as
nav_template_file and then in your main template where you would have
your s
Dustin Tinney wrote:
> First:
> about.abouthome you should have it be just
> about.home or better yet, about.index... the about should be implied
> by the circuit.
Yeah, I was going through all my circuits changing them probably at the
same time you were typing it ;)
> In my design model I woul
First:
about.abouthome you should have it be just
about.home or better yet, about.index... the about should be implied
by the circuit.
In my design model I would have a action on the about news and
anything else that would change up your navigation.. It would some
how set/return a navigation ob
The fusebox forum isn't that active and I've seen some fusebox posts
here so hopefully someone can give me a little advice...
I'm trying to figure out the best way to design my menu system
Fuseactions. I have a sidebar menu that changes for given main menu nav
items. So, let's say the top ma
4 matches
Mail list logo
