CS6 - add non-editable region inside editable template region?

I have the following in a template:
    <div class="main-content">
<!-- TemplateBeginEditable name="main-content" -->
      <div class="content p7ehc-1"> <!-- from projectseven.com; don't change -->
        <h1 class="page-topper">Enter topic here</h1>
        <p>Enter content here</p>
      </div>
    <!-- TemplateEndEditable -->
   </div>
Right now everything in main-content is editable. I'd like to add "Page last revised - " at the bottom of the page which would be non-editable. An editable date would follow.
I already have a number of pages with content so any solution should not destroy the content of those pages. (If needed I'd be willing to manually add "Page last revised -" to each of those pages. However, I'd want this to be automatically added for any new pages that were based on the template.)
I have tried putting "Page last revised -" in another div and making it non-editable but this creates other layout problems. I currently don't want to explore this option further.
Thanks for any suggestions.

You could always drop a server-side include or even a Dreamweaver Library item into that editable region (the latter method is a poor second choice, though). Is that a reasonable solution?
Failing that, manually adding Ben's code both to the existing child pages and the current template will definitely place that code into newly created child pages. The beauty of his suggestion is that it's self maintaining, meaning that the code will always show the proper date on each page.

Similar Messages

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

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

  • DWCS3 Template Editable Regions and Editable Attributes?

    Using DWCS3 / WIN XP
    New to DWCS3 and templates AND CSS but I'm managing I
    think....
    QUESTION:
    is there a way to allow the end user to edit the content of
    an editable region and also the attributes of the cell in which the
    editable region resides?
    SITUATION:
    I'm building templates for pages (styled with external CSS)
    that will be editable by the end user via Contribute. I've put
    editable and repeating regions (imgs and navigation menus) in
    particular tds and would like the end user to be able to change the
    color of the background of the cells in which the editable regions
    reside.....
    Of course I get "cannot place an editable region inside an
    editable region" .......understandable...i've read more than a few
    help/tutorial docs......
    So I thought that I should click the tag selector for that td
    and Make Attribute Editable.....
    That's not working either....I know I'm missing something
    because I haven't used DW in years and I'm just not getting some
    big picture logic......
    EXAMPLE: In the .html page attached for viewing, the upper
    left image SRC is in an editable region. I would like the
    background color of the cell it is in to be editable as well. Same
    goes for the background color of the left navigation menu which
    resides in a nested table by the way...........but i still want the
    color to be editable.....
    Thanks so much for any help you can give....
    CoCo
    PAGE based on Template:
    http://www.methods.com/npsbweb/schools/NPSB_school_lev_1.html
    CSS and TEMPLATE CODE: BELOW
    @charset "utf-8";
    p {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 10pt;
    font-weight: normal;
    h1 {
    font-size: 16px;
    color: #999966;
    font-family: "Times New Roman", Times, serif;
    h2 {
    font-size: 18px;
    color: #333366;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    text-align: center;
    margin: 0px;
    h3 {
    font-size: 14px;
    color: #333366;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    h4 {
    font-size: 12pt;
    color: #999966;
    font-family: "Times New Roman", Times, serif;
    text-align: center;
    letter-spacing: 1px;
    margin-top: 0px;
    margin-right: 0px;
    margin-bottom: 5px;
    margin-left: 0px;
    h5 {
    font-size: 12px;
    color: #999966;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    h6 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 8pt;
    color: #333366;
    text-align: center;
    #tdDivideLineTop {
    border-bottom-width: 1px;
    border-bottom-style: solid;
    border-bottom-color: #999966;
    height: 2px;
    #tdMainImgTop {
    text-align: center;
    vertical-align: middle;
    height: 175px;
    border-bottom-width: 1px;
    border-bottom-style: solid;
    border-bottom-color: #D5D5AA;
    background-color: #ffffff;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #D5D5AA;
    #tdTitleRow {
    height: 175px;
    vertical-align: middle;
    border-bottom-width: 1px;
    border-bottom-style: solid;
    border-bottom-color: #D5D5AA;
    #tdRightLineTop {
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #CACAFF;
    #tdMainNavigation {
    display: block;
    font-size: 9pt;
    background-color: #D5D5AA;
    #tdRightNavigation {
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #D5D5AA;
    background-color: #FFFFFF;
    #tdMainNavigation a:link {
    color: #333366;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    margin: 25px;
    padding: 2px;
    display: block;
    border-left-style: solid;
    border-left-width: 1px;
    border-left-color: #333366;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    background-color: #FFFFFF;
    #tdMainNavigation a:visited {
    color: #333366;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    margin: 25px;
    padding: 2px;
    display: block;
    border-left-style: solid;
    border-left-width: 1px;
    border-left-color: #333366;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    background-color: #FFFFFF;
    #tdMainNavigation a:hover {
    color: #FFFFFF;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    display: block;
    margin: 25px;
    padding: 2px;
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #333366;
    background-color: #999966;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    #tdMainNavigation a:active {
    color: #333366;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    display: block;
    margin: 25px;
    padding: 2px;
    font-weight: normal;
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #333366;
    background-color: #D5D5AA;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    #tdRightNavigation a:link {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #999900;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    #tdRightNavigation a:visited {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #999900;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    #tdRightNavigation a:hover {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #333399;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    #tdRightNavigation a:active {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #666633;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    body {
    margin-left: 0px;
    margin-top: 0px;
    margin-right: 0px;
    margin-bottom: 0px;
    a {
    font-size: 10pt;
    color: #333366;
    a:visited {
    color: #330066;
    a:hover {
    color: #999966;
    a:active {
    color: #999900;
    body,td,th {
    font-size: 10pt;

    Using DWCS3 / WIN XP
    New to DWCS3 and templates AND CSS but I'm managing I
    think....
    QUESTION:
    is there a way to allow the end user to edit the content of
    an editable region and also the attributes of the cell in which the
    editable region resides?
    SITUATION:
    I'm building templates for pages (styled with external CSS)
    that will be editable by the end user via Contribute. I've put
    editable and repeating regions (imgs and navigation menus) in
    particular tds and would like the end user to be able to change the
    color of the background of the cells in which the editable regions
    reside.....
    Of course I get "cannot place an editable region inside an
    editable region" .......understandable...i've read more than a few
    help/tutorial docs......
    So I thought that I should click the tag selector for that td
    and Make Attribute Editable.....
    That's not working either....I know I'm missing something
    because I haven't used DW in years and I'm just not getting some
    big picture logic......
    EXAMPLE: In the .html page attached for viewing, the upper
    left image SRC is in an editable region. I would like the
    background color of the cell it is in to be editable as well. Same
    goes for the background color of the left navigation menu which
    resides in a nested table by the way...........but i still want the
    color to be editable.....
    Thanks so much for any help you can give....
    CoCo
    PAGE based on Template:
    http://www.methods.com/npsbweb/schools/NPSB_school_lev_1.html
    CSS and TEMPLATE CODE: BELOW
    @charset "utf-8";
    p {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 10pt;
    font-weight: normal;
    h1 {
    font-size: 16px;
    color: #999966;
    font-family: "Times New Roman", Times, serif;
    h2 {
    font-size: 18px;
    color: #333366;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    text-align: center;
    margin: 0px;
    h3 {
    font-size: 14px;
    color: #333366;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    h4 {
    font-size: 12pt;
    color: #999966;
    font-family: "Times New Roman", Times, serif;
    text-align: center;
    letter-spacing: 1px;
    margin-top: 0px;
    margin-right: 0px;
    margin-bottom: 5px;
    margin-left: 0px;
    h5 {
    font-size: 12px;
    color: #999966;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    h6 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 8pt;
    color: #333366;
    text-align: center;
    #tdDivideLineTop {
    border-bottom-width: 1px;
    border-bottom-style: solid;
    border-bottom-color: #999966;
    height: 2px;
    #tdMainImgTop {
    text-align: center;
    vertical-align: middle;
    height: 175px;
    border-bottom-width: 1px;
    border-bottom-style: solid;
    border-bottom-color: #D5D5AA;
    background-color: #ffffff;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #D5D5AA;
    #tdTitleRow {
    height: 175px;
    vertical-align: middle;
    border-bottom-width: 1px;
    border-bottom-style: solid;
    border-bottom-color: #D5D5AA;
    #tdRightLineTop {
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #CACAFF;
    #tdMainNavigation {
    display: block;
    font-size: 9pt;
    background-color: #D5D5AA;
    #tdRightNavigation {
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #D5D5AA;
    background-color: #FFFFFF;
    #tdMainNavigation a:link {
    color: #333366;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    margin: 25px;
    padding: 2px;
    display: block;
    border-left-style: solid;
    border-left-width: 1px;
    border-left-color: #333366;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    background-color: #FFFFFF;
    #tdMainNavigation a:visited {
    color: #333366;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    margin: 25px;
    padding: 2px;
    display: block;
    border-left-style: solid;
    border-left-width: 1px;
    border-left-color: #333366;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    background-color: #FFFFFF;
    #tdMainNavigation a:hover {
    color: #FFFFFF;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    display: block;
    margin: 25px;
    padding: 2px;
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #333366;
    background-color: #999966;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    #tdMainNavigation a:active {
    color: #333366;
    text-decoration: none;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 9pt;
    text-align: center;
    vertical-align: middle;
    display: block;
    margin: 25px;
    padding: 2px;
    font-weight: normal;
    border-left-width: 1px;
    border-left-style: solid;
    border-left-color: #333366;
    background-color: #D5D5AA;
    border-right-width: 1px;
    border-right-style: solid;
    border-right-color: #333366;
    #tdRightNavigation a:link {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #999900;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    #tdRightNavigation a:visited {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #999900;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    #tdRightNavigation a:hover {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #333399;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    #tdRightNavigation a:active {
    font-family: "Times New Roman", Times, serif;
    font-size: 9pt;
    font-variant: normal;
    color: #666633;
    text-decoration: underline;
    text-align: center;
    display: block;
    margin: 0px;
    letter-spacing: 1px;
    float: none;
    line-height: 22px;
    body {
    margin-left: 0px;
    margin-top: 0px;
    margin-right: 0px;
    margin-bottom: 0px;
    a {
    font-size: 10pt;
    color: #333366;
    a:visited {
    color: #330066;
    a:hover {
    color: #999966;
    a:active {
    color: #999900;
    body,td,th {
    font-size: 10pt;

  • Error adding editable region in nested template Header

    I have a base template for the website (establishing basic
    menus), and a secondary template using that base template, which
    establishes a common table layout for one part of the site. Having
    created the PHP to drive the page, I need to lock down that
    secondary nested region - otherwise any edit I make to my secondary
    &quot;table-defining&quot; template is not passed through
    to the final pages using the secondary template. I have
    successfully created a secondary editable region in each part of
    the &lt;body&gt; area, and sure enough, it locks down text
    outside the secondary editable region just as DW help says it
    should. So far so good.
    Now the problem - I cannot create a region inside the
    &lt;head&gt; editable region to lock down that region too.
    Normally one would want keywords and so on to be variable from page
    to page, but as I am filling variable keywords from a database, it
    makes sense to lock down the &lt;head&gt; too. Does anyone
    know why that generates an error &quot;cannot create an
    optional region here&quot;? Is there anything that can be done
    about it?

    Posts are hard to read when they are all crammed together
    like yours. Try
    making some paragraphs!
    Nevertheless, I think I understand what you are saying., but
    honestly, I
    just wouldn't do it that way. Anymore, my templates are just
    one editable
    region in the body, and a bunch of server-side includes. I
    find nested
    templates much too complex, and troublesome to work with, and
    have really
    never found a scenario where I could do things with them that
    I could not do
    more easily with other methods.
    > However, I have an Editable
    > region with the HTML Head area, and DW does not permit
    me to add a
    > 'secondary-template Editable Region' within it to lock
    it down.
    Is it only you working on the site? Who are you trying to
    'lock down'? If
    it's only you, I'd forget about this. Invariably the things
    like this that
    you think are a good idea come back later to bite you.
    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
    ==================
    "suddensurprise" <[email protected]> wrote
    in message
    news:[email protected]...
    > Murray 'ACE' wanted to understand why I am using nested
    templates.
    >
    Primary
    > Template or 'base layout' I have a primary template
    which establishes
    > the
    > top, left and bottom borders for the site. These contain
    Spry menus - if
    > I
    > change the menu on the primary template, all pages will
    be updated. The
    > primary template has a 'work area box' which is where
    the page content
    > goes for
    > each different page.
    Secondary or 'nested' template Next I have a
    > secondary template, or nested template. It starts with
    the primary
    > template
    > but this time the 'work area box' is set up with a
    product table and
    > various
    > fixed column headings. The table is filled from
    different database
    > records
    > using PHP and MySQL. Therefore the secondary or 'nested'
    template
    > establishes
    > a common format for the product table. For example, a
    change to a heading
    > in
    > the secondary template is updated into all pages using
    it. And to
    > reiterate, a
    > change to the Spry menu bar on the primary template will
    update the
    > secondary
    > template and all pages created from that template.
    Similarly, I have
    > several
    > other secondary templates, all created from the primary
    template, all
    > setting
    > standard sections of the website so that multiple pages
    can be updated at
    > once
    > via a single template change.
    Note: the code in the secondary
    > template
    > needs to be 'locked' so that edits within it are passed
    on to its slave
    > pages.
    > This is done by creating an empty Editable region at the
    beginning of the
    > 'work
    > area box' I talked about.
    Other Approaches? If anyone knows a
    > better
    > way of enabling site edits to be passed consistently
    down into different
    > standard-section blocks of the website, I would welcome
    your input.
    >
    The
    > Problem Now to reiterate the problem with which I
    started this thread.
    > In
    > a secondary template it works fine creating a second
    Editable Region
    > within the
    > Body of the HTML document - the rest of the code in that
    'primary template
    > editable region' is now locked out as is required.
    However, I have an
    > Editable
    > region with the HTML Head area, and DW does not permit
    me to add a
    > 'secondary-template Editable Region' within it to lock
    it down. I am
    > wondering
    > if anyone in the Community knows why or can suggest a
    solution. Regards
    > Richard
    >

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

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

  • Locking editable template regions to Contribute users only

    Hi,
    I would like to know if it's possible to lock some editable
    template regions to Contribute users only? We need to have these
    regions editable through Dreaweaver so our site designers can still
    modify them. I'm not talking about the "Optional region" here, just
    a "regular" editable region.
    Thank you,
    Stéphane Brault

    there's no option to restrict access to contribute users only
    when using Dreamweaver templates.. but a possible dirty workaround
    would be to place those editable regions inside dynamic code (ASP,
    PHP, JSP, etc..) as Contribute won't be able to interpret them..
    they won't be visible in Contribute

  • How to remove Editable region from nested template?

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

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

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

    When I have an Editable Region in a template and want to
    remove it, and from all child-pages, what to do[mx 2004] ? The
    below code if is in logout.php how is get included in a file ?
    I use:
    <!--#include file="../customeradmin/logout_links.php"
    -->
    but isset($_SESSION["email"] does not working .... well ?
    [code]<?php
    if (isset($_SESSION["email"])) {
    ?>
    <link href="/css-styles.css" rel="stylesheet"
    type="text/css"><body class="text_normal">
    <span class="text_normal">LOGGED IN(<a
    class="text_normal"
    href="/php_files/logout.php">Customer-LogOut</a>)</span>  
    <?php
    ?><br />
    <?php
    if (isset($_SESSION["email-affiliates"])) {
    ?>
    LOGGED IN(<a class="text_normal"
    href="/php_files/affout.php">Affiliate-LogOut</a>)
    <?php
    ?>
    [/code]

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

  • Editable template regions

    I made a div with a editable region and the design view shows
    it to be editable but I am not allowed to make padding changes with
    the css for that div. The error msg shows "Making this change would
    require changing code that is locked by a template or a translator.
    The change will be discarded." What am I missing???? The region is
    editable but I can't edit??????????
    I attached the code and it is specifically the div
    "left_column"
    thanks in advance for your time.
    Rich Gilman

    It is your CSS styles that are in a NONeditable region of the
    head, so
    they can not be edited on the Child page. Either move the
    styles to an
    external stylesheet (best), or move them to the "Head"
    editable region
    on the page, or manually create new styles in that editable
    region that
    will over-ride the current ones.
    E. Michael Brandt
    www.divaHTML.com
    divaPOP : standards-compliant popup windows
    divaGPS : you-are-here menu highlighting
    divaFAQ : FAQ pages with pizazz
    www.valleywebdesigns.com/vwd_Vdw.asp
    JustSo PictureWindow
    JustSo PhotoAlbum, et alia

  • How to make metatags "Editable" region in my template?

    How can I make my metatags "editable" regions in my template?
    I tried doing it as shown below . . . but when trying to update the individual pages from the template, I get an error message that looks like its trying to tell me something is missing from the <!-- TemplateBeginEditable -->  instruction.
    Can anyone help?
    I appreciate it!
    <head>
    <!-- TemplateBeginEditable -->
    <meta name="keywords" content="cat, dog, apple, banana">
    <meta name="description" content="My Description will go here.">
    <title>My Title will go here</title>
    <!-- TemplateEndEditable --><!-- InstanceBeginEditable -->
    <title>undefined</title>
    <!-- InstanceEndEditable -->

    Thanks for your response, David
    Well, I've tried to implement your instructions on the template (see below for EXACT code).   But on all the "child" pages, I am ONLY still allowed to edit the "Title" tag.  Everything else is still GRAYED-OUT (unable to edit).
    What did I do wrong?
    - Jim
    <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns="http://www.w3.org/TR/REC-html40">
    <head>
    <!-- TemplateBeginEditable name="head" -->
    <meta name="keywords" content="resume,resume service,resume writer,resume assistance,resume assistant">
    <meta name="description" content="Professionally-written Resumes ready in 60 minutes! Great quality & friendly service.  Just $49.95. Lowest prices! Our 19th year. Work with a real person on the phone. Hassle-free (no forms to fill out like our competition). Guaranteed Job-Winning Resumes. Open 7 days til 12 Midnight.">
    <title>Best c Resumes - Ready in 1 Hour!</title>
    <style>
    <!--
    a            {
    color: #0000FF
    -->
    </style>
    <link rel="File-List" href="../u4/17YUvRBD_files/filelist.xml">
    <meta name="Microsoft Theme" content="blends 011">
    <!-- TemplateEndEditable -->
    </head>

  • Move Editable Template Region Outside Block Tag

    I am trying to insert an editable region into a template. I
    position my cursor, then choose insert/template objects/editable
    region. But when I try to save the page, DW tells me I have placed
    the editable region within a block tag and that users of this
    template will not be able to create new blocks in this region.
    "Move the region outside the block tag if you want users to be able
    to do this."
    OK, but how?

    One easy way -
    Click in the region where you want to insert the editable
    content. Look at
    the Quick tag selector (at the bottom of the document pane).
    Examine a)
    what tag is selected (if any), and b) what tag is shown
    directly left of
    that selected tag. It (b) is a <p>, or <h#> tag,
    then select it instead by
    clicking on it in the Quick tag selector. Now apply your
    editable region -
    INSERT | Template Objects > Editable Region.
    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
    ==================
    "W Vought" <[email protected]> wrote in
    message
    news:fpl9k2$qgg$[email protected]..
    > That did it..thanks.
    >
    > I'm a total noob and it took me a minute to realise that
    I had to go into
    > code
    > view. After a few minutes your instructions started to
    make sense to me.
    >
    > Why is this problem occurring? How can I keep from
    having to adjust this
    > in
    > the future?
    >
    >

  • Repeating Regions and Editable Tag Attributes?

    I want to produce a template that will let users create pages
    that list items as a thumbnail image and a short text description,
    one after the other.
    I can set this up as a repeating region, but I would also
    like to make only certain attributes of the image editable (src and
    alt for example). However, when I use editable tag attributes to do
    this, the image in each repeated region ends up with the same
    attribute values - when I add a new repeat region and then change
    the src tag through the Template Properties dialog,
    all of the images take on the same src value. Looking at the
    code, it looks like the editable instances in each repeated region
    get the same name, and so I can see that DW will get confused.
    Is this a limitation in DW? Is there a work around anyone can
    suggest?
    TIA

    So, you have some number of people who are editing the child
    pages and you
    want to constrain their editing choices? Are you using
    Contribute?
    Anyhow, I am not aware of any convenient way you can do
    something like this
    using DW's Template features.
    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
    ==================
    "manicbananic" <[email protected]> wrote in
    message
    news:g7pimq$fvg$[email protected]..
    >I want to produce a template that will let users create
    pages that list
    >items
    > as a thumbnail image and a short text description, one
    after the other.
    >
    > I can set this up as a repeating region, but I would
    also like to make
    > only
    > certain attributes of the image editable (src and alt
    for example).
    > However,
    > when I use editable tag attributes to do this, the image
    in each repeated
    > region ends up with the same attribute values - when I
    add a new repeat
    > region
    > and then change the src tag through the Template
    Properties dialog,
    >
    all
    > of the images take on the same src value. Looking at the
    code, it looks
    > like
    > the editable instances in each repeated region get the
    same name, and so I
    > can
    > see that DW will get confused.
    >
    > Is this a limitation in DW? Is there a work around
    anyone can suggest?
    >
    > TIA
    >

Maybe you are looking for

  • REP-1401: FATAL PL/SQL ERROR OCCUARED

    I make below in function in report builder,give me fatal pl/sql error i can`t handle it please any tips function CF_PERF_COMENTFormula return Number is V_VALUE_COMMENT_EMP VARCHAR2(2000); V_VALUE_PERF_ID_EMP NUMBER(15); V_VALUE_PERF_NAME_EMP VARCHAR2

  • Archive logs are increasing please help

    Hi, i have a serious problem, iasdb- that portal is installed on- version 10.3.0.1 and its continuosly writing logs, every 15-16 seconds and eats disk space . any one have the similar experience - continuosly written archive logs, please help me. i c

  • Javascript issues

    I guess this subject has been address before but I can`t solve the problem. when I login to a some sites that requires user id and password all i get is a blank page. This is in all browsers. or if I write any javascript it will not be displayed. (Al

  • CS2 Illustrator Problem

    I will be working on a project in ai SC2, go to save my work and the program just goes off, turns off with out saving anything I have done up to that point. I try to save my work ever 10 mins. or so but it is a pain having to go back and re-do everth

  • Access font information of subreport objects?

    If I want to programmatically access font information of a subreport element in a report, is there any way to do this - either with the RAS or the older CrystalReports.Engine API? Only TextObjects, FieldObjects, and ParagraphElements seem to have a F