Warning against a DWT editable region

Similar Questions

• TemplateBeginEditable tag inside the editable region

  I bought a HTML template several years and it works fine until I updated for Dreamweaver on creative cloud. I can still update the pages, but now I can't update a page template. I get the following error whenever I try to update a page template:

  There is an error on line 49, column 47 (absolute position 2839) of (Template:main.dwt) TemplateBeginEditable tag inside the editable region

  My temporary solution was to go back to an older version of Dreamweaver (CS5) on an old Mac to make updates to the model. But I would like to solve this problem, so I can make changes in CC model.

  Here is the code to the top of the site, including the line 49 (I replaced some content meta here with "xyz")
  FYI: line 49 is: <!-TemplateBeginEditable name = "head"->

  <! DOCTYPE html >

  < head >

  < meta http-equiv = "Content-Type" content = text/html"; Charset = UTF-8 "/ >"

  < meta http-equiv = "X-UA-Compatible" content = "IE = edge, chrome = 1" >

  < meta name = "viewport" content = "width = device-width, original scale = 1.0" >

  <!-< META HTTP-EQUIV = "refresh" CONTENT = "15" > - >

  < meta name = "author" content = "xyz" >

  "< link rel ="shortcut icon"href ="... / favicon.ico ">"

  "" < link rel = "image_src" href = "... / img/logos/Lc_ZAR_dot_FE4F00_B8BABC.jpg" / >

  <!-* fonts Google / /-->

  < link href =' http://fonts.googleapis.com/CSS?family=Raleway:400,100,200,300,500,600,700,800 ' rel = "stylesheet" type = "text/css" >

  < link href =' http://fonts.googleapis.com/css?family=Lato:100, 300, 400, 700, 900, 100italic, 300italic, 400ita lic, 700italic, 900italic ' rel = "stylesheet" type = "text/css" >

  < link href =' http://fonts.googleapis.com/css?family=Open+Sans:400, 300, 300italic, 400italic, 600, 600italic, 700italic ' rel = "stylesheet" type = "text/css" >

  < link href =' http://fonts.googleapis.com/CSS?family=open+sans+condensed:300, 300italic, 700 ' rel = "stylesheet" type = "text/css" >

  <! - core bootstrap CSS - >

  "" < link href = "... / css/bootstrap.min.css" rel = "stylesheet" type = "text/css" >

  <!-Custom-> CSS

  "" < link href = "... / css/animate.css" rel = "stylesheet" type = "text/css" >

  "" < link href = "... / css/jquery.mCustomScrollbar.css" rel = "stylesheet" type = "text/css" >

  "" < link href = "... / css/font-awesome/css/font-awesome.min.css" rel = "stylesheet" type = "text/css" >

  "" < link rel = "stylesheet" href = "... / css/colorbox-skins/4/colorbox.css" type = "text/css" >

  "" < link href = "... / css/main.css ' rel ="stylesheet"type =" text/css">

  "" < link href = "... / css/header/h1.css" rel = "stylesheet" type = "text/css" >

  "" < link href = "... / css/responsive.css" rel = "stylesheet" type = "text/css" >

  "" < link href = "... / css/color1.css" rel = "stylesheet" type = "text/css" id = 'site-color' >

  "" < link href = "... / css/rivathemes.css" rel = "stylesheet" type = "text/css" >

  <! - LayerSlider styles - >

  "" < link rel = "stylesheet" href = "... / css/layerslider/css/layerslider.css" type = "text/css" >

  <!-only for debugging purposes. Do not copy this line really! ->

  "<!-[if lt IE 9] > < script src="js/vendor/ie8-responsive-file-warning.js "> < / script > <! [endif]-->

  <! - HTML5 shim and Respond.js IE8 takes in charge of HTML5 elements and questions from the media - >

  <!-[if lt IE 9] >

  " < script src =" https://OSS.MaxCDN.com/libs/html5shiv/3.7.0/html5shiv.js "> < / script > .

  " < script src =" https://OSS.MaxCDN.com/libs/respond.js/1.4.2/respond.min.js "> < / script > .

  <! [endif]-->

  "< script src ="... / js/vendor/modernizr-2.6.2-respond-1.1.0.min.js "> < / script >"

  "< script src ="... / js/twitterFetcher_v10_min.js "> < / script >"

  < script type = "text/javascript" >

  <!--

  function MM_openBrWindow (theURL, winName, features) {//v2.0

  Window.Open (Theurl, winName, Features);

  }

  ->

  < /script >

  <!-TemplateBeginEditable name = "head"->

  < meta content = "description" name = "xyz" >

  < meta name = "keywords" content = "xyz" >

  XYZ < title > < /title >

  <! - TemplateEndEditable - >

  < script >

  (function(i,s,o,g,r,a,m) {I ['GoogleAnalyticsObject'] = r; i [r] = [r] i: function() {}})

  (.q i [r] = [r] i .q |) ([]) .push (arguments)}, l i [r] = 1 * new Date (); a = s.createElement (o),

  m = s.GetElementsByTagName (o) [0]; a.Async = 1; a.SRC = g; m.parentNode.InsertBefore (a, m)

  ({ }) (window, document, 'script','https://www.google-analytics.com/analytics.js', 'ga');

  GA ('create', ' UA-79018338-1 "," auto");

  GA ('send', 'consultation');

  < /script >

  < / head

  I wonder if this is related to the code Linting.  Maybe if you disable the Linting in preferences DW will leave an error appears when there seems to be none.

  Otherwise, try to restore preferences-

  Unusual behavior in Dreamweaver? Restore preferences.

  Or continue to use the previous version of DW with this model.

  Nancy O.

• Can spry menu cause editable regions?

  Hello. I have two questions menu spry that I hope someone can answer:

  1. I use a horizontal menu spry in my template for my navigation bar (pictured below). But I would like to make the "Menu" tab Middle an editable, so that I can change its destination of links on certain pages of the subsites. Is this possible? I tried to insert an editable region in the spry, but Cree Dreamweaver warnings against me and, when I went anyway, the navigation bar broke out on my pages.

  

  2. I want to only the 'Previous' and 'Next Page' tabs to display on some subpages (and maybe to hide tab "Menu" way). I do not think that an optional region will work in the spry, so I tried just type the new tabs on each side of the menu spy. But, once again, Dreamweaver got mad at me and broke my navigation bar.

  Any suggestions on how I can either work around? Or sprys are not otherwise flexible? I was wondering if I could create two different navbars and make the two optional regions, but still, I don't think it's possible.

  Thanks to all those who can help you.

  Hmm.

  I've never considered part of an editable Spry menu bar, but you can do it. Simply ensure that you delete it or don't overlap the necessary code, and I think the submenus will be problematic.

  When you want to change a menu item, do it in code view, and then select all the contents of the list item:

  Point 1.1

  This way, you will be able to change the link and the text of the item...

  If Dreamweaver warns you that you are working in a block element, don't you worry about this. You know, and it won't hurt anything in this case.

  There will be other ways to build local versions of the menu. If you need the submenus, you must remember to add some class designations, which you certainly can do it if you're careful. I personally would opt for several different menus controlled from the style sheet. It would be a bit more complicated, but then you don't have to remember to go to all the pages to set the menu. I don't know your project, so I couldn't say if it would be a great loss of time or useful. If you were to use the same menu on several pages, it can be useful. If each page is different anyway, make your way!

  In addition:

  I did a modifiable menu item and the code looks like this: each editable region will have its own name.

  Point 2

  Beth

  Post edited by: Zabeth69

• Is it possible to add an editable region where codeOutsideHTMLIsLocked = 'true '.

  Is it possible to add an editable when codeOutsideHTMLIsLocked = 'true' and an editable region is added?

  When I try the following, the first line is grayed out and cannot be changed, but the rest is not grayed out and apparently all editable.

  <!-InstanceBeginEditable name = 'model'->

  I'M EDITABLE

  <! - InstanceEndEditable - >

  I'M NOT EDITABLE

  <! doctype html >

  "< html > <!-InstanceBegin template="/Templates/main.dwt.cfm "codeOutsideHTMLIsLocked ="true"->

  < head >

  < meta charset = "utf-8" >

  <!-InstanceBeginEditable name = "doctitle"-->

  < title > Untitled Document < /title >

  <! - InstanceEndEditable - >

  <!-InstanceBeginEditable name = "head"->

  I'M EDITABLE

  <! - InstanceEndEditable - >

  < / head >

  < body >

  I'M NOT EDITABLE

  <!-Name = 'body'-> InstanceBeginEditable

  I'M EDITABLE

  <! - InstanceEndEditable - >

  < / body >

  <! - InstanceEnd - > < / html >

  I use Dreamweaver CS6 Version 12.0 Build 5861

  Take a look at templates using Dreamweaver to design a page layout, Scripts in the section server models.

• Model Dreamweaver, renounce the error 'instancebegineditable tag inside the editable region.

  I searched the internet and no matter what forum I can find about Dreamweaver and find the solutions that they don't did not help me, but there was a problem of command for many people. I created a template by following the steps via a tutorial from helpvid.net and the website looked very good to be pretty basic but since last night when I try save the model gives the error message "there is an error in line 8, column 47 (absolute position 789) of 'address of the file': InstanceBeginEditable tag inside the editable region.» Now from what I have read on the forums that means usually there is a spelling error or something placed inside the area when should not be, but there are only 50 odd lines on it and can't see any problem. When I view the files it gives error on, replicas of the editable 'start' there are has a number of times, but they shouldn't be there because they are not on the model. IM also conclusive that until this error came pages went well when downloaded, but now the footer height that has been set to 20px is 200px when downloaded and I check all coding for it so the Divs see but still no error. I downloaded my tempalete and some of the pages that mistakes about donations to see if that help, do not know if its better just stick wall of coding so sick message links to the files and if the code must be pasted here ill do it. http://dublinmoulding.com/ <-work im site, one can see the footer is very large. Should be 20px height but inspect element shows his 200px - #wrapper #footer {color: #FFF;}     height: 200px; The model is #wrapper #footer {color: #FFF;}     text-align: center;     margin: 0px;     do-size: 18px;     make-style: normal;     make-weight: lighter;     do-family: Arial, Helvetica, without serif.     padding-top: 5px;     padding-right: 0px;     padding-bottom: 5px;     padding-left: 0px;     height: 20px; http://dublinmoulding.com/dreamweaver/temp1.dwt <-my error tempalate is abandoned on pages created by using the template

  
  

  * Update * I've edited file names of some of the pages I used the template on so now it shows as coding.

  
  

  http://dublinmoulding.com/Dreamweaver/index.html6 <-my index page

  http://dublinmoulding.com/Dreamweaver/about.html6 <-on the page
  

  I've recreated the model and its not waive errors and the layout seems well, hurt that mark as resolved thank you for help

• 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?

• 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 ' > '."

• 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

• 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 &amp; lt; body &amp; 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/

• Masking of non editable regions

  When I work with a page based on a template .dwt, can I put DW8 to not show me anything other than the editable regions? I wish I could see just the editable stuff and not have all the code grayed out of the way.

  No - sorry.

  --
  Murray - ICQ 71997575
  Adobe Community Expert
  (If you * MUST * write me, don't don't LAUGH when you do!)
  ==================
  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
  ==================

  "Drew PCR" wrote in message
  News:eid9gb$7lb$1@forums. Macromedia.com...
  > Info collapse appears not to forward to the .dwt pages.
  > What to do
  > I would like to is to open a new page based on a template and DOESN'T see that the
  > editable
  > code.
  >
  > Y at - it a hotkey to access the following editable or
  > something?
  > That's all just annoying having to fish through things that I can't change anyway
  > in order to get to the line, I want to change...
  >

• Can you have editable regions in content holders?

  Hello world

  I had a bit of difficulty getting my work, the editable regions that, through a process of trial and error, I have locked because they do not work if included in a model by the holder of a content.

  This isn't a major problem, but it does not mean I will need the same code in all of three of the four of my models. Initially I store this code in a content holder and pulling the support content in wherever she was needed in a model.

  Of course, I prefer to do the second way for efficiency, maintainability, etc., but I'm not really sure where to start to solve the problem. Does anyone have ideas on this? Is this something that certainly can not be done, or I just do right?

  I'd be interested to hear comments, thanks in advance.

  Hello Ricki,

  You can have editable in your door-content areas, even if the owner of your content is part of the model, it will be always editable through the "Edit" tab on your admin.

  "Don't forget to add some ice: editable = 'content' in your module_contentholder, after the name =" "parameter. This doc will help you, see the.

  The second important thing is to add a coma as he is mentioned in the doc, after the module_contentholder, otherwise that the content will not be rendered, it will just show you the syntax as specified in the model, and you don't want that.

  See you soon,.

  Cristian

• Create a nonmodifiable (coastal region) within an editable region

  Hello

  So basically, I have my main model that updates the menu and footer on all my pages. On this model, there is an editable region for most of my pages. This model, I have created several models (nested templates?) secondary. On those, I need to have a box of links on the right. Each set of links would be different based on the model and I need the secondary models to update the links on their pages.

  I work with a checkerboard in fluid, and I think that this is part of my problem. If I put the links inside the editable region "content" box then it is changes are not reflected in the updates. But if I put it outside the editable 'content' it lies either above or below the main content of the page. I want the main to wrap around the box content.

  It's my current site is NOT fluid grid. See how the text will wrap around the area outlined in green in? Program of salt marshes

  I use Dreamweaver CS6.

  Any help would be appreciated. Thank you!

  Nested models are never a good option. Never, ever.

  I recommend using 'editable optional regions' instead.

  Using Dreamweaver | Using optional regions in templates

  Or, my favorite way is to use the Server - Side Includes - alone or with models.

  ALT-Web Design & Publishing: Inclusions with PHP server-side

  Nancy O.

• 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]