How to remove Editable region from nested template?

Question

I'm trying to remove an editable region from a nested
template while retaining it in the parent template. DW doesn't want
to let me do this.
Example:
- I've created an overall template call ALLPAGES.DWT
- In it, there's an editable region called "related links".
- The "related links" will stay the same for all my main
pages (welcome, news, info, etc), so I'd like to create a nested
template called MAINPAGES.DWT where the field is locked.
So here's what I did; I started a new page from ALLPAGES.DWT
and then I created a template MAINPAGES.DWT from it. Now I want to
remove the editable region "related links". According to the DW
manual, I should be able to highlight the region and go to
Modify > Templates > Remove Template Markup, but that
option is greyed out!
Apparenlty the only way of removing the editable region is to
create a smaller editable region within it. But that's unnecessary
and sloppy. How can I remove the region entirely?

Answer 1

> This use of nested templates is very useful and very
simple and
> straightforward.
> It involves no additional overheads, and introduces no
reliability
> problems.
I really disagree with this.
> I cannot understand why Murray has such a bad attitude
to nested
> templates.
I spent quite a bit of time using them, tweaking them,
understanding them,
and watching the problems that others have had here on the
forum. My
compelling conclusion is that there is nothing you can do
with nested
templates that you cannot do more simply and with far less
trouble by using
other methods, some involving other kinds of template
regions, and some
involving simple use of Library items, or better, server-side
includes.
> I can only assume either that he had a bad experience on
the road to
> Damascus,
> after writing his definitive book on templates
I assure you, it's based on much more study and experience
than you have put
into it.
> "Templates are wicked and sinful! Don't play with them,
or you will go
> blind!"
This is not only unkind, it's completely erroneous. Far and
away, I am the
single most enthusiastic proponent for the use of templates
on these boards.
Perhaps a read of my book would help you rid yourself of your
attitude, too.
Murray --- ICQ 71997575
Adobe Community Expert
(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
==================
"Clancy" <[email protected]> wrote in message
news:[email protected]...
> "Dodgeit" <[email protected]> wrote:
>
>>I'm trying to remove an editable region from a nested
template while
>>retaining
>>it in the parent template. DW doesn't want to let me
do this.
>>
>> Example:
>> - I've created an overall template call ALLPAGES.DWT
>> - In it, there's an editable region called "related
links".
>> - The "related links" will stay the same for all my
main pages (welcome,
>> news,
>>info, etc), so I'd like to create a nested template
called MAINPAGES.DWT
>>where
>>the field is locked.
>
> Very simple:
>
> Open allpages.dwt.
> Save as template, with name mainpages.dwt (I always do
this immediately so
> that
> if I do something stupid I don't corrupt the original
template).
> Insert the desired content into "related links".
> At the beginning of the content area of "related links"
insert the magic
> code
> @@("")@@
> This turns off the editable region, and there will be no
reference to it
> in
> pages derived from this template.
> Save the changes to mainpages.dwt
> Done!
>
> Have a look at
>
>
http://www.corybas.com/Technical/Nested.htm
> This is derived from my template techpage.dwt, which in
turn is ultimately
> derived from my template basicpage.dwt.
>
> Basicpage.dwt defines two editable regions 'title' and
'subtitle' at the
> top of
> the page. Techpage.dwt sets a fixed title for all my
technical pages, as
> follows:
>
> <p class="hdgtn" ><!-- InstanceBeginEditable
name="Title" -->@@("")@@Roger
> Riordan: Technical notes<!-- InstanceEndEditable
--></p>
> <p class="hdgstn"><!-- InstanceBeginEditable
name="Subtitle" -->Notes<!--
> InstanceEndEditable --></p>
>
> In the page Nested.htm the references to 'title'
disappear, and the two
> lines
> appear as
>
> <p class="hdgtn" >Roger Riordan: Technical
notes</p>
> <p class="hdgstn"><!-- InstanceBeginEditable
name="Subtitle" -->Nested
> Templates<!-- InstanceEndEditable --></p>
>
> This use of nested templates is very useful and very
simple and
> straightforward.
> It involves no additional overheads, and introduces no
reliability
> problems.
>
> I cannot understand why Murray has such a bad attitude
to nested
> templates. I
> can only assume either that he had a bad experience on
the road to
> Damascus,
> after writing his definitive book on templates, or that
it says simply:
>
> "Templates are wicked and sinful! Don't play with them,
or you will go
> blind!"
>
>
> Clancy