Remove editable region

I am trying to remove an editable region on a template but
get a dialog box with inconsistent regions problems. I am afraid I
will mess things up if I don't know what to select from the menu.
Anyone know what to do here/?

Removing an editable region from a TEMPLATE page would not
general such.
Are you sure you have properly described what you are doing?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"sugar_d" <[email protected]> wrote in
message
news:gh9f0j$cps$[email protected]..
>I am trying to remove an editable region on a template
but get a dialog box
> with inconsistent regions problems. I am afraid I will
mess things up if I
> don't know what to select from the menu. Anyone know
what to do here/?
>
>
>

Similar Messages

How to remove Editable region from nested template?

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?

> 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" >@@("")@@Roger
> Riordan: Technical notes</p>
> <p class="hdgstn">Notes</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">Nested
> Templates</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

DW CS3 Remove editable regions

Hi
How does one go about removing an editable region in DW CS3?

Thanks David...it was rather a simple issue but for whatever reason my mind wasn't working and this had me stumped.
I have another template based question on the forum, once I get past this last issue, I think my troubles will be behind me. If you have time, please have a look.
Cheers!
Bob

Remove editable region *and* propagate?

Hi all,
I have an editable region in a template which I would like to
make uneditable. I can remove it in the template, but the change
does not seem to propagate to the child pages. In other words, the
region is still editable on the child pages after I apply the
changed template. Is there a way to do this or am I outta luck
here?
Thanks!

Removing the editable region markup should certainly render
that region
uneditable in the child pages. Something is preventing that
from happening.
Can you show me the child page after removing the markup and
tell me which
region you are deleting?
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
==================
"idRatherBeOutside" <[email protected]>
wrote in message
news:e4e3s6$j23$[email protected]..
> Hi all,
>
> I have an editable region in a template which I would
like to make
> uneditable.
> I can remove it in the template, but the change does not
seem to propagate
> to
> the child pages. In other words, the region is still
editable on the
> child
> pages after I apply the changed template. Is there a way
to do this or am
> I
> outta luck here?
>
> Thanks!
>

I can't remove Editable Region

I have multiple templates and I cannot remove and editable region...it won't allow me to do so through Modify>Templates>Remove Markup...it will not make that option available to me...Help
Learning

You need to make the change in the main template, not in a child page.

How to delete editable regions and template?

Hi everybody,
I posted this question earlier in the web discussions area, being unaware of a forum specific to Dreamweaver. Sorry for posting in two different places.
For the past week, I have been learning Dreamweaver CS4 from an online tutorial. I got to the place where I generated a template (index.dwt) from the main page (index.html) and created some editable regions on it. At that point, I realized that I had done all the steps by rote and did not actually absorb what I was doing. I wanted to delete the template in order to repeat the steps and gain a better understanding of the process. When I tried to delete the editable regions (modify-templates-remove editable regions), I was unable to do so because "remove editable regions" was greyed out. Nor was I able to delete the html code. I tried to delete the template itself, but when I did that, the index.html page retained those editable regions! Can anyone tell me if there is a way to get back to the place I was in before creating the template?
Thank you for any assistance.

All you need to do is detach the index.html file from the template. Then you can delete the template and start all over.
Go to the Modify menu --> Templates --> Detach from Template

How do I remove an extra editable region in the head of a specific page?

I have a single-template website. My template has the standard two editable regions in the head ("title" and "head"). Somehow, one of my pages ended up with three editable regions in the head - two named "head" as well as title. My template won't update this page because the editable regions don't match. How do I remove this extra editable region from the head of the page? I can't modify it on the page itself, of course, and I can't remove it by modifying the template because it's not part of the template.
Thanks in advance!

Your child page would not contain any editable regions if it wasn't attached to a Template. Perhaps you nested templates which is the wrong thing to do.
Go to Modify > Templates > Detach from Template.
Nancy O.

I have an Editable Region in a template and want to remove it

When I have an Editable Region in a template and want to
remove it, and from all child-pages, what to do[mx 2004] ? The
below code if is in logout.php how is get included in a file ?
I use:

but isset($_SESSION["email"] does not working .... well ?
[code]<?php
if (isset($_SESSION["email"])) {
?>
<link href="/css-styles.css" rel="stylesheet"
type="text/css"><body class="text_normal">
<span class="text_normal">LOGGED IN(<a
class="text_normal"
href="/php_files/logout.php">Customer-LogOut</a>)</span>
<?php
?><br />
<?php
if (isset($_SESSION["email-affiliates"])) {
?>
LOGGED IN(<a class="text_normal"
href="/php_files/affout.php">Affiliate-LogOut</a>)
<?php
?>
[/code]

Click in the editable region in the Template file. Right
click on the
mmeditable tag you see on the tag selection and choose Remove
Tag from the
menu. Save the Template.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"123polis123" <[email protected]> wrote in
message
news:gf7pu8$p69$[email protected]..
> When I have an Editable Region in a template and want to
remove it, and
> from
> all child-pages, what to do[mx 2004] ? The below code if
is in logout.php
> how
> is get included in a file ?
>
> I use:
> 
> but isset($_SESSION["email"] does not working .... well
>
> [code]<?php
> if (isset($_SESSION["email"])) {
> ?>
> <link href="/css-styles.css" rel="stylesheet"
type="text/css"><body
> class="text_normal">
> <span class="text_normal">LOGGED IN(<a
class="text_normal"
>
href="/php_files/logout.php">Customer-LogOut</a>)</span>
> <?php
> }
> ?><br />
> <?php
> if (isset($_SESSION["email-affiliates"])) {
> ?>
> LOGGED IN(<a class="text_normal"
>
href="/php_files/affout.php">Affiliate-LogOut</a>)
> <?php
> }
> ?>
> [/code]
>
>
>

Modifying a template resulted in all child pages with repeating editable regions - Help !

Good morning,
I have recently been appointed to update a website designed in Dreamweaver by an employee who is no longer here. I have read books on the software and practiced an insane amount which permitted me to update child pages, links, documents etc... however:
I was asked to add a new button to an "non-editable" region of a template. Trying to do so resulted in a massive mess (with massive anxiety).
Even thou the new template had all the same text and editable regions, all my pages look completely different from the template itself. The editable regions appears 2-3 times in different locations ex: Header is showed on the bottom, top etc... and the Editable region titles (EditableRegion1 etc...) repeat themselves as well.
I really need help and not sure what to do, I have tried everything and I am only making it worse and worse. All I want/need is for all my html pages created with this template, match the template.
Please note that this site is local, not online.
Since I noticed on other threads that the code is needed; here it is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>QMS: AFM</title>
<style type="text/css">

</style>
<link href="file:///U|/AFM/Dreamweaver/Left sidebar.css" rel="stylesheet" type="text/css" />
</head>
<body link="#006699" class="twoColElsLtHdr">
<div id="container">
<div id="header">
    <h1><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/pwgsc-e.gif" width="364" height="33" align="left" alt="wordmark" /><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/wordmark_canada.gif" width="83" height="21" align="right" alt="wordmark2" /></h1>
    <p> </p>
    <p><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/AFM QMS banner.jpg" width="709" height="80" alt="banner" border="0"/><a href="mailto:[email protected]"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Contactus-e.JPG" width="110" height="21" alt="contactus-e" border="0" /></a><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/French-e.JPG" width="115" height="21" alt="french-e" border="0" /> <a href="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Continual Improvement/QMSTeamMembers-e.html"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Help-e.JPG" width="115" height="21" alt="help-e" border="0" /> <img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Search-e.JPG" width="115" height="21" alt="search-e" border="0" /></a><a href="http://source.tpsgc-pwgsc.gc.ca"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/thesource.jpg" width="120" height="21" alt="TheSource" border="0" /> <img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Home-e.jpg" width="104" height="21" alt="home-e" border="0" /></a></p>
    <p> </p>
</div>
<div class="twoColElsLtHdr" id="sidebar1">
    <p><a href="../QMS HOME/QMSHome-e.html"><strong>QMS Home</strong></a></p>
    <hr />
    <p><a href="../ABOUTAFM/AboutAFM-e.html"><strong>About AFM</strong></a></p>
<hr />
<p><a href="../AdminProcedures/AdminProcedure-e.html"><strong>Administrative Procedures</strong></a></p>
<hr />
<p><a href="../BusinessUnits/BusinessUnits-e.html"><strong>Business Units</strong></a></p>
<hr />
<p><a href="../POINTSOFINTEREST/pointsofinterest-e.html"><strong>Points Of Interest</strong></a></p>
<hr />
<p><a href="../Achievements/Achievements-e.html"><strong>Achievements</strong></a></p>
<hr />
<p><strong><a href="../MeasuringPerformance/measuringperformance-e.html">Measuring Performance</a></strong></p>
<hr />
<p><a href="../References/references-e.html"><strong>References</strong></a></p>
<hr />
<p><a href="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/ContinualImprovement-e.html"><strong>Continual Improvement</strong> </a></p>
</div>
<div id="mainContent">
    <h2>Header</h2>
    <p>Paragraph</p>
    <h1>Sub Header </h1>
    <p> </p>
    <h1> </h1>
    <h2> </h2>
    <h1> </h1>
    <p> </p>
    <h2> </h2>
    
</div>

       <br class="clearfloat" />
</p>
<div id="footer">
    <hr width="100%" size="8" noshade="noshade" color="#006666" id="color="069"" colour="#069"/>
    <p><strong>Maintainted by: ASQM </strong></p>
    <p><strong>Date Modified: 2013-03-25</strong></p>
    
</div>
<script type="text/javascript">

</script>
</h3>
    
</h3>
</div>
<script type="text/javascript">

</script>
</body>
</html>

I am not suprised, the previous employee tried to recreate the English version of the site in another folder structure and did not change all links and was still using a template in the wrong location.
I think I created the mess by trying to modify the existing template's non-editable region in order to add a new button. When trying to update all the pages, the fiasco started.
Do you think the best option would be to create a new template in the correct folder structure and apply it? Would it fix the current pages or will I have to fix them all manualy on by one?
I understand it is difficult to deal with a newbie of my magnitude and thanks again.

Can't Delete Non-Editable Region in Template?

Well, I can in existing templates but if I create a new one from an existing page using "Save as Template", when I try to delete a non-editable region in the template, DW won't let me. I don't know why. Aaaargh!
It's my understanding I should be able to edit anything in a template. I've tried existing DW and restarting. I've tried using other pages as a basis for the template. Every template I create won't let me delete non-editable regions. I'm highlighting the non-editable region and pressing the delete key. I can't delete.

burro_mail wrote:
Not sure DW is doing what you describe...
But I am certain you could remove the region in code view.
Even if you are a WYSIWYG-er and not a big code-head, it should be pretty easy to remove the region markers and everything between them...
Trust me, it is. I'm wondering if the problem is associated with the fact that the source page that I saved as a template was based on a template? I just noticed that this new template refers to another template. I'm thinking that means the other template is controlling what I'm trying to do in the current template.
That's it. I just tried saving a template under a different name (still retaining the correct template file extension) but did not do the save as template. Now I can completely edit that template. So you if you save a page that is controled by a template, as a template, that new template is controlled by the previous template.
I've got a headache now.

Can't edit 2nd editable region

Hi,
I have a template which uses CSS and DIVs. It has 2 editable
regions, each within a DIV.
When I open a document based on this template, for some
reason only the first editable region is editable. The only way I
can edit the second is to turn of styles or go into code view.
Any ideas why?

> That's just being picky.
> It makes no difference whether it is absolute or
relative - it doesn't
> work
> either way!
Well, for it to be a layer, it has to be absolutely
positioned, and the
difference in behavior between the two (absolute vs.
relative) is certainly
NOT picky.
Remove the overflow:auto style on the div#main container, and
you'll be able
to edit it in Design view.
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
==================
"mrdebauchery" <[email protected]> wrote in
message
news:[email protected]...
> That's just being picky.
> It makes no difference whether it is absolute or
relative - it doesn't
> work
> either way!
>
> Code attached, with crap cut out.
>
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
> "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="
http://www.w3.org/1999/xhtml"
lang="en-gb">
> <head>
> <meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
> 
> <title>Title</title>
> 
> <style>
> body,td,th {
> font-family: Times New Roman, Times, serif;
> font-size: 16px;
> color: #000000;
> line-height: 105%;
> }
> body {
> background-color: #FFFFFF;
> margin-left: 0px;
> margin-top: 0px;
> margin-right: 0px;
> margin-bottom: 0px;
> }
> a:link {
> color: #0066CC;
> }
> a:visited {
> color: #0066CC;
> }
> a:hover {
> color: #006699;
> }
> a:active {
> color: #006699;
> }
> h1, h2, h3, h4, p {
> padding: 0px 0px 20px 0px;
> margin: 0px;
> }
> h1 {
> font-size: 24px;
> color: #4376BD;
> }
> h2 {
> font-size: 20px;
> color: #4376BD;
> }
> h3 {
> font-size: 16px;
> color: #4376BD;
> }
> h4 {
> font-size: 14px;
> }
>
> #container {
> width:760px;
> margin: auto;
> overflow:visible;
> }
>
> #topbar {
> position:relative;
> width:760px;
> height:104px;
> background-image: url(images/topbar.jpg);
> background-repeat: no-repeat;
> overflow: hidden;
> }
> #title {
> float: left;
> width: 325px;
> z-index: 2;
> }
> #pics {
> float: right;
> z-index: 2;
> }
> #pics img {
> margin: 4px 10px 4px 0px;
> border: #ffffff 1px solid;
> }
> #middle {
> position:relative;
> width:754px;
> overflow: auto;
> border-right: #006699 3px solid;
> border-left: #006699 3px solid;
> min-height:489px;
> background:url(images/lines.gif) repeat-y;
> }
>
> #menu {
> position:relative;
> width:194px;
> min-height:465px;
> float: left;
> border-right: #006699 3px solid;
> padding: 15px 0px 0px 0px;
> text-align: center;
> overflow: auto;
> }
>
> #links {
> width: 134px;
> height: 320px;
> border: #0276C0 1px solid;
> background-color: #DCF4F8;
> margin: 30px auto 15px auto;
> text-align: center;
> color: #0276C0;
> font-size: 18px;
> padding: 0px 6px 0px 6px;
> }
>
> #links ul {
> list-style: none;
> margin: 0px;
> padding: 0px;
> }
>
> #links ul li {
> padding: 29px 0px;
> margin: 0px;
> }
>
> #links ul li a {
> text-decoration: none;
> }
>
> #main {
> position:relative;
> width:512px;
> min-height:450px;
> float: left;
> overflow: auto;
> padding: 25px 15px 15px 30px;
> text-align: left;
> line-height: 105%;
> }
>
> #botbar {
> position:relative;
> width:760px;
> height:14px;
> background-image: url(images/botbar.jpg);
> background-repeat: no-repeat;
> overflow: hidden;
> }
> .small {
> font-size: 10px;
> padding: 0px 0px 5px 0px;
> line-height: 12px;
> }
>
> </style>
> </head>
> <body>
> <div id="container">
> <div id="topbar">
> <div id="title"><img
> width="325"
> height="104" /></div>
> <div id="pics"><img width="66"
> height="89" /><img width="66" height="89"
/><img width="66" height="89"
> /><img
> width="66" height="89" /></div>
> </div>
> <div id="middle">
> <div id="menu"> <img width="190" height="85"
/>
> <div id="links">
> <ul>
> <li> </li>
> <li> </li>
> <li> </li>
> <li> </li>
> </ul>
> </div>
> <p class="small"> </p>
> </div>
> <div id="main"> 
> <h1>Heading 1</h1>
> <p>Paragraph</p>
> <h2>Heading 2</h2>
> <p>Paragraph</p>
> <h3>Heading 3</h3>
> <p>Paragraph</p>
> <p>Paragraph</p>
>  </div>
> </div>
> <div id="botbar"> </div>
> <p> </p>
> </div>
> </body>
> </html>
>

Spry tool tip does not work in template or child pages within an editable region. Why not?

Ok. so I am getting pretty frustrated. I take the time to learn how to use CSS and to create a template page for a Contractor Site (www.ContractorInsurance.net). The idea is to create a page that I can use for different classes of Contractors...right?
Then I get all happy about being able to insert ToolTip onto pages to help the user. Great!
LIfe to turn to Sorrow after nearly five hours of searching for a "eeking" answer.
So what good does it do to have an Editable region to update if we cannot have the flexibility to insert a tool tip on child pages? Ok so the fast solution is to what... Have a question mark image, insert another apDiv, name it toolTip_Not and provide it with a show=hide behavior?
RRRRRrrr...
This really sucks not being able to find a solution within a reasonable amount of time.

I have tried thank you. However...it is still not working.
www.ContractorInsurance.net/course_of_construction.php
The error message is "Making this change would require code that is locked by a template translator"
Re: Spry tool tip does not work in template or child pages within an editable region. Why not?
created by altruistic gramps in Spry Framework for Ajax - View the full discussion
If you have a look at the following simple document with a tooltipTooltip trigger goes here.
Tooltip content goes here.
you will notice that a couple of lines have been placed in the HEAD section of the document. When using DW templates, the HEAD section is usually not editable, hence the error mesaage. By default, your template should have an editable region in it just before the closing tag. It looks like this:  Dreamweaver should be able to find that editable region and insert the
<script> tag there automatically. Because you don't have an editable region like that in the <head>, open the master template, and paste the code above just before the closing </head>
tag. Gramps
Edited to remove personal data

Nesting Templates: Child-Template Pages not Fully Responding to Editable vs. Un-Editable Regions

M'kay, so first and foremost, all of this is being done within Dreamweaver CS5. How I might explain this is that I have a series of Master-Templates for my website, accompanied then by Child-Templates linked off of / nested from my Master-Templates. So far this is going wonderfully, that is, until I try to make a page from one of my Child-Templates.
The page from my Child-Template accurately comments-out an un-editable region (Region in which was editable within the Master-Template, but left as ONLY editable within the Child-Template) so long as I add an EDITABLE region WITHIN it. Under the circumstance that I DO NOT add an editable region within the Master-Template's editable region, the region within the Page is still appearing editable.
For example:
Master Template:

     Child Template CSS Links Here.

Child Template:

     Child Template CSS Links Here.
     
          Child PAGE CSS Links Here.
     

Child Page:
Child Template CSS Links Here. (Accurately appearing Un-Editable - {Master-Template's editable region tags accurately appearing invisible})

     Child PAGE CSS Links Here. (Accurately appearing Editable)

This is an example of an editable regions that WORKS. In the Child-Page the "Child Template CSS Links Here." IS appearing commented out and therefore un-editable within the Child-Page, like it's supposed to be. This then allows the "Child PAGE CSS Links Here" to be ACCURATELY editable within the Child-Page.
Now for an example of what DOESN'T work:
Master Template:

     Child Template CSS Links Here.

Child Template:

     Child Template CSS Links Here.
     (As you see, I have NOT added an additional editable region within this Master-Template's editable region. This is an area that is ONLY supposed to be editable within the Child-Template and NOT the Child-Page, which SO FAR appears to be accurate.)

Child Page:

     Child Template CSS Links Here.
     (For some reason, ONLY so long as I DO NOT add an additional Child-Template-editable-region within this Master-Template's editable region, this area is STILL appearing visible as well as editable within the Child-Page.)

So, under this circumstance, it seems that the only way I can leave a Master-Template's editable region ONLY editable within the Child-Template and NOT editable within the Child-Page is by leaving an ADDITIONAL editable region produced via the Child-Template somewhere within EVERY SINGLE editable region produced via the Master-Template. Unless I am doing something seriously wrong, this so far appears to be a potential defect/bug within Dreamweaver CS5. I can't imagine how this would be accurate, otherwise Child/Nested-Templates would not be possible to make. What might I be doing wrong? Is there any way that I can specify in the Master-Template that an Editable Region is ONLY Editable within the Child-Template and NOT within further Child-Pages (A Page based off of the Child-Template)? Or perhaps is there a way that I can specify in the Child-Template that an editable region WILL NOT be editable within the Child-Page? Furthermore, no, I DO NOT want to make them "Optional Regions," so please do not suggest that.
I know that this is all probably a bit confusing, but hopefully the examples above will help more than the descriptions aside. As you can probably assume, this is definitely a HUGE complication within my website if there doesn't end up being a solution, especially with all the time I have put into making the Child-Templates that I hope to rely on. It really would be a bit ridiculous if I had to script-in an additional editable region within every single Master-Template-editable-region available within my Child-Template just so that I may update my Child-Template, furthermore allowing my edits to drop down to my Child-Pages, especially since it would maintain content that I never wanted to be editable within the Child-Page in the FIRST place.
Some help would be sincerely appreciated, and as soon as possible, if I might ask politely.
Thank you. Sincerely,
~ Miss Cat

=____= I cannot believe that I am saying this, after writing ALL of that up, but thanks to "Dreamweaver CS5 for Dummies," I just learned that if you place: @@(" ")@@ within the Child/Nested Template's editable region that you DO NOT want passed down to your Child-Pages, it won't appear editable. Goodness knows why such an inconspicuous formula was the answer, but I guess whatever works. ...WHY WAS THIS INFORMATION SO DIFFICULT TO FIND?!?!?!?! @____@ Information on Nested Templates in general seems rather difficult to find, however, so I'm glad I figured this out /not ever a full hour/ after writing all this up and posting it. #__# ...At least my Child-Templates can work thoroughly now, though. So... Scenario FIXED. ^^
I only hope now that such information will appear helpful to anyone else hunting for this information via Google or other Search Engine in the future. And if there is anything at all that I am still officially missing, then do feel free to add it to the feed and let me know, because the last thing I need right now are more surprise difficulties to equally slow down the productivity of this massive project I've been working on... @___@ ..But so far things seem to be going good. ^^ So I can settle myself unbelievably grateful that there ended up being a solution to this ridiculousness after all.
Sincerely,
Miss Cat
[signature promo info removed by moderator]

Editable regions and UL tags

I notice that D8 design view can corrupt the view of a page
element if an editable region is included. I.e.
<div class="leftsideCol">
<ul>
<li class="title">In-Page links</li>
<li><a href="#">Navigation
Title</a></li>
<li><a href="#">Navigation
Title</a></li>
<li><a href="#">Navigation
Title</a></li>
<li><a href="#">Navigation
Title</a></li>
<li><a href="#">Navigation
Title</a></li>
<li><a href="#">Navigation
Title</a></li>
<li><a href="#">Navigation
Title</a></li>
</ul>


<p class="sidebarTitle">?! Notices !?</p>

<div class="sideMssgeBoxCntnr">
<p class="sideMessageTitleBkgrndYel">Subject
Title</p>
<p class="sideMessageBoxText">Put your message here. Be
succinct to avoid overcrowding the sidebar. Here is a <a
href="#">link</a> which can be removed by normal text
delete.</p>
</div>
</div>
The first region statements corrupt the view (remove them and
all displays correctly). This does not affect the final page.
If I try to solve this by putting the region just inside the
UL and /UL tags the design view is good. BUT the resulting page has
an extra UL opening tag. Why is this, it upsets the styling?
Where can I find a definitive set of rules for putting
regions around tags other than <p> which seems to work OK? I
want to make a set of LIs editable and be able to add another LI to
the list.

>I notice that D8 design view can corrupt the view of a
page element if an
> editable region is included.
There must be something else going on. Your posted code would
be quite
normal. Why not upload this page and post a link to it so I
can see the
whole picture, please.
> Where can I find a definitive set of rules for putting
regions around
> tags
> other than <p> which seems to work OK? I want to
make a set of LIs
> editable and
> be able to add another LI to the list.
The regions must be properly nested. That's about it. In
other words, you
could not have this -
<div>
</div>

> I want to make a set of LIs editable and
> be able to add another LI to the list.
Exactly what you have would do that.
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
==================
"ROGM" <[email protected]> wrote in message
news:[email protected]...
>I notice that D8 design view can corrupt the view of a
page element if an
> editable region is included. I.e.
>
> <div class="leftsideCol">
>
> <li class="title">In-Page links</li>
>
<a href="#">Navigation Title</a></li>
>
<a href="#">Navigation Title</a></li>
>
<a href="#">Navigation Title</a></li>
>
<a href="#">Navigation Title</a></li>
>
<a href="#">Navigation Title</a></li>
>
<a href="#">Navigation Title</a></li>
>
<a href="#">Navigation Title</a></li>
>
> 
> 
> <p class="sidebarTitle">?! Notices !?</p>
> 
> <div class="sideMssgeBoxCntnr">
> <p class="sideMessageTitleBkgrndYel">Subject
Title</p>
> <p class="sideMessageBoxText">Put your message
here. Be succinct to avoid
> overcrowding the sidebar. Here is a <a
href="#">link</a> which can be
> removed
> by normal text delete.</p>
> </div>
> </div>
>
> The first region statements corrupt the view (remove
them and all displays
> correctly). This does not affect the final page.
>
> If I try to solve this by putting the region just inside
the UL and /UL
> tags
> the design view is good. BUT the resulting page has an
extra UL opening
> tag.
> Why is this, it upsets the styling?
>
> Where can I find a definitive set of rules for putting
regions around
> tags
> other than <p> which seems to work OK? I want to
make a set of LIs
> editable and
> be able to add another LI to the list.
>

(un)editable regions extension

Hello !
I'm currently trying to do an extension which would parse a
(JSF) DreamWeaver file, find a certain kind of tag and then make
all content nested into them uneditable.
Could anyone give me an hint ? Ideally, I would not use
templates, but I'm afraid I will have to. No problem.
The problem is that I would like to be as little intrusive as
possible regarding the page code : is there another way to proceed
than   ?
Another question : is there some kind of code like @@("")@@
which I could use ? Because this code is nice but I can't afford to
use nested templates : if I use it into a page, I want it to be
effective into that page, not into the one to which my page is a
template to.
I'm using DreamWeaver 8 & JavaScript.
Cheers,
TheGridOne

=____= I cannot believe that I am saying this, after writing ALL of that up, but thanks to "Dreamweaver CS5 for Dummies," I just learned that if you place: @@(" ")@@ within the Child/Nested Template's editable region that you DO NOT want passed down to your Child-Pages, it won't appear editable. Goodness knows why such an inconspicuous formula was the answer, but I guess whatever works. ...WHY WAS THIS INFORMATION SO DIFFICULT TO FIND?!?!?!?! @____@ Information on Nested Templates in general seems rather difficult to find, however, so I'm glad I figured this out /not ever a full hour/ after writing all this up and posting it. #__# ...At least my Child-Templates can work thoroughly now, though. So... Scenario FIXED. ^^
I only hope now that such information will appear helpful to anyone else hunting for this information via Google or other Search Engine in the future. And if there is anything at all that I am still officially missing, then do feel free to add it to the feed and let me know, because the last thing I need right now are more surprise difficulties to equally slow down the productivity of this massive project I've been working on... @___@ ..But so far things seem to be going good. ^^ So I can settle myself unbelievably grateful that there ended up being a solution to this ridiculousness after all.
Sincerely,
Miss Cat
[signature promo info removed by moderator]

Remove editable region

Similar Messages

Maybe you are looking for