How about trying our product, Nested Templates and Menus?
http://www.decloak.com/Products/Dreamweaver/NestedTemplates/
Free 30-day evaluation version
Considering the complexity of your site, this product is just for you. The
demos show 3 levels of nesting and and also with 4 levels.....I can most
probably go as deep as you want in the nesting levels.
dc
decloak.com
p.s. This product is now able to handle foreign languages
......see the TONGUES of FIRE demo web site at
http://www.decloak.com/Products/Dreamweaver/NestedTemplates/Demos/NestedT_Tongues_of_Fire/
"GGirlando" <webforumsuser (AT) macromedia (DOT) com> wrote
Quote:
I'm building a site right now for a small university using templates, and
relying heavily on the Halstead & Summers book about Templates.
While I am having success using parameters with a single template and
child pages, I keep hitting road blocks when I try to integrate these things
|
into a nested template system. I'm about ready to give up and just have 12
different templates for each of the sections of our site, yet I would so
much prefer to get the nested system working--I am certain it would be of
much benefit down the road to be able to update all twelve templates at
once.
Quote:
Basically, the navigation is the same on all pages, with the exception
that on each of our six primary navigation sections of the site (e.g.
|
"Academics", "Student Services", etc.) there is a different pull-down text
navigation menu that opens in the down-state for each section.
Quote:
Thus, I need to implement a multipleIf statement which displays the proper
sub-nav menu for each section. In this, I was successful, and appreciated
|
the feedback I received from Murray on this forum. However, I'm having
problems getting this to work in a nested structure.
Quote:
Second problem is that each of the six primary navigation sections has a
rollover image, while the pull-down subnav menus are in text. Thus, I have
|
to integrate parameters for both images and text--and all within nested
templates.
Quote:
The third problem is that templates 7 thru 12 (one for each of the
programs our university offers) are all sub-nested underneath the primary
|
nav section titled "Academics". After having problems with just one layer
of nesting, I am leery of having to add another set of nested templates
below the first level.
Quote:
I've been searching forum archives trying to find comments which pertain
to these issues. I have seen some suggestions that seem like they might
|
apply---such as to make each of the subnav menus a Library Item. However,
when i tried that one, it wouldn't let me add conditional parameters to the
first nested template level, especially when all six of the first level
nested templates are based on conditional parameters from the Master parent
template. (Is it even possible to have conditional parameters in a child
template that is based in conditional parameters from it's parent template?)
Quote:
Yet, on the other hand, when I take a different approach and try to have a
simple editable region called "navigation" on the master parent template,
|
and then add in the conditional parameters to generate the child pages from
each child template, it won't let me do that either--I get the following
error message:
Quote:
"You have made changes to code that is not marked as editable." Yet, it
is right smack dab in the center of an editable region! Plus, when I try
|
to save the changes anyways, I get another error message: "Access to
undefined template parameter "page_id"." Yet, up in the head that very
parameter exists, as follows:
Quote:
!-- InstanceParam name="page_id" type="text" value="home" --
What gives?
This is getting very frustrating! :-)
Has anyone attempted a project like this who can give me some feedback?
Basically, the challenge is to integrate three layers of templates (Master,
|
Primary Nav, Secondary Nav) with different pulldown text menus under each of
the templates which involve both text and graphic elements.
Quote:
Big request I know--just having an example of something like this would be
very helpful though!
Thank you. |