Dreamweaver template giving up "instancebegineditable tag inside editable region" error

I have been searching the internet and any forum I can find relating to Dreamweaver and find it has been a comman problem for a lot of people but the solutions they got have not helped me. I created a template by following steps via a helpvid.net tutorial and the site looked very good for being basic enough but since last night when I try save the template it gives up the error "there is an error at line 8, column 47 (absolute position 789) of "file address": InstanceBeginEditable tag inside editable region." Now from what I have read on the forums it usually means there is a mispelling or something placed inside the region when it shouldn't be but there is only 50 odd lines on it and can't see any problem. When I view the files it gives the error about, there are duplications of the "begin editable region" a number of times but they shouldn't be there because they aren't on the template. Im also finding that before this error came up the pages looked fine when uploaded but now the footer height which was set to 20px is 200px when uploaded and I have checked all coding for it and checked the Divs but still see no error. I have uploaded my tempalete and some of the pages that its giving errors about to see if that helps, not sure if its best to just paste wall of coding so ill post links to the files and if code needs to be pasted here ill do so. http://dublinmoulding.com/ <- site im working on, it can be seen the footer is very big. Should be 20px height but inspect element shows its 200px - #wrapper #footer {     color: #FFF;     height: 200px; On the template it is #wrapper #footer {     color: #FFF;     text-align: center;     margin: 0px;     font-size: 18px;     font-style: normal;     font-weight: lighter;     font-family: Arial, Helvetica, sans-serif;     padding-top: 5px;     padding-right: 0px;     padding-bottom: 5px;     padding-left: 0px;     height: 20px; http://dublinmoulding.com/dreamweaver/temp1.dwt <- my tempalate The error is given up on every page created using the template
**Update**  I edited the file names of some of the pages that I used the template on so now it shows the coding.
http://dublinmoulding.com/dreamweaver/index.html6  <- my index page
http://dublinmoulding.com/dreamweaver/about.html6 <-about page

No need for tricks.  We can view source code directly from our browsers or with Inspect Element.
Like I said, I don't see any code errors in your Template or child pages. 
If DW continues to display errors,  the first thing to try is Deleting Corrupted Cache in DW
http://forums.adobe.com/thread/494811
If that doesn't help, try Restore Preferences
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
Nancy O.

Similar Messages

  • "instancebegineditable tag inside editable region"

    i've tried to update my site and it wont let me. i keep getting this error "instancebegineditable tag inside editable region" im not sure how to fix it..

    Here is my code.....
    <!doctype html>
    <html><head>
    <meta charset="utf-8">
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>My Portfolio - Add Title Here</title>
    <!-- TemplateEndEditable -->
    <style type="text/css">
    body {
      background-color: #CCCCCC;
      color: #000;
      height: 100%;
      margin: 0px;
      padding: 0;
      font-family: "Arial Rounded MT Bold", Arial, Helvetica, sans-serif;
      font-size: 100%;
    ul, ol, dl {
      padding: 0;
      margin: 0;
    h1, h2, h3, h4, h5, h6, p {
      text-align: left;
      margin-left: 7px;
    a img {
    a:link {
      text-decoration: none;
    a:hover, a:active, a:focus {
      text-decoration: none;
    .container {
      width: 1000px;
      background-color: #CCCCCC;
      margin: auto;
      height: 100%;
    header {
      background-color: #999999;
      height: 150px;
      background-image: url(../images/plaid_banner.png);
      clear: inherit;
    nav p a{
      color: #FFF;
        display: inline-block;
        -webkit-transition: 0.5s;
        -moz-transition: 0.5s;
        -o-transition: 0.5s;
        -ms-transition: 0.5s;
        transition: 0.5s;
    nav p a:hover {
      -webkit-transform: scale(1.125,1.125);
      -moz-transform: scale(1.125,1.125);
      -o-transform: scale(1.125,1.125);
      -ms-transform: scale(1.125,1.125);
      transform: scale(1.125,1.125);
      font-size: 100%;
    .sidebar1 {
      width: 187px;
      background-color: #333;
      padding-bottom: 10px;
      height: 100%;
      background-image: url(../images/sidebar1.png);
      background-repeat: repeat-y;
      position: absolute;
      display: marker;
    .sidebar1 a {
      color: #FFF;
      -webkit-transition: 0.3s;
        -moz-transition: 0.s;
      -o-transition: 0.3s;
      -ms-transition: 0.3s;
      transition: 0.3s;
    .sidebar1 a:hover {
      -webkit-transform: scale(1,1.3);
      -moz-transform: scale(1,1.3);
      -o-transform: scale(1,1.3);
      -ms-transform: scale(1,1.3);
      transform: scale(1,1.3);
      font-size: 120%;
      transition: 0.1s;
    nav p {
      /* [disabled]padding-top: 5px; */
      padding-bottom: 13px;
      font-weight: normal;
      height: 40px;
    .container nav p {
      background-color: #666;
      text-align: right;
      width: auto;
      font-weight: normal;
      color: #fff;
      background-image: url(../images/plaid_banner.png);
      font-size: 120%;
    .button {
      background-color: #666666;
      border: 2px solid #0CF;
      border-radius: 8px;
      width: 180px;
      font-size: 120%;
      margin-bottom: 5px;
      text-align: left;
    .aboutme {
      background-color: #666666;
      text-align: center;
      border: 2px solid #0CF;
      border-radius: 8px;
      padding: 3px 12px;
      margin: 0 15px 0 0;
    .home {
      background-color: #666666;
      text-align: center;
      border: 2px solid #0CF;
      border-radius: 8px;
      padding: 3px 28px;
      margin: 0 15px 0 0;
    .content {
      padding: 10px 0;
      width: auto;
      margin-left: 186px;
      height: 100%;
      background-color: #FFF;
    .content ul, .content ol {
      padding: 0 15px 15px 40px;
      height: 100%;
    ul.nav {
      margin: 10px 0 5px 0;
    ul.nav li {
    ul.nav a, ul.nav a:visited {
      padding: 6px 0px 6px;
      display: block;
      width: 160px;
      text-decoration: none;
      background-color: #CCCCCC;
      color: #FFFFFF;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus {
      background-color: #666666;
      color: #FFF
    footer {
      position: relative;
      font-size: 90%;
      width: 1000px;
      font-weight: normal;
      font-weight: normal;
      bottom: 0px;
    footer p  {
      float: none;
    .socialnetwork {
      float: right;
    .container .socialnetwork {
      margin-right: 7px;
      margin-top: -5px;
    .container footer p {
      font-size: 90%;
      background-image: url(../images/Untitled-1.png);
      text-align: left;
      width: auto;
      color: #0CF;
      padding-top: 10px;
      padding-bottom: 10px;
      padding-left: 10px;
    .container footer nav p {
      background-color: #666;
      text-align: right;
      width: auto;
      font-weight: normal;
      color: #fff;
      background-image: url(../images/Untitled-1.png);
      font-size: 120%;
    header, section, footer, aside, article, figure {
      display: block;
    <!--Gallery CSS Here-->
    @import url('http://fonts.googleapis.com/css?family=Lato');
      margin: 0;
      padding: 0;
      box-sizing: border-box;
    .gallery {
      width: 795px;
      margin: 0 auto;
      padding: 5px 0px 5px 5px;
      background: #333;
    .gallery > div {
      position: relative;
      float: left;
      padding: 5px;
    .gallery > div > img {
      width: 250px;
      transition: .1s transform;
      transform: translateZ(0); /* hack */
    .gallery > div:hover {
      z-index: 1;
    .gallery > div:hover > img {
      transform: scale(1.5,1.5);
      transition: .3s transform;
    .cf:before, .cf:after {
        display: table;
        content: "";
        line-height: 0;
    .cf:after {
        clear: both;
    h1 {
      font-size: 24px;
      font-family: "Arial Rounded MT Bold", Arial, Helvetica, sans-serif;
      float: none;
      color: #000;
      text-align: center;
    <!--End Gallery CSS-->
    </style>
    <link href="../SpryAssets/SpryMenuBarVertical.css" rel="stylesheet" type="text/css">
    <!-- TemplateBeginEditable name="head" -->
    <script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    </head>
    <body class="container">
        <header>
          <h3><img src="../images/GP_3.png" alt="" name="Logo" width="950" height="140"></h3>
    </header>
      <nav>
        <p class="container"><a href="#" class="home">Home</a> <a href="#" class="aboutme"> About Me</a> <a href="#" class="aboutme">Contact Me</a></p>
      </nav>
    <aside>
        <div class="sidebar1"><!-- TemplateBeginEditable name="Sidebar"-->
        <ul id="MenuBar1" class="MenuBarVertical">
            <li><a href="#">Home</a></li>
            <li><a href="#">Gallery</a>        </li>
            <li><a href="#">Websites</a></li>
            <li><a class="MenuBarItemSubmenu" href="#">R&eacute;sum&eacute;</a>
        <ul>
        <li><a href="#">R&eacute;sum&eacute;</a></li>
            <li><a href="#">Cerifications</a></li>
        </ul>
            </li>
            <li><a href="#" class="MenuBarItemSubmenu">About Me</a>
         <ul>
            <li><a href="#">About Me</a></li>
            <li><a href="#">Contact</a></li>
         </ul>
            </li>
        </ul>
        <!-- TemplateEndEditable -->
          <aside> </aside>
          <p style="font-size:90%"></p>
        </div>
    </aside>
      <!-- TemplateBeginEditable name="Main" -->
      <article class="content">
        <h1 class="stars">Add heading here</h1>
        <section>
          <h2>Add subheading here</h2>
          <p>Add content here</p>
        </section>
        <section></section>
      </article>
      <!-- TemplateEndEditable -->
      <footer>
        <p class="container">Copyright 2014 G.Powell.Portfolio. All rights reserved.<a href="../www.facebook.com"><img src="../images/Social Site Logos/Facebook_Logo.png" alt="Facebook" name="Sidebar" width="25" height="25" class="socialnetwork"></a>
        <a href="../www.twitter.com"><img src="../images/Social Site Logos/twitter_logo.png" alt="Twitter" name="Sidebar" width="25" height="25" class="socialnetwork"></a>
        <a href="../www.instagram.com"><img src="../images/Social Site Logos/Instagram_logo.png" alt="Instagram" name="Sidebar" width="25" height="25" class="socialnetwork"></a>
        <a href="../www.plus.google.com"><img src="../images/Social Site Logos/Google_Plus_Logo.png" alt="Google Plus" name="Sidebar" width="25" height="25" class="socialnetwork"></a></p>
      </footer>
    </div>
              <script type="text/javascript">
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
    </script>
    </body>
    </html>

  • TemplateBeginEditable tag inside editable region

    A weird issue...
    I created a template for my asp files.. All goes fine until I
    try to add a specific editable region in my code. I just do not see
    why I get the error "TemplateBeginEditable tag inside editable
    region" on this when I add this on line 6 ("PANA")...
    Anyone an idea why I get this error?

    Yes. Your coding is completely wrong.
    This markup -
    <!-- TemplateBeginEditable name="PANA" -->
    and this markup -
    <!-- TemplateEndEditable -->
    CANNOT go above the doctype.
    Why is it there at all?
    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
    ==================
    "worldofrugs" <[email protected]> wrote in
    message
    news:g11cad$8fq$[email protected]..
    >A weird issue...
    > I created a template for my asp files.. All goes fine
    until I try to add a
    > specific editable region in my code. I just do not see
    why I get the error
    > "TemplateBeginEditable tag inside editable region" on
    this when I add this
    > on
    > line 6 ("PANA")...
    >
    > Anyone an idea why I get this error?
    >
    >
    > <% response.Buffer=true %>
    > <!--#include file="A.asp"-->
    > <!--#include file="B.asp"-->
    > <!--#include file="C.asp"-->
    > <!--#include file="D.asp" -->
    > <!-- TemplateBeginEditable name="PANA" -->
    > <%
    > on error resume next
    > '*******************************
    > ' Page Name
    > '*******************************
    > Dim StrPageName
    > StrPageName = "test.asp"
    > %>
    > <!-- TemplateEndEditable -->
    >
    >
    > <!--#include file="StartSession.asp"-->
    > <%
    > Dim query, conntemp, rs, rstemp
    > call openDb()
    > %>
    > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
    Transitional//EN"
    > "
    http://www.w3.org/TR/html4/loose.dtd">
    > <html>
    > <head>
    >

  • Dreamweaver Template: circle with diagonal line in editable region, but can still edit

    Since upgrading to Dreamweaver CC 2014, for only one of dozens of clients, in a Template, I get a circle with diagonal line in editable region, but I can still edit it, I just can't click to the spot that I want to edit, I have to navigate there with the up down left and right arrows on my keyboard. And, I created a new Template and it didn't happen, until I "got" a file, and now it happens in the new Template too. What's going on?

    Sorry, I'm new here. Do you mean like a screen shot? I just thought maybe somebody had seen this before and would just tell me "you need to uncheck the something or other"

  • 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: <!-- TemplateBeginEditable name="head" > <! TemplateEndEditable --> 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 uneditable regions inside editable regions? [CS5]

    Hello, I am running into a situation where I have a template structure looking like:
    <ul id="outer">
         <li class="nohighlight"><a href="something.html">A page</a>
                     <ul id="inner">
                            <li><a href="other.html">A subpage</a></li>
                     </ul>
         </li>
         <li class="highlight"><a href="something2.html">Another page</a>
                      <ul id="inner2">
                             <li><a href="other2.html">Another  subpage</a></li>
                      </ul>
          </li>
    </ul>
    Now what I would like to do be apply to create new html documents from the template that uses the above structure, and be able to edit the CSS class in the new document. This is easily done by making the (outer) li tags into editable regions. But I would also like to be able to modify/update the "inner" lists in the template file and apply these updates to all files using the template.
    Something like:
    <!-- TemplateBeginEditable name="Navbar1" --><li class="nohighlight"><a href="something.html" >A page </a><!-- TemplateEndEditable -->
                <ul>
                  <li><a href="#">The Hydrological Cycle</a></li>
                </ul>
            </li>
    Does not work as Dreamweaver ends up auto-completing the <li> tag when templates are applied, leaving the document with two </li>.
    Is there a way to make a child tag uneditable and hence to make it update in files when the template is updated, when its parent tag's CSS class remains editable?
    Thanks,
    Ron

    Build your menu with a persistent page indicator and you won't need to change anything on your pages except the body class name.
    I keep my menus in server-side include files and this method works great.
    http://forums.adobe.com/message/2647186#2647186
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists
    http://alt-web.com/
    http://twitter.com/altweb
    http://alt-web-design.blogspot.com/

  • Can't click inside editable region in template based HTML document in CS5

    Hi Everyone,
    I m having a strange problem in Dreamweaver Cs5. After making the html page based on template, when i am opening the HTML page to edit content in editable region, I couldnot click inside the editable region. I can make changes in code view but not in design view in Dreamweaver Cs5.
    Please help if anyone knows the solution. It is really creating a mess for me.
    Thanks,
    Komal

    One of the sites is www.ShelbyVideo.com.
    The code for one of the pages 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"><!-- InstanceBegin template="/Templates/index.dwt" codeOutsideHTMLIsLocked="false" -->
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- InstanceBeginEditable name="doctitle" -->
    <meta name="description" content="SHELBY VIDEO SERVICES: Shelby, NC Video services that are inexpensive, professional, and thorough! Offering corporate and wedding video production services in and around Shelby North Carolina and South Carolina." />
    <meta name="keywords" content="shelby video, shelby videographer, shelby videography, shelby nc video, north carolina shelby video, shelby video camera, shelby videos, north carolina videos, nc video, shelbyvideo, shelbyvideo.com, shelby video production, shelby video services, cleveland county video, cleveland county wedding video" />
    <title>Shelby Video Production Services: SheblyVideo.com offering videography services in the Carolinas.</title><!-- InstanceEndEditable -->
    <link href="css/main.css" rel="stylesheet" type="text/css" media="projection,screen" />
    <!-- InstanceBeginEditable name="head" -->
    <!-- InstanceEndEditable -->
    </head>
    <body class="body">
    <div id="wrapper">
      <div id="header">
        <p><a href="http://www.shelbyvideo.com"><img src="images/shelby-video-logo.jpg" alt="Shelby Video Services" name="weddingVideo" width="216" height="77" border="0" id="weddingVideo" /></a></p>
        <p><a href="index.html">HOME</a>   <a href="shelby-nc-video-services.html">SHELBY VIDEOS</a>   <a href="shelby-video-demos.html">DEMOS</a>   <a href="shelby-video-prices.html">PRICES</a>   <a href="shelby-video-faqs.html">FAQ'S</a>   <a href="shelby-video-north-carolina-reviews-testimonials.html">TESTIMONIES</a>   <a href="shelby-video.html">BOOK US</a></p>
      </div>
      <div id="mainContent"><!-- InstanceBeginEditable name="CONTENT" --><br />
        <h1>ShelbyVideo.com</h1>
        <div id="carolinaWeddingVideoDiv">
          <object width="300" height="182">
              <param name="movie" value="http://www.youtube.com/v/QUSnPSLdnG0&amp;hl=en&amp;fs=1&amp;" />
              </param>
              <param name="allowFullScreen" value="true" />
              </param>
              <param name="allowscriptaccess" value="always" />
              </param>
              <embed src="http://www.youtube.com/v/QUSnPSLdnG0&amp;hl=en&amp;fs=1&amp;" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="300" height="182"></embed>
          </object>
        Shelby Video Demo</div>    <p> </p>
        <p>Welcome to  Shelby Video Services. We have been producing  videos in Shelby North Carolina and South Carolina since 2004. </p>
        <p> </p>
        <p>Your video will be professional and comprehensive. We will beautifully cover your video production in a way that will propell your business into your market and/or enable you to relive your special event over and over and enjoy sharing with others.</p>
        <p> </p>
        <p> </p>
        <p> </p>
      <!-- InstanceEndEditable --></div>
      <div id="footer">© <a href="index.html">Shelby  Video Services</a><br />
      <a href="shelby-nc-video-services.html">shelby nc video services</a> | <a href="shelby-video.html">start here</a> | <a href="shelby-video-demos.html">demos</a> | <a href="links.html">links</a> | <a href="sitemap.html">site map</a> | <a href="shelby-video.html">contact</a> | <a href="shelby-video-north-carolina-reviews-testimonials.html">testimonials</a></div>
    </div>
    <script type="text/javascript">
    var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
    document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
    </script>
    <script type="text/javascript">
    try {
    var pageTracker = _gat._getTracker("UA-9484651-2");
    pageTracker._trackPageview();
    } catch(err) {}</script>
    </body>
    <!-- InstanceEnd --></html>
    Because I didn't create the code, rather it was dreamweaver, i believed that DW is obviously broken. Because I have a bunch of sites I made in earlier versions and when I start using a newer versions, CS5, I now can't access the editable region in any of them it seems DW is broken. So, I didn't think the code was necessary. I thought it was something that others have already experienced and resolved. However, that doesn't seem to be the case. Thanks though for helping with what appears to be broken. Hopefully it's an easy fix because there's other sites I have that this annoyance is plaguing me...

  • Templates in DW CS5.5 and editable regions

    I have a template 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 -->
      <article class="content">
        <h1>BCEF Clubs</h1>
        <section>
    other code goes here
    </section>
    <!-- InstanceEndEditable -->
    Note the </div> tag  after the start of the editable region. This is a proper tag, as it is needed to close the sidebar1 div.
    When it is not in an editable region, the </div> does not show up in yellow in design veiw and it works in every repect.
    When the editable region is introduced, the </div> shows yellow in design view, and it works in every respect.
    It validates using the W3C validation page.
    Pages built with it also show the tag as yellow but they do not display it when live or in a browser.
    If I delete the </div> as dreamweaver suggests, the css breaks and the page will not work.
    It seems that DW thinks that this is an illegal tag. If I click my mouse on the <!-- InstanceBeginEditable name="all" --> tag, and collapse the tag, all the code in the editable region + that in the sidebare 1 div, ( even that before the editable region begins) collapses. The editable region does not allow edits in the sidebar1 code outside the region.
    I need to put the editable region within part of the sidebar 1 div so that I can add aditional floated items in the sidebar 1 div if needed later.
    Is this a bug or am I missing something?

    This would make more sense.
    </nav>
    <!-- InstanceBeginEditable name="sidebar1" -->
    <p>Some unique sidebar1 content goes here</p>
    <!-- InstanceEndEditable -->
    </div><!-- end .sidebar1 -->
    <article class="content">
    <!-- InstanceBeginEditable name="content" -->
    <h1>Unique heading here</h1>
    <section>
    other code
    </section>
    <!-- InstanceEndEditable -->
    </div> <!--end .content-->
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    Message was edited by: Nancy O.  Forgot to close the .content div.

  • Template: Adding Site Wide Code To Editable Region

    I have a template
    I have an editable region called content
    I would now like to add a navigation bar within the editable region, so that it can be managed from the Template and thereon aplies to the child pages
    Q:
    How do I insert a site wide section within an editable region, which is only edited via the template, so that I can set up my navigation bar?
    woolf

    So, here's a sample page: http://www.gravenimagedesign.net/levnav/
    Here's the template code:
    <!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>Untitled Document</title>
    <!-- TemplateEndEditable -->
    <style type="text/css">
    <!--
    #header {
         background-color: #333;
         height: 200px;
         width: 800px;
         position: relative;
         margin: 0 auto;
    #header h1 {
         color: white;
    #content {
         background-color: #FFC;
         height: 500px;
         width: 800px;
         margin: 0 auto;
         border: 1px solid red;
         position: relative;
    #content h1 {
         color: red;
         text-align: center;
    #apDiv1 {
         position:absolute;
         width:663px;
         height:115px;
         z-index:1;
         left: 63px;
         top: 438px;
         background-color: #FCF;
    -->
    </style>
    <script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    </head>
    <body>
         <div id="header"><!--begin header-->
           <h1>This header div is position: relative;</h1>
           <div id="apDiv1">
             <ul id="MenuBar1" class="MenuBarHorizontal">
               <li><a class="MenuBarItemSubmenu" href="#">Item 1</a>
                 <ul>
                   <li><a href="#">Item 1.1</a></li>
                   <li><a href="#">Item 1.2</a></li>
                   <li><a href="#">Item 1.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 2</a></li>
               <li><a class="MenuBarItemSubmenu" href="#">Item 3</a>
                 <ul>
                   <li><a class="MenuBarItemSubmenu" href="#">Item 3.1</a>
                     <ul>
                       <li><a href="#">Item 3.1.1</a></li>
                       <li><a href="#">Item 3.1.2</a></li>
                    </ul>
                  </li>
                   <li><a href="#">Item 3.2</a></li>
                   <li><a href="#">Item 3.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 4</a></li>
            </ul>
             <p><br />
            This menu bar is <strong>position: absolute;</strong></p>
             <p>It is  nested in the code inside the &quot;header&quot; div (the dark grey one), which is positioned &quot;relative.&quot;</p>
          </div>
         </div><!--end header-->
         <div id="content">
           <!--begin content-->
           <!-- TemplateBeginEditable name="EditRegion3" -->
           <h1>This text (really an h1) is appearing within the div with id of "content"</h1>
           <!-- TemplateEndEditable --></div>
         <!--end content-->
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
        </script>
    </body>
    </html>
    And here's a child page:
    <!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"><!-- InstanceBegin template="/Templates/maintemplate.dwt" codeOutsideHTMLIsLocked="false" -->
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- InstanceBeginEditable name="doctitle" -->
    <title>Untitled Document</title>
    <!-- InstanceEndEditable -->
    <style type="text/css">
    <!--
    #header {
         background-color: #333;
         height: 200px;
         width: 800px;
         position: relative;
         margin: 0 auto;
    #header h1 {
         color: white;
    #content {
         background-color: #FFC;
         height: 500px;
         width: 800px;
         margin: 0 auto;
         border: 1px solid red;
         position: relative;
    #content h1 {
         color: red;
         text-align: center;
    #apDiv1 {
         position:absolute;
         width:663px;
         height:115px;
         z-index:1;
         left: 63px;
         top: 438px;
         background-color: #FCF;
    -->
    </style>
    <script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    <!-- InstanceBeginEditable name="head" -->
    <!-- InstanceEndEditable -->
    </head>
    <body>
         <div id="header"><!--begin header-->
           <h1>This header div is position: relative;</h1>
           <div id="apDiv1">
             <ul id="MenuBar1" class="MenuBarHorizontal">
               <li><a class="MenuBarItemSubmenu" href="#">Item 1</a>
                 <ul>
                   <li><a href="#">Item 1.1</a></li>
                   <li><a href="#">Item 1.2</a></li>
                   <li><a href="#">Item 1.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 2</a></li>
               <li><a class="MenuBarItemSubmenu" href="#">Item 3</a>
                 <ul>
                   <li><a class="MenuBarItemSubmenu" href="#">Item 3.1</a>
                     <ul>
                       <li><a href="#">Item 3.1.1</a></li>
                       <li><a href="#">Item 3.1.2</a></li>
                    </ul>
                  </li>
                   <li><a href="#">Item 3.2</a></li>
                   <li><a href="#">Item 3.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 4</a></li>
            </ul>
             <p><br />
            This menu bar is <strong>position: absolute;</strong></p>
             <p>It is  nested in the code inside the &quot;header&quot; div (the dark grey one), which is positioned &quot;relative.&quot;</p>
          </div>
         </div><!--end header-->
         <div id="content">
           <!--begin content-->
           <!-- InstanceBeginEditable name="EditRegion3" -->
           <h1>This text (really an h1) is appearing within the div with id of &quot;content&quot;</h1>
           <!-- InstanceEndEditable --></div>
         <!--end content-->
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
        </script>
    </body>
    <!-- InstanceEnd --></html>
    I arbitrarily positioned the nav in the middle of the action. You can play with its positioning, but remember that it is positioned "absolutely" from the left and top of the "header" div. (in this case)
    If this is unclear, let me know! By the way, the CSS is in the head of the Template, and the child page, but I didn't print out the other auxiliary files, which you will get automatically if you insert a SpryMenuBar. But the sample on my site will work...
    Beth

  • Nested Editable Regions Error Message

    I'm trying to create a dynamic template. I've saved a header
    and footer as library items, and I want to include them in the
    template. In addition I want to have an editable region between
    them. For some reason, when I go to save as template, the error
    message comes up. It says 'error at line 57, column 323(absolute
    position 2998) of ... :nested editable regions' . I have narrowed
    this error to be caused by the header (which was created as a
    sliced image in photoshop), but for what reason I don't know. Any
    ideas why I am getting this error message and what I can do to fix
    it? The template won't save otherwise and I can't find any
    information on dreamweaver 8 help menu.

    There is a parent file and an included file. Here's an
    example -
    The parent file is this -
    <html>
    <head>
    </head>
    <body>
    <!--#include file="foo.html" -->
    </body>
    </html>
    and foo.html (the included file) is this -
    <p>Hello World</p>
    The file you have linked me to is a badly broken template
    page. It's broken
    because the Library items have not been made properly since
    they contain
    redundant <body> tags, CSS, and javascript as well.
    This will never work the way you want, particularly not in
    DW....
    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
    ==================
    "Genius2112" <[email protected]> wrote in
    message
    news:eo41an$93v$[email protected]..
    >
    http://www.lyncourtrec.com/Lyncourt%20Rec%20Website/Pages/Template.dwt.asp
    >
    >
    > Sorry, I'm not quite sure what you meant by "being
    included". The images
    > aren't with the header b/c I didn't adjust their source
    folder since I had
    > to
    > upload it on a different site (I don't have a hosting
    plan for this site
    > yet).
    > Hope this is what you were looking for. Thank you for
    your help.
    >
    >

  • Editable Region Error Message

    I have one DW template (CS3) that gives an error message when
    you try to make a new page using the template: "You have made
    changes to code that is not marked as editable. If you retain those
    changes, they will be lost the next time you apply a template to
    this file. Do you want to retain the changes until then?
    This message appears immediately after you create new page
    from template and save. I can see the cursor in the code view and
    it clearly inside begin editable region tag. I've even crreated an
    alternate template from scratch and am still getting the
    message.

    The error message is likely a red herring. It can be
    triggered by any
    validation error on the page, including in linked CSS files.
    Does the page
    validate?
    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
    ==================
    "hexpix" <[email protected]> wrote in
    message
    news:gqgnak$102$[email protected]..
    >I have one DW template (CS3) that gives an error message
    when you try to
    >make a
    > new page using the template: "You have made changes to
    code that is not
    > marked
    > as editable. If you retain those changes, they will be
    lost the next time
    > you
    > apply a template to this file. Do you want to retain the
    changes until
    > then?
    >
    > This message appears immediately after you create new
    page from template
    > and
    > save. I can see the cursor in the code view and it
    clearly inside begin
    > editable region tag. I've even crreated an alternate
    template from scratch
    > and
    > am still getting the message.
    >

  • 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:
    <!-- TemplateBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
    <!-- TemplateEndEditable -->
    Child Template:
    <!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
         <!-- TemplateBeginEditable name="ChildPageCSSLinks" -->
              Child PAGE CSS Links Here.
         <!-- TemplateEndEditable -->
    <!-- InstanceEndEditable -->
    Child Page:
    Child Template CSS Links Here. (Accurately appearing Un-Editable - {Master-Template's editable region tags accurately appearing invisible})
    <!-- InstanceBeginEditable name="ChildPageCSSLinks" -->
         Child PAGE CSS Links Here. (Accurately appearing Editable)
    <!-- InstanceEndEditable -->
    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:
    <!-- TemplateBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
    <!-- TemplateEndEditable -->
    Child Template:
    <!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
         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.)
    <!-- InstanceEndEditable -->
    Child Page:
    <!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
         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.)
    <!-- InstanceEndEditable -->
    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]

  • How can we add multiple editable region in template

    Hi,
    My issue is when I am going to create a new template I want to add multiple editable region in template and I want to use those editable region per page wise so that in page editor I will add different text for each page for those editable region.
    I can use incontxt editor to change those area for different pages although is it possible to use online editor to add different text for different pages.
    I also have a plan to solve the issue ... that is also not working.
    Plan is .. if we can use tag (not the default one in template), want to use different tag like {tag_headding},{tag_sidebarcontent} in template so that we can use those tag in template and fill the field in the page online editor, so when differnt page we will create we will fill those field for those tag and that will show in the front view of the site.
    Please help me. I am really stuck on this issue.
    Thanks in advance.
    Projjwal

    Hi Projjwal,
    Yes, if you look at many of the commercial BC templates available the way they are getting around it is with Content Holders and multiple templates.
    Now I know you will say that multiple templates is high maintenance ..... not if you use Content holders for both recurring content and unique content.
    Think of Conent Holders as 'Includes' ... I have been doing it this way with templates that I build from scratch as well. Easier than you think.
    And that way the client can change content such as footer information or whatever that appears on all pages without editing the template itself.
    Only drawback is that if you are using Design View in Dreamweaver the content holders don't render. But other than that Content Holders are awesome.
    Brad

  • Child pages inheriting editable regions from template

    I have looked far and wide and cannot find an answer to this problem:
    We recently did a homepage update where the nested and/or second level template (index_template.dwt) was changed. Since much of the formatting was the same - I duplicated the original index_template and made all necessary changes. From this template two child pages were created for our US and UK site. Upon creating the page(s) from the index_template they are inheriting the editable regions, thus not having the ability to update when changes are being made to the template. I have tried multiple ways in an attempt to correct this - but to no avail. Does anyone have a clue how to correct this? As of now I have to manually update all 3 pages.
    BTW I am also a relatively new user who was thrown into managing our company website and pretty much doing a redo on the whole thing. Talk about a learning experience!

    My issue is when you create a page from a template they are not supposed to inherit the editable regions less otherwise marked.
    But that is not true. A newly created child page will inherit ALL content from its template.  But changes to the editable region contents in the template will NOT propagate to existing child pages.
    So, for example, if I want all child pages to have an embedded stylesheet in the head that is EDITABLE, my template would look like this -
    <!-- TemplateBeginEditable name="head" -->
    <style type="text/css">
    </style>
    <!-- TemplateEndEditable -->
    All newly created child pages will then look like this -
    <!-- InstanceBeginEditable name="head" -->
    <style type="text/css">
    </style>
    <!-- InstanceEndEditable -->
    If I then go back to the template and change it like this -
    <!-- TemplateBeginEditable name="head" -->
    <style type="text/css">
    body { margin:0; }
    </style>
    <!-- TemplateEndEditable -->
    that change will NOT propagate to existing child pages, but WILL appear in child pages created subsequently to the save of the template after the change.
    And by the way, it's always been this way.

  • Dreamweaver template to reformat data

    I'm trying to do the following task.
    Write an ezine issue in text format, then applying a
    template, convert it to an html format.
    I'm doing this because I publish a weekly ezine that must go
    out in both formats and was hoping to develop a way to expedite
    this.
    Here's what I've tried:
    - Created an ezine template for the html version with
    editable regions for each section defined by individual table rows.
    - Created a text version which is basically a clean html file
    without any tables consisting of a servies of editable regions that
    correlate to the ones above. I was hoping to apply the above
    template to this one to covert to the html format.
    - The problem shows up during application of new template
    when a location is requested for the body data, which ofcourse is
    the content of the whole document. Selecting one region plops all
    the data into that region.
    So, is there a way to map content from editable regions in
    one document to corresponding regions in another?
    Thanks for any help you can provide.
    Best,
    Steve

    Yes, I think so.
    I made a test page like this -
    <!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" />
    <!-- InstanceBeginEditable name="doctitle"
    --><title>Untitled
    Document</title><!-- InstanceEndEditable -->
    <meta http-equiv="imagetoolbar" content="no" />
    <meta name="MSSmartTagsPreventParsing" content="TRUE"
    />
    <meta name="robots" content="index,follow" />
    <!-- InstanceBeginEditable name="head" --><!--
    InstanceEndEditable -->
    </head>
    <body>
    <p>This is a test</p>
    <!-- InstanceBeginEditable name="EditRegion1"
    --><p>This is a test</p><!--
    InstanceEndEditable -->
    <p>This is a test</p>
    <p>This is a test</p>
    </body>
    </html>
    I have a template page with this in the body -
    <p>Lorem ipsum ...snip... Cras orci. </p>
    <!-- TemplateBeginEditable name="EditRegion1" -->
    <!-- TemplateEndEditable -->
    <p>Curabitur ... snip ... In eget mauris. </p>
    <p>Proin sit amet ... snip... Donec orci. </p>
    I apply the template to the page, and place body into
    EditRegion1, and head
    Nowhere. That seems to work for me.
    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
    ==================
    "davissm777" <[email protected]> wrote in
    message
    news:fpvjd1$6lf$[email protected]..
    > Hi Murray,
    >
    > Yes I know that I can select the respective editable
    regions for each
    > region
    > in the template to place content TO. But the dialogue
    box ask where I want
    > to
    > place the Body content FROM the html file. If I select
    any one of the
    > editable
    > regions in the template, all content goes into the
    region.
    >
    > Am I missing something?
    >
    > thx
    > sd
    >
    >

Maybe you are looking for

  • Printing to the margins

    I noticed in AppleWorks my documents are not printing to the margins allowed by my printer as they are in other programs. Today I again got the warning message that part of my document may be clipped when I knew that the whole thing should fit within

  • Change ipad 2 from AT & T to sprint?

    Does anyone know if my ipad 2 has the 3G AT & t, can I change it to Sprint since they now have ipads?

  • Convert reports 2.5 to 6i

    can i convert reports 2.5 to 6i directly by recompling? thanx Ganpat

  • Disk Drive Not Working After iTunes Update

    Every time i install or update iTunes my computer doesn't read my disk drive. If i put in a disk for music or a game or anything it acts as if its not there. How do i fix this?

  • Fan speed varies 0 - 42 000 !! on K7N2G-ILSR

    Hello people! :D I have MSI K7N2G-ILSR board. I use the on board cpu fan connector for my cpu fan. The problem is this: according to PC-Alert the fan speed varies very much: sometimes PC-Alert says the fan is spinning over 42 000 rpm/min REALLY! and