Templates and editable regions < body >

I have a model for the site with all the div, as I would like.

If I area-editable regions, then where it says < body > in the template - it can be changed in a single page to say

< body onload = "DoThis (); ">

because as soon as you open the template, it is up to the page back to the < body > and the onload bit is lost.

I wanted to use templates to maintain consistency, but when you have problems with the editable regions all the time that I wonder if this is a feature implemented there to help or harm us.

I tried to put the tabs html in an editable area, but then the said model id had not.

Please how can I do the < body > tag editable in the various documents because I want this function to launch the load on one page only.

The only way around this would be to have an onload for each page and have only a function empty on the pages that is not required, but it's unprofessional.

I think that there is another thing like document.ready but don't know where to put it in the document, and if it is as effective.

THANK you for any comments.

TERRY

Try this, you can use it in any region can be changed as thesection of the page.

Tags: Dreamweaver

Similar Questions

How to remove the template and editable regions?

Hello world
I posted this question earlier in the area of discussion web to ignore a specific Dreamweaver forum. Sorry for posting in two places.
Since last week, I learned Dreamweaver CS4 to an on-line tutorial. I got to the place where I have generated a model (index.dwt) homepage (index.html) and created boxes on it. At that moment, I realized that I had done all the steps of the Rota and that he didn't really absorb what I was doing. I wanted to delete the model to repeat and acquire a better understanding of the process. When I tried to remove the editable regions (change-models-remove editable regions), I was unable to do so because 'remove the editable regions' is gray. Nor I was able to remove the html code. I tried to delete the template itself, but when I did, the index.html page kept these editable regions! Can someone tell me if there is a way to get back to the place I was forward to create the model?
Thank you for any assistance.

All you need to do is detach the template index.html file. Then you can remove the template and start all over again.

Go to the menu change--> models--> detach the model

Templates in DW CS5.5 and editable regions

I have a model page that has an editable region defined as follows:
< div class = "sidebar1″" >
< nav >
< ul >
< li > < a href = "#" > home < /a > < /li >
< li > < a href = "#" > < /a > < /li >
< li > < a href = "#" > < /a > < /li >
< li > < a href = "#" > < /a > < /li >
< li > < a href = "#" > Members Only < /a > < /li >
< li > < a href = "#" > Gallery < /a > < /li >
< li > < a href = "#" > Constitution < /a > < /li >
< li > < a href = "#" > links < /a > < /li >
< /ul >
< / nav >
<!-InstanceBeginEditable name = 'all'->
< / div >
<! - end .sidebar1 - >
< section class = "content" >
CBEF clubs < h1 > < / h1 >
< section >
other code goes here
< / section >
<! - InstanceEndEditable - >
Note the < / div > tag after the beginning of the editable region. It's a tag that is appropriate, it is necessary to close the div sidebar1″
When he is not in an editable area, the < / div > shows no upward in yellow in design veiw and it works in every respect.
When the combo box is introduced, the < / div > shows yellow in design mode, and it works in all respects.
It validates using the W3C validation page.
Pages built with it also show the yellow label, but they do not display it when live or in a browser.
If I delete the < / div > as dreamweaver indicates, breaks css and page do not work.
It seems that DW thinks that it is an illegal tag. If I click my mouse on the <!-InstanceBeginEditable name = 'all'-> tag and collapse of the tag, all the code in the edit box + than in the sidebare 1 div (even starting before the editable) collapses. The editable area does not allow changes in the sidebar1″ outside the region code.
I need to put the editable region in the part of the sidebar div 1 so that I can add aditional items floated in box 1 div if necessary later.
Is this a bug or am I missing something?

It would be more logical.

Some unique sidebar1″ content goes here

The unique position here

another code

Nancy O.

ALT-Web Design & Publishing

Web | Graphics | Print | Media specialists

http://ALT-Web.com/

Post edited by: Nancy O. I forgot to close the div. I'm glad

Templates, backgrounds and editable regions.
A simple question with, hopefully, a simple answer!
I designed a site that uses a background image (800 x 600) with links mapped offshore. So far so good. I then added an editable region, and in fact a model. My problem is the positioning of parts. My background image is set to the absolute center, but the combo box takes its location between the corner of the screen, not the background, so continues to move in different size screens. Is there a way to anchor the editable region in the background, so when one moves, the other not?

Thanks in advance,
Hmm, tried, and everything went to pot. But after combining the first two sets of advice, everything works fine. Thanks for the help.
P.S. I don't know the size, will sort that and other small pieces now, the site works!

CSS, DIV and editable regions

Hi all

I am having trouble about a fairly simple dreamweaver model in combination with an external css file. For design purposes, it should be all done using DIV (without tables).

That's what I am looking for: page 80% width, centered:

1 (editable) left header - the header right

2 menu

3 content (editable)

4 footer

It is particularly important that the content (3) can be changed WITHOUT interfering with the other DIV or anything else. Also, the left of the header (1) must be editable, but it is only text or banner or so.

I really hope that someone can help me here, because after hours of research, I'm kindof see letters, no words more ;-)

<!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" />
<!-- TemplateBeginEditable name="doctitle" -->
<title>Testing</title>
<!-- TemplateEndEditable -->
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
<link href="../Style/Main.css" rel="stylesheet" type="text/css" />
<script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
</head>
<body class="MainCssClass">
<div id="container">
<div id="header">
<div align="right"><!-- TemplateBeginEditable name="Header" --><!-- TemplateEndEditable -->Header</div>
</div>
<div id="Menubar">
<ul id="MenuBar1" class="MenuBarHorizontal">
  <li><a href="../index.html" title="Home" target="_self">Home</a></li>
  <li><a href="#">Contact</a></li>
  <li><a href="#">About</a></li>
</ul>
</div>
<div id="container">
  <div align="center"><!-- TemplateBeginEditable name="MainContent" -->
    <p align="center"> </p>
    <p align="center"> </p>
    <p align="center"> </p>
    <div id="mainContent">
      <p> </p>
    </div>
    <!-- TemplateEndEditable -->
    <!-- end #mainContent -->
  </div>
</div>
  <div id="footer">
    <p align="center">Footer</p>
<!-- end #footer --></div>
<!-- end #container --></div>
<script type="text/javascript">
<!--
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
//-->
</script>
</body>
</html>

And here is the external STYLE sheet that I use:

@charset "utf-8";
body {
 font: 100% Verdana, Arial, Helvetica, sans-serif;
 background: #666;
 /* margin: 0; it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
 padding 0 0 0 0;
 text-align: center; /* this centers the container in IE 5* browsers. The text is then set to the left aligned default in the #container selector */
 color: #CCC;
}
.MainCssClass #container {
 width: 80%;  /* this will create a container 80% of the browser width */
 height: 100%;
 background: #000;
 margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
 padding: 0; /* remember that padding is the space inside the div box and margin is the space outside the div box */
 border: 0px;
 text-align: right; /* this overrides the text-align: center on the body element. */
}
.MainCssClass #header 
{
 margin: 0 0 0 0;
 background-color: #FFF;
 color:#000;
 width:100%;
}
.MainCssClass #mainContent {
 padding: 10px 10px 10px 10px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
 background: #000;
 color:#CCC;
 text-align:center;
 height:auto;
}
.MainCssClass #footer 
{
 margin: 0; /* zeroing the margins of the first element in the footer will avoid the possibility of margin collapse - a space between divs */
 padding: 0 0 0 0; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
 font-size: small;
 background-color:#666;
}
#divLeft { 
 float:left; 
 width:50%;
} 
#divRight { 
 float:right; 
 width:20%;
}

I've been trying and troubleshooting all afternoon, but I can't seem to find what I'm doing wrong. Can someone advise me on this? I'm afraid it's the nested DIV I mix it up.

Any help would be really appreciated!

Thank you

Mich

CSS:

{body
Police: 100% Verdana, Arial, Helvetica, without serif.
Background: #666;
/ * margin: 0; It is advisable to zero, the margin and the filling of the body to hold element has a different default browser * /.
fill 0 0 0 0;
text-align: center; / * This centers the container in IE 5 * browsers. The text is then set left aligned by default in the #container selector * /.
color: #CCC;
}
. MainCssClass #container {}
Width: 80%; / * This will create one that contains 80% of the width of the browser * /.
Background: #000;
margin: 0 auto; / * margins (in conjunction with a width) auto Center the page * /.
padding: 0; / * Remember that the fill is space inside the box of div and margin is the space outside the div box * /.
border: 0px;
text-align: left; / * This setting overrides the text-align: center on the body element. */
overflow: hidden; / * encapsulates container around the floating elements inside * /.
}
. MainCssClass #header
{
background-color: #0F3;
Color: #000;
overflow: hidden;
}
{#divHeaderLeft}
float: left;
Width: 50%;
}
{#divHeaderRight}
float: right;
Width: 20%;
}
. MainCssClass #content {}
padding: 10px 10px 10px 10px; / * Remember that the fill is space inside the box of div and margin is the space outside the div box * /.
Background: #000;
color: #CCC;
text-align: center;

}
. MainCssClass #footer
{
margin: 0; / * zero setting the margins of the first element in the footer will avoid the possibility of the collapse of the margin - a space between the div tags * /.
padding: 0 0 0 0; / * padding on that element will create space, just as it would the margin, free margin collapse question * /.
font size: small;
background-color: #666;
}

Error in adding an editable region in the nested template header
I have a basic model for the website (creation of main menus) and a secondary model using this basic model, which establishes a common table, on the one hand of the site layout. After you create the PHP to drive page, I need to lock this secondary nested region - otherwise any edit I make on my secondary & quot; -definition of table & quot; model is not passed to the last pages using the secondary model. I created a secondary edit box successfully in every part of the & lt; body & gt; region, and of course, it locks text outside the secondary editable help DW says it should. So far so good.

Now the problem - I can not create a region inside the & lt; head & gt; combo box to lock this region too. Normally we'd like keywords and so on to be variable from one page to another, but as I am filling variable keywords from a database, it makes sense to lock the & lt; head & gt; Too much. Does anyone know why that generates an error & quot; failed to create an optional region here & quot;? Is there anything we can do about it?
> by whom?
This is DW CS3 help on nested models:

A nested template is a template whose design and editable regions is based on another model. Nested models are useful for the control of content in the pages of a site that share many design elements, but have some differences between pages. For example, a basic model can contain broader design areas and be usable by many contributors of content on site, while a nested model can further define the editable regions in the pages of a specific section of a site.

> the solution
I just figured out how to lock the header in the document of reference to TechNote 16416. It is referenced in the called DW CS3 help page

Prevent an editable region to a nested model

In summary - insert the marker @@("") @ in the editable area.

I tried it and it works perfectly! The cephalic region is now locked in the nested template, so the changes in this area went from child pages. That's the answer.

> your book
Yes, I saw it on Amazon. Kudos to you for publication.

> your suggestion extracted
Thanks for that. This looks like a more manual approach, however.

> mysteriously missing paragraphs
Very strange, I can see them on my screen in Firefox and IE7.

Best regards
Richard

Make editable regions in a template

I have a model in which I want to make an editable region uneditable. Is this possible?
Appreciate any input
Gilbert

Yes.

With the model of open file, select the area you want to make editable and go to insert > template objects > editable region and then give it a meaningful name.

Alternatively, wrap the code around the area you want to be editable and name, below, both do exactly the same thing: just in different ways.

How to apply a template with a new editable region to a group of existing pages

Hello
Here's my question:
1. I have a group of web pages that were created by using a template with editable regions.
2. I added a new editable region to a template that should be added to the previous pages.
What is the procedure to add the new editable region to previous web pages?
Thanks for your advice
Juan

When you have saved the model, you have been invited by Dreamweaver to ask if you want to update pages based on the template. As long as you click Update, the new editable region should be in the pages of the child.

Fixed size on editable regions Dreamweaver?

Dear all,
I have inexplicable problems with my Web site template.
Well, I did my site template Web everything is where it should be etc. However, when I try to insert an editable on my Web site region, it extends the editable area.
It's the process that I take to insert an editable region.
I select my "content" div tag Then I click on Insert > template objects > editable region. When I click on 'editable' my 'content' div tag extends the size of the page - which is what I don't want.
Please can you tell me if I'm doing something wrong or if there is further about this.
Thanks a lot for reading

After these steps, my code is changed it-

...

on this subject.

...

Is that what you see also? In this case, the editable region is not wider than the content div (i.e., 660px; such as defined in the CSS).

What DW and which platform do you use (PC/Mac)?

New model Page - lack of editable regions

When you use the new template Page, the resulting HTML code is missing from the editable regions.

I've created a very simple HTML page, saved as a template, assigned editable regions, saved. Then, I created a new Page of the model.

Here's the code in this file as well as the resulting HTML file.

TestTemplate.dwt

<!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" />
<!-- TemplateBeginEditable name="doctitle" -->
<title>Test Template</title>
<!-- TemplateEndEditable -->
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
</head>

<body>
<table>
 <tr>
  <td><!-- TemplateBeginEditable name="EditRegion3" -->One<!-- TemplateEndEditable --></td>
  <td><!-- TemplateBeginEditable name="EditRegion4" -->Two<!-- TemplateEndEditable --></td>
  <td><!-- TemplateBeginEditable name="EditRegion5" -->Three<!-- TemplateEndEditable --></td>
 </tr>
</table>
</body>
</html>

TestTemplate.html

<!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>Test Template</title>
</head>

<body>
<table>
 <tr>
  <td>One</td>
  <td>Two</td>
  <td>Three</td>
 </tr>
</table>
</body>
</html>

I use Dreamweaver CS5 (Version 11.0 Build 4993) on MAC OS X 10.6.8.

This is the first time that I am using models in CS5. They worked fine when I used CS4 (on the same computer). Now I have CS5.

Note that your child page contains model NO markup at all. This means that when you created it, you should not do check the box called "update page when the template is changed" (on the right side of the new Document dialog box). Could this be it?

The editable regions and Flash animation
Hello

I'm trying to insert a flash movie into an editable region of a page of the child, but I get the following error: "this change should change the code which is locked by a model or a translator. The changes will be rejected. »

I read the previous posts on the same topic, but none of them does answer my question. I tried to create a new model and a child by him as a test by removing the css links (as someone suggested to do) to try to identify troubled css and I kept getting the same error in the new pages. I hope someone can help identify the problem and the solution. The area where I want to insert the movie is called "FinalMainContent".

BTW, I don't know how to write the code... Sorry!

Thanks in advance for any help you can provide!

Here is the code:

<! DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional / / IN".
" http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" > ".
<!-saved from url = (0014) subject: internet->
"< html xmlns =" http://www.w3.org/1999/xhtml "> <! - model InstanceBegin =" / models/hand Pages.dwt "codeOutsideHTMLIsLocked =" false "- >"
< head >
<!-InstanceBeginEditable name = "doctitle"-->
< title > TotusMundus - video/Film < /title >
<! - InstanceEndEditable - >
< meta http-equiv = "Content-Type" content = text/html"; Charset = UTF-8 "/ >"
<!-target fireworks 8 Dreamweaver 8. Created Sat Jan 13 16:43:41 GMT - 0500 () 2007->
< link href = "TotusMundus_Styles.css" rel = "stylesheet" type = "text/css" / > "
<!-InstanceBeginEditable name = "head"->
< link href = "Templates/TotusMundus_Styles.css" rel = "stylesheet" type = "text/css" / > "
<! - InstanceEndEditable - >
< script language = "JavaScript1.2" type = "text/javascript" >
<!--
function MM_findObj (n, d) {//v4.01
var p, i, x; if(!d) d = document; If ((p = n.IndexOf ("?")) > 0 & & parent.frames.length) {}
d = parent.frames [n.Substring(p+1)] .document; n = n.Substring (0, p) ;}
If (!) () x = d [n]) & & copyrights) x = d.all [n]; for (i = 0;! x & & I < d.forms.length; i ++) x = d.forms [n];
for (i = 0;! x & & d.layers & & I < d.layers.length; i ++) x = MM_findObj(n,d.layers.document);
If (! x & & d.getElementById) x = d.getElementById (n); Return x;
}
function MM_swapImage() {//v3.0
var i, j = 0, x, a = MM_swapImage.arguments; document. MM_sr = new Array; for (i = 0; i <(a.length-2); I += 3).
If ((x = MM_findObj (un ))! = null) {document. MM_sr [j ++] = x; if(!x.oSrc) x.oSrc = x.src; x.SRC = a [i + 2] ;}
}
function MM_swapImgRestore() //v3.0 {}
var i, x = offline. MM_sr; for (i = 0; a & & I <.) Length & & (x = a) & & x.oSrc; i ++) x.src = x.oSrc;
}

function MM_preloadImages() {//v3.0
var d = document; If (d.images) {if(!d.MM_p) d.MM_p = new Array();
var i, j is d.MM_p.length, a = MM_preloadImages.arguments; for (i = 0; i <.) Length; i ++)
If (one .indexOf("#")! = 0) {d.MM_p [j] = new Image; d.MM_p [j ++] .src = a;}}}
}

->
< /script >
< script type = "text/javascript" src = "p7pm/p7popmenu.js" > < / script >
< style type = "text/css" >
TD img {display: block ;} < / style >}

< style type = "text/css" media = "screen" >
<!--
@import url("p7pm/p7pmv0.css");
a: link {}
color: #999999;
text-decoration: none;
}
a: visited {}
text-decoration: none;
Color: #666666;
}
a: hover {}
text-decoration: none;
Color: #666666;
}
a: active {}
text-decoration: none;
Color: #666666;
}
->
< / style >
< script src = "Scripts/AC_RunActiveContent.js" type = "text/javascript" > < / script > "
< / head >
< body onload = "P7_initPM (0,0,1,0,-8); "MM_preloadImages (" Images/LinesBtn_f2.jpg','Images/SmallFlow erBtn_f2.jpg','Images/SquigliBtn_f2.jpg','Images/StarBtn_f2.jpg','Images/DoubleSquigliBtn_ f2.jpg','Images/BigFlowerBtna_f2.jpg','Images/PrevBtn_f2.jpg','Images/NextBtn_f2.jpg'");" > < table align = "center" border = "0" cellpadding = "0" cellspacing = "0" width = "800" >
"<!-fwtable fwsrc ="Index.png"fwbase =" TotusMundus.jpg "fwstyle ="Dreamweaver"fwdocid ="1262947761"fwnested ="0"->
< b >
"< td > < img src ="Images/spacer.gif"width ="116"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="8"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="182"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="109"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="102"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="180"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="7"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="96"height ="1"border ="0"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="1"height ="1"border ="0"alt =" "/ > < table >
< /tr >

< b >
"< td rowspan ="2"colspan ="7"> < a href =" index.htm "> < img name ="LogoAnfTagLine"src = Images/LogoAnfTagLine.jpg" "width ="704"height ="100"border ="0"id ="LogoAnfTagLine"alt =" "/ > < /a > < table >
"< td > < img name ="MusicTitle"src ="Images/MusicTitle.jpg"width ="96"height ="74"border ="0"id ="MusicTitle"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="1"height ="74"border ="0"alt =" "/ > < table >
< /tr >
< b >
< td rowspan = "4" > < a href = "" javascript:; "" MM_swapImgRestore; "onmouseover =" MM_swapImage ('LinesBtn', ", ' Images/LinesBtn_f2.jpg', 1);" "" > < img name = "LinesBtn" src = "Images/LinesBtn.jpg" width = "96" height = "57" border = "0" id = "LinesBtn" alt ="" / > < / a > < table >
"< td > < img src ="Images/spacer.gif"width ="1"height ="26"border ="0"alt =" "/ > < table >
< /tr >
< b >
"< td colspan ="7"> < img name ="CushionforPath"src ="Images/CushionforPath.jpg"width ="704"height ="13"border ="0"id ="CushionforPath"alt =" "/ > < table >
"< td > < img src ="Images/spacer.gif"width ="1"height ="13"border ="0"alt =" "/ > < table >
< /tr >
< b >

OK, I thought about it: the problem is that in the window options, when I tried to insert Flash video, I ticked the box: 'invite users to download Flash Player if necessary.' It was not allowing me to insert. When I unchecked, the error message disappears. I guess, I have to add this option to download in a different way.

Thank you for taking the time to answer. Much appreciated!

MS

An editable region in the & lt; body & gt;
I'm doing customizable body IDs so that I can make the anchor points of the visited links "you are here" on my site. Here is the code that I follow:

Here are three elements of the "you are here link":

The body ID: body id = 'about' >

The link: < a href = "about.html" id = "aboutLink" >: on < /a > "

And the CSS:

body #about a {#aboutLink
background-color: #fff;
color: #900;
}

Now, I know it works because I did several times with the pages that are performed outside of Dreamweaver. HOWEVER, because I use models and nested models, I can not set the id when using this feature because Dreamweaver does not allow me to create an editable region before the < body > element in the HTML code.

So far, my work around solution was to change the .html and .dwt (model) of the files in Notepad, and sneak in my < id body = "#" >. However, this solution proves to be short-lived, because as soon as you edit again the model files in Dreamweaver, it crushes everything that has been done outside of Dreamweaver.

I need to create links 'you are here', but can't think of any other way to make them. Thank you for your comments.

Web page in question
rausch_g wrote:
> I can not set the id when using this feature because
> Dreamweaver does not allow me to create an editable region before the
> element in the HTML code.

This question was asked a few days ago. Do a forum search or
Using Dreamweaver for "editable attribute. Dreamweaver templates allow you to
create editable attributes, that does exactly what you want.

--
Adobe Community Expert David Powers
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Messed up the editable regions in the documents based on templates

Y at - there no way to fix corrupt editable regions in a document?
We have 2 editable regions in a template: -.
<!-TemplateBeginEditable name = "MidText"->
< p > < / p >
<! - TemplateEndEditable - >
<!-TemplateBeginEditable name = "LowText"->
< p > < / p >
<! - TemplateEndEditable - >
In several documents based on these models, the name has been deleted by mistake: -.
<!-TemplateBeginEditable name = ""-> "
< p > < / p >
<! - TemplateEndEditable - >
<!-TemplateBeginEditable name = ""-> "
< p > < / p >
<! - TemplateEndEditable - >
If we try to update the documents in an attempt to fix, we get the following error message:
There is an error on line..., column... (absolute position...) of "nomDuDocument": name missing for InstanceBeginEditable ""
If we try to update using the templates, we get the following error message:
no update, error in the file of template or instance
Is there a 'fix' for this?
Thank you.

Looks like you know what you're doing.

Assuming your child pages are incorrect, try closing DW and open the problem page in a simple editor like Notepad or Simpletext ascii text, add in the missing name values (remember to use the proper case) and save & close them.

Then see if DW is happy.

Nesting templates: child-model Pages does not fully to the Editable vs a-Editable regions

Me kay, so first of all, it's all done within Dreamweaver CS5. How can I explain this, is that I have a series of Master-models for my site, then accompanied by child-models related to offshore of / nested my master-models. So far it's going wonderfully, until what I'm trying to make a page of one of my children-models.
The page of my child-model accurately comment on an non editable (region in which is editable in the master model, but left as ONLY editable within the child-model) as long as I add an EDITABLE area it contains. In the circumstances I have DO NOT add an editable region in the editable area of the master model, the area within the Page is appearing always editable.
For example:
__________________
Model Master:
<!-TemplateBeginEditable name = "ChildTemplateCSSLinks"->
Model child CSS links here.
<! - TemplateEndEditable - >
_____
Child model:
<!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->
Model child CSS links here.
<!-TemplateBeginEditable name = "ChildPageCSSLinks"->
Child CSS PAGE links here.
<! - TemplateEndEditable - >
<! - InstanceEndEditable - >
_____
The child page:
Model child CSS links here. (Precisely appearing not editable - {editable area of the master model tags appearing exactly invisible})
<!-InstanceBeginEditable name = "ChildPageCSSLinks"->
Child CSS PAGE links here. (Accurately appearing editable)
<! - InstanceEndEditable - >
__________________
It is a WORKING example of editable regions. In the child Page "Template CSS child links here." Appearing in comment and therefore not editable in the child Page, as if it was supposed to be. This time allows the 'child PAGE CSS links here' to be editable with PRECISION within the child-Page.
Now for an example of what does not work:
__________________
Model Master:
<!-TemplateBeginEditable name = "ChildTemplateCSSLinks"->
Model child CSS links here.
<! - TemplateEndEditable - >
_____
Child model:
<!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->
Model child CSS links here.
(As you can see, I've added an extra editable within the editable area of the master model. This is an area which is supposed not to be editable within the child-model and NOT the child-Page, which seems to be up to NOW accurate.)
<! - InstanceEndEditable - >
_____
The child page:
<!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->
Model child CSS links here.
(For a reason, THAT as long as I DO NOT add an additional child-model - edit box in the editable area of the master model, this area is appearing ALWAYS visible but also editable in the child Page.)
<! - InstanceEndEditable - >
__________________
So, in this circumstance, it seems that the only way I can leave ALONE the editable region of the master model can be changed within the child-model and NOT editable in the child Page is leaving an ADDITIONAL editable produced through the child-model somewhere within the editable region EVERY SINGLE, produced by the master model. Unless I do something bad, it seems this until a potential defect/bug in Dreamweaver CS5. I can't imagine how this would be correct, otherwise child/Nested-Templates would be not possible to do. What could I do it wrong? Is it possible that I can specify in the master model is an editable editable ONLY within the child-model and NOT yet child-Pages (A Page based on the template of the child)? Or maybe is it possible that I can specify the child-model that an area can be changed WILL NOT be editable in the child Page? Furthermore, no, I DON'T want to make "Optional Regions", so please do not suggest that.
I know it's all probably a little confusing, but I hope the examples above more than descriptions aside. As you can probably assume, it is definitely a HUGE complication in my site if it does not end up being a solution, especially with all the time I put into making the child models, which I hope to rely on. It would be really silly if I had to script - in an editable region extra in each master-model-editable-region unique available within my child-model just so that I can update my child-model, in addition to my changes to my child-Pages, to fall as much as it would maintain the content that I never wanted to be editable in the child Page in the FIRST place.
Some help would be appreciated sincerely, as soon as possible, if I could ask politely.
Thank you. Sincerely,
~ Miss Cat

= _ = I can't believe that I say this, after having written ALL that a period, but thanks to 'Dreamweaver CS5 for Dummies,' I just found out that if you place: @@("") @ in the editable area of the desired child/Nested model DO NOT passed down for your child-Pages, it won't appear not editable. God knows why such a discrete formula was the answer, but I guess that everything works. ... WHY WAS IT SO DIFFICULT TO FIND INFORMATION? @_ @ Information about nested templates in general seems quite hard to find, however, so I'm glad that I thought that this output /not/ never a full hour / after writing all this upward and detachment. #__# ... At least my child models can work perfectly now, though. Then... FIXED scenario. ^^

I hope that now this information will appear useful to someone else hunting for that information via Google or other search engine in the future. And if there is nothing at all that I'm still officially missing, then do feel free to add to food and let me know, because the last thing I need now of law are more surprising difficulties also slow down the productivity of this vast project I worked on... @_ @... But so far things seem to be going well. ^^ So I can just incredibly grateful that he will eventually be a solution to this ridiculous after all.

Sincerely,

Miss Cat

[info promo signature removed by Moderator]

Editable regions, nested on template

The model has 2 elements of library, each container javascript rollovers and a couple of editable regions. He recorded without error and fine views. But when I try to create a file based on the template, the error reads: ' there is an error on line 152, 190 (absolute position 8582) column of... ". Filename. nested editable regions.
http://www.aptcoweb.com/templates/aptcopage.dwt

Now I see it. Open your model, go to line 152 and remove this block of code:

It is a repetition of thetag and it confuses your model.

You should also validate your model. I see several incorrect entries for XHTML. For example, images tags should be closed with a "" / > "(space-bar oblique-angled support), not just ' > '."

Templates and editable regions &lt; body &gt;

Similar Questions

The unique position here

Maybe you are looking for

Templates and editable regions < body >