Dreamweaver - Nested Templates & Repeat regions

Author

Nested Templates & Repeat regions

Glitch808

2004-08-26, 12:22 pm

Xref: newsfeed-west.nntpserver.com macromedia.dreamweaver:958815

I have a page design that consists of 1 constant main navigation and various
secondary navigations based on what section of the site you are in.

First, I made a template with the basics that all pages will have including
the constant main navigation.
Then, I created my first nested template with the Secondary navigation for
section 1. Next, I made my first page based on this nested template. First
thing I notice is that all repeat regions and the editable regions within those
repeat regions are gone. Those regions are locked in place. How can this be,
this makes the nested template near useless? I can not adjust the breadcrumbs
for this section, nor can I customize he related links for the pages in this
section.

Am I doing something wrong in my implementation of the nested Templates?
I can see how many, many optional regions in the master template could provide
a solution, but this seems bulky. I would have to create the several secondary
navigations for each section in the Master template.

Murray *TMM*

2004-08-26, 12:22 pm

> First
> thing I notice is that all repeat regions and the editable regions within
> those
> repeat regions are gone.

That's how it should be. Think about it. A region that is defined in the
top-level template will NOT continue to be "a region" in a nested child page
(the 3rd generation). It's only remains a region in the top-level child
pages (the 2nd generation). To get around this problem, you can use the
passthrough feature. When you create a region you can elect to pass that
region through the next generation, effectively skipping a generation. So -
in the master template, you could designate those regions as passthrough
(you do this when they are created) and this prevents them from being edited
in the 2nd generation, but allows it in the 3rd generation.

This is one of the reasons why I encourage people to avoid nested templates
if at all possible - things can get mighty complicated.

How can you avoid it in this particular case? Here are some ways -

1. Create an editable region where your page-specific elements will be.
Use Library items to drop the desired element in those editable regions.
You get all the advantages of templates and none of the complexity.

2. Learn how to use Optional regions to control which navigation element
will be revealed on your child pages. I do this all the time and find it
very useful (you can see such a site here - http://www.ent-sys.com - where
the inner pages have section specific navigation).

Maybe that will help....

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Glitch808" <webforumsuser@macromedia.com> wrote in message
news:cgj6mp$3gn$1@forums.macromedia.com...
>I have a page design that consists of 1 constant main navigation and
>various
> secondary navigations based on what section of the site you are in.
>
> First, I made a template with the basics that all pages will have
> including
> the constant main navigation.
> Then, I created my first nested template with the Secondary navigation for
> section 1. Next, I made my first page based on this nested template.
> First
> thing I notice is that all repeat regions and the editable regions within
> those
> repeat regions are gone. Those regions are locked in place. How can this
> be,
> this makes the nested template near useless? I can not adjust the
> breadcrumbs
> for this section, nor can I customize he related links for the pages in
> this
> section.
>
> Am I doing something wrong in my implementation of the nested Templates?
> I can see how many, many optional regions in the master template could
> provide
> a solution, but this seems bulky. I would have to create the several
> secondary
> navigations for each section in the Master template.
>
>