After inserting editable regions, DW CS3 tells me none exist...?

I am having muliple problems with templates on this particular project, that I have never seen before. I was going to break them into multiple
questions, per the instructions here at the forum, but all of these relate to the same template code, which I will post below, so I think it would be
more efficient to include the related questions in this thread.
Background
I created this template by first scraping the client's existing site, which is a dynamic CMS site, with HTTrack. Secondly, I opened the HTML file generated by that processs, and saved it as a template in my DW project, which automatically assigned it to the "Templates" folder, and is accessable via the "Assets" panel (usual stuff.)
The reason for starting with a scraped version of existing is that this project involves moving the site off of the CMS platform and into HTML/CMS, yet preserving essentially the same design.
1. The most obvious problem I have is that in the subject line: after adding a couple of editable regions to my template,
when I save/preview, an error message comes up saying "your template has no editable regions, do you want to proceed?"
2. In doing the save as template operation, I am prompted with "Update links?" and I do. When I open the template, all looks good in DW, however as soon as I do a preview, I get a completely raw html page with NO css styling, no images, no fonts, etc.  Conversely, if I do the same step, yet choose not to update links when prompted, then I get a template that looks completely bare in DW (no styling, no images, etc.) yet looks fine when previewed...?
Additionally, one other thing I tried was doing the save as template, choosing not to update links, and then moving it out of the templates folder into the main project folder - Here, it both looks fine in DW, and previews, yet I am unable to use it as a template (does not appear in assets, cannot use "create new from" or "apply", etc.)
I have also tried changing from "site root" to "document" in terms of linking, yet nothing has worked. Every time I have created a template on other projects, all has just worked fine from the start, so I am really stumped here.
The project will have too many pages to not use a template for updates, so I am hopeful that I can figure out what is causing this. Following is my 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 profile="http://gmpg.org/xfn/11">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<!-- TemplateBeginEditable name="HEAD TAGS" -->
<title>Home | Records Management Center</title>
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
<base href="http://records-storage.biz/RMCAugusta/">
<meta name="robots" content="all" />
<meta name="description" content="records management center augusta's choice for data storage, records management, document shredding.">
<meta name="keywords" content="augusta, data, storage, records, management, document, shredding, center">
<!-- TemplateEndEditable -->
<link rel="stylesheet" type="text/css" href="../include/scripts/css/screen.css" />
<!--[if IE 6]> <link href="/include/scripts/css/ie6.css" rel="stylesheet" type="text/css" /> <![endif]-->
<!--[if IE 7]> <link href="/Include/Scripts/css/ie7.css" rel="stylesheet" type="text/css" /> <![endif]-->
  <script language="JavaScript">
  <!--
     img = new Array(70);
     for (i = 0; i < 70; i++)
          img[i] = new Image;
     img[0].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/add.gif';
     img[1].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/add_f2.gif';
     img[2].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/add1.gif';
     img[3].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/add1_f2.gif';
     img[4].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/addcontent.gif';
     img[5].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/addcontent_f2.gif';
     img[6].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/addfeedback.gif';
     img[7].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/addfeedback_f2.gif';
     img[8].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/addforum.gif';
     img[9].src  = 'http://www.recordsmanagementcenter.com/common/images/admin/addforum_f2.gif';
     img[10].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addhotlist.gif';
     img[11].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addhotlist_f2.gif';
     img[12].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addnavlist.gif';
     img[13].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addnavlist_f2.gif';
     img[14].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addpage.gif';
     img[15].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addpage_f2.gif';
     img[16].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsection.gif';
     img[17].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsection_f2.gif';
     img[18].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addup.gif';
     img[19].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addup_f2.gif';
     img[20].src = 'http://www.recordsmanagementcenter.com/common/images/admin/adsection.gif';
     img[21].src = 'http://www.recordsmanagementcenter.com/common/images/admin/adsection_f2.gif';
     img[22].src = 'http://www.recordsmanagementcenter.com/common/images/admin/content.gif';
     img[23].src = 'http://www.recordsmanagementcenter.com/common/images/admin/content_f2.gif';
     img[24].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit.gif';
     img[25].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit_f2.gif';
     img[26].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit1.gif';
     img[27].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit1_f2.gif';
     img[28].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editcontent.gif';
     img[29].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editcontent_f2.gif';
     img[30].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editfeedback.gif';
     img[31].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editfeedback_f2.gif';
     img[32].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editforum.gif';
     img[33].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editforum_f2.gif';
     img[34].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edithotlist.gif';
     img[35].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edithotlist_f2.gif';
     img[36].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editnavlist.gif';
     img[37].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editnavlist_f2.gif';
     img[38].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editpage.gif';
     img[39].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editpage_f2.gif';
     img[40].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection.gif';
     img[41].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection_f2.gif';
     img[42].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection1.gif';
     img[43].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection1_f2.gif';
     img[44].src = 'http://www.recordsmanagementcenter.com/common/images/admin/feedback.gif';
     img[45].src = 'http://www.recordsmanagementcenter.com/common/images/admin/feedback_f2.gif';
     img[46].src = 'http://www.recordsmanagementcenter.com/common/images/admin/forums.gif';
     img[47].src = 'http://www.recordsmanagementcenter.com/common/images/admin/forums_f2.gif';
     img[48].src = 'http://www.recordsmanagementcenter.com/common/images/admin/hotlists.gif';
     img[49].src = 'http://www.recordsmanagementcenter.com/common/images/admin/hotlists_f2.gif';
     img[50].src = 'http://www.recordsmanagementcenter.com/common/images/admin/navlists.gif';
     img[51].src = 'http://www.recordsmanagementcenter.com/common/images/admin/navlists_f2.gif';
     img[52].src = 'http://www.recordsmanagementcenter.com/common/images/admin/pages.gif';
     img[53].src = 'http://www.recordsmanagementcenter.com/common/images/admin/pages_f2.gif';
     img[54].src = 'http://www.recordsmanagementcenter.com/common/images/admin/questions.gif';
     img[55].src = 'http://www.recordsmanagementcenter.com/common/images/admin/questions_f2.gif';
     img[56].src = 'http://www.recordsmanagementcenter.com/common/images/admin/resources.gif';
     img[57].src = 'http://www.recordsmanagementcenter.com/common/images/admin/resources_f2.gif';
     img[57].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsup.gif';
     img[58].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsup_f2.gif';
     img[59].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsdn.gif';
     img[60].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsdn_f2.gif';
     img[61].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsup.gif';
     img[62].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsup_f2.gif';
     img[63].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsdn.gif';
     img[64].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsdn_f2.gif';
     function gfAdminOver(img)
     {          window.event.srcElement.src = "/common/images/admin/" + img + "_f2.gif";
     function gfAdminOut(img)
          window.event.srcElement.src = "/common/images/admin/" + img + ".gif";
     function gfGoAdmin(url)
          window.location = url;
     function poppoll(dest, ff)
          var d = document;
          var ans, ii, jj, pname;
          ans = 0;
          dest = dest + "&FEEDBACK=" + d.frm["feedback_" + ff].value;
          dest = dest + "&SQ=" + d.frm["startq_" + ff].value;
          dest = dest + "&EQ=" + d.frm["endq_" + ff].value;
          dest = dest + "&SN=" + d.frm["startn_" + ff].value;
          dest = dest + "&EN=" + d.frm["endn_" + ff].value;
          pname = "";
          for (ii = 0; ii < d.frm.length; ii++)
               if (d.frm[ii].name.substr(0,7) == "pinput_")
                    ans = "";
                    if ((d.frm[ii].type == "radio") || (d.frm[ii].type == "checkbox"))
                         if (d.frm[ii].checked)
                              ans = d.frm[ii].value;
                    else
                         ans = d.frm[ii].value;
                    if (ans != "")
                         if (d.frm[ii].name == pname)
                              dest = dest + "|" + ans;
                         else
                              dest = dest + "&" + d.frm[ii].name + "=" + ans;
                         pname = d.frm[ii].name;
          popup(dest);
     function gfClick(dest)
          window.location = dest;
     function gfNavOver()
     {          window.event.srcElement.style.cursor = "hand";
     function gfNavOut()
          window.event.srcElement.style.cursor = "default";
     function gfNavImg(fld,img)
          if (document.images)
               document[fld].src = img;
     function gfNewStyle(sid)
          var i;
          for (i = 0; i < document.styleSheets.length - 1; i++)
               document.styleSheets[i].disabled = ! (document.styleSheets[i].id == sid);
function popup(dest)
     window.open(dest,null,"width=800,height=600,location=no,menubar,toolbar,scrollbars,resizable,top=0,left=0");
     function popupres(dest,wi,ht)
          window.open(dest,null,"width=" + wi + ",height=" + ht + ",location=no,menubar,toolbar,scrollbars,resizable,top=0,left=0");
CSInit = new Array;
function CSScriptInit() {
if(typeof(skipPage) != "undefined") { if(skipPage) return; }
idxArray = new Array;
for(var i=0;i<CSInit.length;i++)
     idxArray[i] = i;
CSAction2(CSInit, idxArray);}
CSAg = window.navigator.userAgent; CSBVers = parseInt(CSAg.charAt(CSAg.indexOf("index.html")+1),10);
function IsIE() { return CSAg.indexOf("MSIE") > 0;}
function CSIEStyl(s) { return document.all.tags("div")[s].style; }
function CSNSStyl(s) { return CSFindElement(s,0); }
function CSFindElement(n,ly) { if (CSBVers < 4) return document[n];
     var curDoc = ly ? ly.document : document; var elem = curDoc[n];
     if (!elem) { for (var i=0;i<curDoc.layers.length;i++) {
          elem = CSFindElement(n,curDoc.layers[i]); if (elem) return elem; }}
     return elem;
function CSClickReturn () {
     var bAgent = window.navigator.userAgent; 
     var bAppName = window.navigator.appName;
     if ((bAppName.indexOf("Explorer") >= 0) && (bAgent.indexOf("Mozilla/3") >= 0) && (bAgent.indexOf("Mac") >= 0))
          return true; // dont follow link
     else return false; // dont follow link
function CSButtonReturn () {
     var bAgent = window.navigator.userAgent; 
     var bAppName = window.navigator.appName;
     if ((bAppName.indexOf("Explorer") >= 0) && (bAgent.indexOf("Mozilla/3") >= 0) && (bAgent.indexOf("Mac") >= 0))
          return false; // follow link
     else return true; // follow link
CSIm = new Object();
function CSIShow(n,i) {
     if (document.images) {
          if (CSIm[n]) {
               var img = (!IsIE()) ? CSFindElement(n,0) : document[n];
               if (img && typeof(CSIm[n][i].src) != "undefined") {img.src = CSIm[n][i].src;}
               if(i != 0)
                    self.status = CSIm[n][3];
               else
                    self.status = " ";
               return true;
     return false;
function CSILoad(action) {
     im = action[1];
     if (document.images) {
          CSIm[im] = new Object();
          for (var i=2;i<5;i++) {
               if (action[i] != '') { CSIm[im][i-2] = new Image(); CSIm[im][i-2].src = action[i]; }
               else CSIm[im][i-2] = 0;
          CSIm[im][3] = action[5];
CSStopExecution = false;
function CSAction(array) {
     return CSAction2(CSAct, array);
function CSAction2(fct, array) { 
     var result;
     for (var i=0;i<array.length;i++) {
          if(CSStopExecution) return false;
          var actArray = fct[array[i]];
          if (actArray == null) return false;
          var tempArray = new Array;
          for(var j=1;j<actArray.length;j++) {
               if((actArray[j] != null) && (typeof(actArray[j]) == "object") && (actArray[j].length == 2)) {
                    if(actArray[j][0] == "VAR") {
                         tempArray[j] = CSStateArray[actArray[j][1]];
                    else {
                         if(actArray[j][0] == "ACT") {
                              tempArray[j] = CSAction(new Array(new String(actArray[j][1])));
                    else
                         tempArray[j] = actArray[j];
               else
                    tempArray[j] = actArray[j];
          result = actArray[0](tempArray);
     return result;
CSAct = new Object;
  // -->
  </script>
<script type="text/javascript" src="../include/scripts/jquery/jquery1.2.6.js"></script>
<link rel="stylesheet" type="text/css" href="../include/scripts/superfish/superfish.css" media="screen">
<script type="text/javascript" src="../include/scripts/superfish/superfish.js"></script>
<script type="text/javascript" src="../include/scripts/superfish/hoverIntent.js"></script>
<script type="text/javascript" src="../include/scripts/jquery/site.js"></script>
<script language="Javascript" src="../include/scripts/rotate.js"></script>
<link href="/RMCAugusta/common/wsaglobal.css" rel="stylesheet" type="text/css" />
</head>
<!-- TemplateBeginEditable name="BODY" -->
<body>
<div id="container">
<div id="header">
<h1>
<a class="logo" href="../index.html" title="Home Page">
<img src="../images/RMC-logo.gif" alt="Home Page" /></a>
</h1>
<div id="supernav">
<a href="../index.html" title="Go Home">Home</a> |
<a href="#" title="FAQ">FAQ</a> | 
<a href="../common/feedback_footerc73a.html?PAGE=355" title="Contact RMC">Contact Us</a> |
<a href="../common/contentff2a.html?PAGE=353" title="Client Login">Login</a> |
</div>
<div id="searchsite">
<form action="http://www.recordsmanagementcenter.com/common/textsearch-std.asp?PAGE=375" method="post" id="Search" title="Search">
<input type="text" name="i_search" class="searchbox" value="Search Site..."
onfocus="if (this.value == 'Search Site...') {this.value = '';}"
onblur="if (this.value == '') {this.value = 'Search Site...';}" />
<input type="submit" class="submit" alt="Submit" value="Search" />
</form>
<div class="clear"></div>
</div>
<div class="clear"></div>
</div>
<div id="topnav">
<ul  id="menu" class="sf-menu">     
     <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/contentd618.html?PAGE=350">About RMC</a>
       <ul >
        <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content9a68.html?PAGE=356">Customer Bill of Rights</a></li>
          <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content0864.html?PAGE=369">My Three Point Pledge</a></li>
          <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content1f72.html?PAGE=363">Testimonials</a></li>
          <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content3fb4.html?PAGE=364">Our Facility</a></li>
        <li><a href="#">Newsletter</a></li>     
        <li><a href="#">Special Offer</a></li>     
     </ul>
</li>
     <li><a href="#">Records Managment</a>
      <ul>
      <li><a href="#">Records Storage</a></li>
      <li><a href="#">File Storage</a></li>
      <li><a href="#">File Indexing</a></li>
      <li><a href="#">Storage & Delivery Process</a></li>
      <li><a href="#">Barcode Tracking </a></li>
      <li><a href="#">File Restoration</a></li>
      <li><a href="#">Dedicated Vault Storage</a></li>
      <li><a href="#">Supplies</a></li>          
     </ul>
</li>
     <li><a href="#">Document Imaging Solutions</a>
      <ul >
       <li><a href="#">Service Bureau</a></li>
       <li><a href="#">Scan On Demand</a></li>
       <li><a href="#">Data Silo</a></li>                    
      </ul>
    </li>
    <li><a href="#">Shredding & Destruction</a>
     <ul >
       <li><a href="#">Shredding Process</a></li>
       <li><a href="#">Drop Off Shred</a></li>
       <li><a href="#">One Time Purges</a></li>
       <li><a href="#">Media Destruction</a></li>
       <li><a href="#">Collection Containers</a></li>                         
      </ul>
   </li>
    <li><a href="#">Data Backup</a>
     <ul >
       <li><a href="#">Tape Vaulting</a></li>
       <li><a href="#">Electronic Vaulting</a></li>
      </ul>
   </li>
   <li><a href="#">Info Management 101</a>
     <ul >
       <li><a href="#">Special Info Kit</a></li>
       <li><a href="#">Storage Options</a></li>
       <li><a href="#">How To Choose</a></li>
       <li><a href="#">Storage Tips</a></li>
       <li><a href="#">Retention Guide</a></li>                         
      </ul>
   </li>
   </ul>
    <div class="clear"></div>
</div>
<div id="slideshow">
<script language="JavaScript">
//new fadeshow(IMAGES_ARRAY_NAME, slideshow_width, slideshow_height, borderwidth, delay, pause (0=no, 1=yes), optionalRandomOrder)
new fadeshow(fadeimages, 632, 258, 0, 4000, 0)
</script>
</div>
<div id="page">
<div class="tophome">
<div class="bot">
<div id="contenthome">
<table border="0" cellpadding="0" cellspacing="5" width="100%">
     <tr>
          <td valign="top">
               <table border="0" cellpadding="0" cellspacing="0" width="100%">
                    <tr>
                         <td valign="top" width="">
<!-- gfShowAllContent(137,) -->
<a name="1"></a>
<!-- gfShowOther(137,130,) -->
<h1>Welcome to <b>Records Management Center</b></h1>
<table width="100%" border="0" cellpadding="0" cellspacing="0"><tr><td valign="top" align="Left" class="text">We know you have many options when it comes to storing your organization's records and information. You may choose to store them on-site in your own storeroom, in a mini-storage (self storage) unit, with a moving and storage company or with a full-service records management company like Records Management Center. There are, however, major differences not only in the storage options available, but in the companies that provide them as well. Please take some time to review our website and familiarize yourself with your records management options, so that you can make the choice that's right for your organization.</td>
</tr></table>
<table width="100%" border="0" cellpadding="0" cellspacing="0"><tr><td valign="top" align="Left" class="h2">About Us</td>
</tr></table>
<table width="100%" border="0" cellpadding="0" cellspacing="0"><tr><td valign="top" align="Left" class="text">Records Management Center was established in 1985 as a full-service records management company providing document storage, digital imaging, media storage and shredding services to the Central Savannah River Area.<br />
<br />
We protect businesses and their customers by securing their confidential information and helping them comply with HIPAA, GLB and FACTA, as well as all state and federal information management and destruction laws.</td>
</tr></table>
<!-- End gfShowOther(137,130,) -->
<!-- End gfShowAllContent(137,) -->                         </td>
                    </tr>
               </table>          </td>
     </tr>
</table>
</div>
<div class="clear"></div>
<div id="specials">
<div class="top">
<div class="quote">
<a href="../common/feedback_footerc73a.html?PAGE=355" title="Get A Quote"> </a></div>
<div class="info">
<a href="../common/content371a.html?PAGE=373" title="Free Information Kit"> </a></div>
<div class="days">
<a href="../common/content371a.html?PAGE=373" title="30 Days of Free Shredding"> </a></div>
<div id="newsletter">
<h3>Sign up for our<br /><span class="caps">Free Newsletter</span></h3>
<form action="http://www.recordsmanagementcenter.com/common/feedback_footer.asp?PAGE=374" method="post" id="Search" title="Sign Up">
<input type="text" name="input_2" class="searchbox" value="Email Address"
onfocus="if (this.value == 'Email Address') {this.value = '';}"
onblur="if (this.value == '') {this.value = 'Email Address';}" />
<input name="Sign up" type="submit" class="submit" alt="Sign Up" value="Sign Up" />
</form>
<div class="clear"></div>
</div>
</div>
<div class="bot"> </div>
</div>
<div id="boxes">
<div class="records">
<a href="../common/content5697.html?PAGE=331" title="Records Management"> </a></div>
<div class="imaging">
<a href="../common/content9e28.html?PAGE=61" title="Digital Imaging"> </a></div>
<div class="storage">
<a href="../common/content7f9f.html?PAGE=333" title="Computer Media Storage"> </a></div>
<div class="shredding">
<a href="../common/content1cd1.html?PAGE=296" title="Secure Shredding"> </a></div>
<div class="clear"></div>
</div>
</div>
</div>
<div class="clear"></div>
</div>
<div id="footer">
<div id="links">
<a href="#">Terms and Conditions</a> |
<a href="#">Privacy</a></div>
<div id="copyright">
&copy; 2009 Records Management Center.<br />
A Division of RBW Logistics Corporation<br />
Powered by <a href="http://www.powerserve.net/">PowerServe</a><br />
<a href="http://www.rbwlogistics.com/"><img src="../images/logo-footer.gif" /></a>
</div>
</div>
</div>
<script language="JavaScript" type="text/javascript" src="/NoIEActivate.js"></script><script src="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-159577-28";
urchinTracker();
</script>
<!-- TemplateEndEditable -->
</body>
<!-- Mirrored from www.recordsmanagementcenter.com/ by HTTrack Website Copier/3.x [XR&CO'2008], Tue, 18 Aug 2009 14:14:38 GMT -->
</html>

There are (or can be), of course, editable regions in the head of a document. Typically, around the <title></title> you will find 'space' to put links etc, and meta tags:
<!-- InstanceBeginEditable name="doctitle" -->
<title> Your title here </title>
<meta name="description" content="Description here." />
<meta name="keywords" content="keywords here " />
<meta name="robots" content="index,follow" />
<!-- InstanceEndEditable -->
Further down in this same document, I find:
<!-- InstanceBeginEditable name="head" -->
<link href="styles.css" rel="stylesheet" type="text/css">
<style type="text/css">
<!--
.style4 {color: #FFFFFF}
-->
</style>
<script src="../Scripts/swfobject_modified.js" type="text/javascript"></script>
<!-- InstanceEndEditable -->
showing a stylesheet link and an embedded style.
So it's not so much that you can't have editable areas in the head of the document, it's more that you can't overlap or improperly nest ANYTHING.
You can also (am I repeating myself?) make a tag's attributes editable. I use that feature most notably for applying different IDs to <body> tags for different neighborhoods in my sites. By applying different body IDs, I can control more specifically elements on those pages. But that's a conversation for another time!
Best,
Beth

Similar Messages

  • Why does this happen when I insert editable region?

    Hi ppl... I got a small problem here. When I insert editing region into the ORANGEBOX div, for some unknown reason which I can't figure out, my spry menu bar shifts to the left. But in preview, it looks fine. What's the reason for this and how can I avoid it? The shifted spry menu bar in the workspace is disturbing me.. haha.. I have attached screenshots of the 2 states below (Before inserting editable region and after inserting editable region)
    Before inserting editable region into the ORANGE BOX
    After inserting editable region into the ORANGEBOX
    Here's the code BEFORE inserting editable region.. If you are free, do try to insert an editable region into the ORANGEBOX, and kindly tell me why it's happening! =) Thanks!
    <!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">
    <!--
    body {
        background-color: #666;
        margin: 0px;
        padding: 0px;
        margin: 0px;
        padding: 0px;
    #wrapper {
        padding: 0px;
        width: 900px;
        margin-right: auto;
        margin-left: auto;
        margin-top: 0px;
        overflow: hidden;
    #navigation {
        height: 122px;
    #mainContent {
        background-color: #FFF;
        overflow: hidden;
    #header {
        background-color: #033;
        height: 248px;
    #navigationlinks {
        font-family: Arial, Helvetica, sans-serif;
        font-size: 14px;
        font-weight: bold;
        color: #000;
        height: 42px;
        background-color: #0C0;
    #footer {
        height: 100px;
        background-color: #F39;
    #orangebox {
        height: 100px;
        width: auto;
        background-color: #F60;
    -->
    </style>
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    <script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    </head>
    <body>
    <div id="wrapper">
      <div id="header"></div>
      <div id="navigationlinks">
        <ul id="MenuBar1" class="MenuBarHorizontal">
          <li><a href="#">Home</a>      </li>
          <li><a href="#">Audio Lectures</a></li>
          <li><a class="MenuBarItemSubmenu" href="#">Video Lectures</a>
            <ul>
              <li><a href="aqeedah1.htm">Aqeedah</a></li>
              <li><a href="fundamentals1.shtml">Tawheed</a></li>
    <li><a href="#">Friday Bayans</a></li>
    <li><a href="#">Other Topics</a></li>
            </ul>
          </li>
          <li><a href="#">Books</a></li>
        </ul>
      </div>
      <div id="mainContent">
        <p> </p>
        <p>mainContent</p>
        <p> </p>
        <div id="orangebox">
          <p>ORANGE BOX    </p>
          <p> </p>
        </div>
    <p> </p>
        <p>mainContent</p>
        <p> </p>
        <p> </p>
      </div>
      <div id="footer">
        <p> </p>
        <p> </p>
        <p> </p>
        <p> </p>
        <p>FOOTER </p>
        <p> </p>
        <p> </p>
        <p> </p>
      </div>
      <p> </p>
      <p> </p>
    </div>
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
    </script>
    </body>
    </html>

    Here's the SpryMenuBarHorizontal.css
    @charset "UTF-8";
    /* SpryMenuBarHorizontal.css - version 0.6 - Spry Pre-Release 1.6.1 */
    /* Copyright (c) 2006. Adobe Systems Incorporated. All rights reserved. */
    LAYOUT INFORMATION: describes box model, positioning, z-order
    /* The outermost container of the Menu Bar, an auto width box with no margin or padding */
    ul.MenuBarHorizontal
        margin: 0;
        padding: 0;
        list-style-type: none;
        font-size: 100%;
        cursor: default;
        width: auto;
    /* Set the active Menu Bar with this class, currently setting z-index to accomodate IE rendering bug: http://therealcrisp.xs4all.nl/meuk/IE-zindexbug.html */
    ul.MenuBarActive
        z-index: 1000;
    /* Menu item containers, position children relative to this container and are a fixed width */
    ul.MenuBarHorizontal li
        margin: 0;
        padding: 0;
        list-style-type: none;
        font-size: 100%;
        position: relative;
        text-align: left;
        cursor: pointer;
        width: 9em;
        float: left;
    /* Submenus should appear below their parent (top: 0) with a higher z-index, but they are initially off the left side of the screen (-1000em) */
    ul.MenuBarHorizontal ul
        margin: 0;
        padding: 0;
        list-style-type: none;
        font-size: 100%;
        z-index: 1020;
        cursor: default;
        width: 9em;
        position: absolute;
        left: -1000em;
    /* Submenu that is showing with class designation MenuBarSubmenuVisible, we set left to auto so it comes onto the screen below its parent menu item */
    ul.MenuBarHorizontal ul.MenuBarSubmenuVisible
        left: auto;
    /* Menu item containers are same fixed width as parent */
    ul.MenuBarHorizontal ul li
        width: 9em;
    /* Submenus should appear slightly overlapping to the right (95%) and up (-5%) */
    ul.MenuBarHorizontal ul ul
        position: absolute;
        margin: -5% 0 0 95%;
    /* Submenu that is showing with class designation MenuBarSubmenuVisible, we set left to 0 so it comes onto the screen */
    ul.MenuBarHorizontal ul.MenuBarSubmenuVisible ul.MenuBarSubmenuVisible
        left: auto;
        top: 0;
    DESIGN INFORMATION: describes color scheme, borders, fonts
    /* Submenu containers have borders on all sides */
    ul.MenuBarHorizontal ul
        border: 1px solid #CCC;
    /* Menu items are a light gray block with padding and no text decoration */
    ul.MenuBarHorizontal a
        display: block;
        cursor: pointer;
        color: #333;
        text-decoration: none;
        font-family: Arial, Helvetica, sans-serif;
        font-size: 12px;
        font-weight: bold;
        padding-top: 1.1em;
        padding-right: 0.75em;
        padding-bottom: 1.1em;
        padding-left: 0.75em;
        text-align: center;
    /* Menu items that have mouse over or focus have a blue background and white text */
    ul.MenuBarHorizontal a:hover, ul.MenuBarHorizontal a:focus
        color: #FFF;
    /* Menu items that are open with submenus are set to MenuBarItemHover with a blue background and white text */
    ul.MenuBarHorizontal a.MenuBarItemHover, ul.MenuBarHorizontal a.MenuBarItemSubmenuHover, ul.MenuBarHorizontal a.MenuBarSubmenuVisible
        color: #FFF;
    SUBMENU INDICATION: styles if there is a submenu under a given menu item
    /* Menu items that have a submenu have the class designation MenuBarItemSubmenu and are set to use a background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal a.MenuBarItemSubmenu
        background-image: url(SpryMenuBarDown.gif);
        background-repeat: no-repeat;
        background-position: 95% 50%;
    /* Menu items that have a submenu have the class designation MenuBarItemSubmenu and are set to use a background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal ul a.MenuBarItemSubmenu
        background-image: url(SpryMenuBarRight.gif);
        background-repeat: no-repeat;
        background-position: 95% 50%;
    /* Menu items that are open with submenus have the class designation MenuBarItemSubmenuHover and are set to use a "hover" background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal a.MenuBarItemSubmenuHover
        background-repeat: no-repeat;
        background-position: 95% 50%;
    /* Menu items that are open with submenus have the class designation MenuBarItemSubmenuHover and are set to use a "hover" background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal ul a.MenuBarItemSubmenuHover
        background-image: url(SpryMenuBarRightHover.gif);
        background-repeat: no-repeat;
        background-position: 95% 50%;
    BROWSER HACKS: the hacks below should not be changed unless you are an expert
    /* HACK FOR IE: to make sure the sub menus show above form controls, we underlay each submenu with an iframe */
    ul.MenuBarHorizontal iframe
        position: absolute;
        z-index: 1010;
        filter:alpha(opacity:0.1);
    /* HACK FOR IE: to stabilize appearance of menu items; the slash in float is to keep IE 5.0 from parsing */
    @media screen, projection
        ul.MenuBarHorizontal li.MenuBarItemIE
        display: inline;
        f\loat: left;

  • How to edit modified preferences in my profile ( non existent printers)

    Two printers I previously owned are listed. How do I remove them; or is this necessary?

    On way (there may be others) is to save the picture you want to use to your desktop and simply drag it onto your existing pic is User & Groups Prefs.

  • Can't manually add editable regions to head in template

    When I created my main template in Dreamweaver CS6 for my website, I had copied most of the page code from another layout I already had, including the head code.  I did not realize there were already editable regions built into the head section of the Dreamweaver template and deleted them when I pasted my previous code without adding new ones.  I then added an editable region to the body and started created pages using the template.
    Everything works well and updates properly when I make changes to the template but now that I am trying to add those editable regions back to the head section so I can change the page title (and possibly add more responsive code), it doesn't work.  I copied and pasted the following code into my template file in Dreamweaver and it saves in the template telling me it's updating the related pages, but when I open those individual pages in Dreamweaver, the code isn't there and those regions are not editable; only the original editable region I created in the body exists and works properly.  Everything else continues to work perfectly.
    Here is the code I pasted into the head around the <title> tag:
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Collings Document Database</title>
    <!-- TemplateEndEditable -->
    And here is the code I pasted into the head just before the </head> tag:
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    </head>
    Any help would be appreciated.  From everything I've read on these forums after searching, it sounds like pasting that code should work but I continue to get the results mentioned.  Thank you.

    Thanks for the response.  I've run the template code through the validator and the following two errors are the only ones that showed up.  I don't see how either of these would cause this issue.  Thoughts?
    Line 5, Column 53: Bad value X-UA-Compatible for attribute http-equiv on element meta.
    <meta http-equiv="X-UA-Compatible" content="IE=Edge">

    Line 27, Column 127: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images. …gs_guitars_stroke_clear.png" width="184" height="81" class="scalable">  </div>

  • Please Help Nested Editable Region Image & Spry

    Please Help Me.
    New to Dreamweaver. I've been given a "grandchild" nested temple with only one editable region to alter. I've read and Googled since Saturday. My brain actually hurts.
    Goal
    - Insert my background image into region
    - Add Spry accordion to mid left
    - Add Spry collapsible to bottom right
    How can 3 things be so hard? Please, can someone walk me through this? Thank you

    I've been given a "grandchild" nested template with only one editable region to alter.
    Nested templates.  Aaaaaak! There's no advantage in nested templates, ever.  They're so problematic it makes my head hurt just thinking about them.
    If you have the parent and grandparent template.dwt files to work with, you'll need to insert Editable Regions to hold your scripts and other supporting widget code.
    If you don't have those files and you can't edit the <head>, you can't insert widgets into Template child or grandchild pages.  You'll need to detach the page from Templates.
    Nancy O.

  • Making template background an editable region

    Oh my goodness, I'm about to cry.  I've literally and without hyperbole spent days trying to figure this out on my own.  I have also contacted Adobe Tech help and was willing to pay for help ... all to no avail.  I am SO hoping there is someone out there who is able to help me.  My deadline to have this website finished is Monday, Sept. 03 and I am stuck.  Now down to the question:
    I have created a webpage which I have saved as template and which I want to use as my master from which all the other templates and pages on my site will be derived.  I would like to be able to change the background in different sections of the site.  The page I have created has an image, but other pages may just have a colour.  Is it possible to make the background colour and image, as set in the page properties, into an editable region?  And, if so, how is it done?  If it is not possible, are there any suggestions for work arounds that will allow me at least some flexibility in this matter?
    Any help on this will be gratefully accepted and enormously appreciated.
    Thank you,
    Malene

    Thank you so much for the reply.  I will be using the Master template I have created to make about another 6 templates.  These templates I will use to create about another 200 pages.  So, my thinking is that the best way is to make the relevant section editable and that is where I am at a loss. I am a novice designer and not at all versed in HTML, so I rely heavily on Dreamweaver's menus to perform various actions.  I know how to make regions editable in general, but I can't find a way to use the "insert editable region" to make the actual background, as set in the "page properties" CSS, editable.  I am guessing doing so requires some sort of HTML knowledge that I don't have. 
    In the code, this is the region I need to make editable (copied and pasted from my template's code):
    body {
    background-color: #e5dfd3;
    background-image: url(../Images/Global/Toronto_Osgoode_Hall_1856.jpg)
    ;      margin-left: 0px;
    margin-top: 0px;

  • Modify Editable regions in template

    I created a main template  then created other templates from this templates.  I now realize that I will need to change the image in the header in some of the nested templates.  for example, there is a template for wisdom which has a child called wisdom videos.  I wanted to change the header image in wisdom which would affect all of its children.  I added an editable region to the main template which changed everything.  I then changed the image in wisdom, but it is not going through to the child wisdom video, which is what i want.
    How can i do that?
    Thanks

    I use templates (although I wouldn't touch nested templates with a 10-foot pole) and server-side includes.
    First, I mentally separate the page layout into three sections:
    1.  Stuff that will not change for the life of the site (i.e., the basic
    structural elements)
    2.  Stuff that *could* change from time to time (e.g., navigation elements,
    burst advertisements, section-specific navigation, etc.)
    3.  Stuff that *will* change from one page to the next
    Then I create a template containing all class1 elements.  Next I create
    server-side include files containing all class 2 elements and place them on
    the template as needed.  Note - some of the class 2 elements may be
    "section-specific elements", and their placement on the template will be
    subject to the next item.  Finally, I insert editable regions to cover the
    class 3 items, INCLUDING the section-specific navigation.
    This allows me to just cookie-cut the rest of the site.  I estimate that
    even for fairly large sites, about 80% of my work goes into planning and
    creating this template file.

  • Editable Regions Problem in CS3

    I am working a set of pages based on the two column fixed with template.
    4 Editable Regions.
    Two Created by Dreamweaver
    Two Created by me
    Doc Title
    Head
    MainContent
    Ad Area
    Almost ALL of my additions are going into the Content Region. 80% of the time I have NO ISSUES
    between Code View and Design View.
    What is happing to me too many times now that it has become annoying......
    I will make a simple code change in Code View, usually WELL WITHIN the editable region tags
    and when I go to view what I did in Design View, I get an error box that says something like this.
    You have made a code change in an area that is designated as uneditable.
    If you wish to keep this change it will be lost the next time you update the template.
    This could be a siple change like adding a bold to a piece of text.
    A lot of times it happens whe I try to put a Container Div around some text.
    It almost ALWAYS happens when I am trying to float something.
    Is this a BUG. Is there a fix? I know I can't ignore it because I have seen what happens when I do that....
    Please don't tell me to update to a more recent version unless that absolutely has the fix in it.
    It cost me an arm to buy this product in the first place and if I had known how little I was gaining
    I would have NEVER purchased it.I certainly don't want to spend any more unless it solves the issue.
    The design view in CS3 STINKS! Design View was one of the reasons
    I wanted the product in the first place. WYSIWYG.  I was trying to upgrade away from years of using HotDog.
    Two years of this now and I still find myself doing most of my design in Code View.
    I don't TRUST Design View.
    I do eventually publish to a copy without template marup but I need to code in the version that is still templated.
    I do change the master template from time to time.
    HELP!

    Better than your helpless nagging would be that you share a link to your page.
    ... and your: Please don't tell me to update to a more recent version unless that absolutely has the fix in it. It's actually also not a very good attitude and (for me!) not a great motivation to help you. Ok, I have this program on the computer, even, but the reasons are to work here in the forum.
    ... and I quote from a thread here in the forum:
    "It's not a word processor or WYSIWYG, never has been, but I think you're using those terms more broadly than the regulars in this forum use them. But if you're happy to use only Design View and let DW code then you'll get similar results to using DW8."

  • How to insert a widget in a editable region from a template

    Hi there,
    ok so basically I am trying to create a HTML page from a template i have already designed.
    when I try to insert a widget (Lightbox Gallery) in the editable region I get the following error.
    "the widget requires code that must be inserted into the head of the document. insertion cannot happen because this document is read only"
    I saw a previous thread (http://forums.adobe.com/thread/901299) that had the same problem with a solution but cant seem to make sense of it.
    Not exactly sure where and what to paste in the header of the HTML page.
    Any help will be much appreciated.
    Thanks

    Hi Murray,
    ha funny you would say that is the exact answer you would give me seeing you posted it
    I understand the logic behind it though not sure what i need to copy and where.
    Basically i craeted a "dummy page" and inserted the widget-no problem there.
    next step- what code do i copy from the dummy page and where do i paste it? in the template or HTML page.
    Dummy HTML with widget 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" />
    <title>Untitled Document</title>
    <script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/jquery.js" type="text/javascript"></script>
    <script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/lightbox.js" type="text/javascript"></script>
    <link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/lightbox.css" rel="stylesheet" type="text/css" />
    <link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/sample_lightbox_layout.css" rel="stylesheet" type="text/css" />
    <style type="text/css">
    /* BeginOAWidget_Instance_2127022: #gallery */
                        .lbGallery {
                                  /*gallery container settings*/
                                  background-color: #CCC;
                                  padding-left: 20px; 
                                  padding-top: 20px; 
                                  padding-right: 20px; 
                                  padding-bottom: 20px; 
                                  width: 540px;
                                  height: auto;
                                  text-align:left;
                        .lbGallery ul { list-style: none; margin:0;padding:0; }
                        .lbGallery ul li { display: inline;margin:0;padding:0; }
                        .lbGallery ul li a{text-decoration:none;}
                        .lbGallery ul li a img {
                                  /*border color, width and margin for the images*/
                                  border-color: #3e3e3e;
                                  border-left-width: 10px;
                                  border-top-width: 10px;
                                  border-right-width: 10px;
                                  border-bottom-width: 20px;
                                  margin-left:5px;
                                  margin-right:5px;
                                  margin-top:5px;
                                  margin-bottom:5px:
                        .lbGallery ul li a:hover img {
                                  /*background color on hover*/
                                  border-color: #ffffff;
                                  border-left-width: 10px;
                                  border-top-width: 10px;
                                  border-right-width: 10px;
                                  border-bottom-width: 20px;
                        #lightbox-container-image-box {
                                  border-top: 0px none #ffffff;
                                  border-right: 0px none #ffffff;
                                  border-bottom: 0px none #ffffff;
                                  border-left: 0px none #ffffff;
                        #lightbox-container-image-data-box {
                                  border-top: 0px;
                                  border-right: 0px none #ffffff;
                                  border-bottom: 0px none #ffffff;
                                  border-left: 0px none #ffffff;
    /* EndOAWidget_Instance_2127022 */
    </style>
    <script type="text/xml">
    <!--
    <oa:widgets>
      <oa:widget wid="2127022" binding="#gallery" />
    </oa:widgets>
    -->
    </script>
    </head>
    <body>
    <div id="gallery" class="lbGallery">
      <ul>
        <li> <a href="/images/lightboxdemo1.jpg" title=""><img src="/images/lightboxdemo_thumb1.jpg" width="72" height="72" alt="Flower" /></a> </li>
        <li> <a href="/images/lightboxdemo2.jpg" title=""><img src="/images/lightboxdemo_thumb2.jpg" width="72" height="72" alt="Tree" /></a> </li>
        <li> <a href="/images/lightboxdemo3.jpg" title=""><img src="/images/lightboxdemo_thumb3.jpg" width="72" height="72" alt="" /></a> </li>
        <li> <a href="/images/lightboxdemo4.jpg" title=""><img src="/images/lightboxdemo_thumb4.jpg" width="72" height="72" alt="" /></a> </li>
        <li> <a href="/images/lightboxdemo5.jpg" title=""><img src="/images/lightboxdemo_thumb5.jpg" width="72" height="72" alt="" /></a> </li>
      </ul>
    </div>
    <script type="text/javascript">
    // BeginOAWidget_Instance_2127022: #gallery
                        $(function(){
                                  $('#gallery a').lightBox({
                                            imageLoading:                              '/images/lightbox/lightbox-ico-loading.gif',                    // (string) Path and the name of the loading icon
                                            imageBtnPrev:                              '/images/lightbox/lightbox-btn-prev.gif',                              // (string) Path and the name of the prev button image
                                            imageBtnNext:                              '/images/lightbox/lightbox-btn-next.gif',                              // (string) Path and the name of the next button image
                                            imageBtnClose:                              '/images/lightbox/lightbox-btn-close.gif',                    // (string) Path and the name of the close btn
                                            imageBlank:                                        '/images/lightbox/lightbox-blank.gif',                              // (string) Path and the name of a blank image (one pixel)
                                            fixedNavigation:                    false,                    // (boolean) Boolean that informs if the navigation (next and prev button) will be fixed or not in the interface.
                                            containerResizeSpeed:          400,                               // Specify the resize duration of container image. These number are miliseconds. 400 is default.
                                            overlayBgColor:                     "#999999",                    // (string) Background color to overlay; inform a hexadecimal value like: #RRGGBB. Where RR, GG, and BB are the hexadecimal values for the red, green, and blue values of the color.
                                            overlayOpacity:                              .6,                    // (integer) Opacity value to overlay; inform: 0.X. Where X are number from 0 to 9
                                            txtImage:                                        'Image',                                        //Default text of image
                                            txtOf:                                                  'of'
    // EndOAWidget_Instance_2127022
    </script>
    </body>
    </html>
    thanks again

  • DW CS3 Remove editable regions

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

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

  • CS6 Inserting table breaks editable region

    In DW CS6 I am building out a site based on one template with three editable regions. I generally work in split view building PHP-MySQL sites such as the current one, and I have been building template-driven sites in Dreamweaver since 1998; but this problem has me stumped. Everything works fine until I insert a table into one of the editable regions. That region immediately becomes non-editable in design view (but I can edit in code view). It doesn't matter how I insert the table -- whether I paste code from another page where the table is being delivered, whether I use the DW Insert Table function, or hand-code from scratch. The result is the same -- I can no longer place a cursor in that editable region, in any design window.
    I seem to remember from CS5 a similar situation with a workaround that included triple clicking somewhere, but I have not been able to find that in this forum or in my notes. Any suggestions?

    The issue exists both at home and at the office. There may be minor differences.  I am now at the office .
    Mac OSX ver. 10.9.4
    DW v. 12.0 Build 5861
    xxxxxxxxxxxxxx
    TEMPLATE CODE
    xxxxxxxxxxxxxxx
    <!doctype html>
    <html>
    <head>
    <meta id="p7PM3" name="viewport" content="width=device-width">
    <meta charset="utf-8">
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Advanced Reporting</title>
    <!-- TemplateEndEditable -->
    <link href="../3D/p7affinity/p7affinity-5.css" rel="stylesheet" type="text/css" media="all">
    <link href="../3D/p7affinity/p7mobius-animate.css" rel="stylesheet" type="text/css" media="all">
    <script type="text/javascript" src="../3D/p7ehc/p7EHCscripts.js"></script>
    <link href='http://fonts.googleapis.com/css?family=Federo' rel='stylesheet' type='text/css'>
    <link href='http://fonts.googleapis.com/css?family=Life+Savers' rel='stylesheet' type='text/css'>
    <link href="../3D/p7dmm/p7pm3/p7PM3-01.css" rel="stylesheet" type="text/css" media="all">
    <script type="text/javascript" src="../3D/p7dmm/p7pm3/p7PM3scripts.js"></script>
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    </head>
    <body>
    <div id="layout">
      <div id="logo">
        <?php include('../3D/includes/logo_content.php'); ?>
      </div>
      <div id="top-navigation">
        <?php include('../3D/includes/primarynav.php'); ?>
      </div>
    <div id="content"><!-- TemplateBeginEditable name="Action Call" -->
      <div class="column-content border-bottom colored-black"> Lorem ipsum dolor sit amet, ne sea vocent scripta abhorreant. </div>
    <!-- TemplateEndEditable -->
      <div class="affinity-row">
        <div class="affinity-column percent70 reverse-float">
          <div class="column-content border-left p7ehc-1"><!-- TemplateBeginEditable name="Main Section" -->
          <h1>Main section heading</h1>
          <p>Lorem ipsum dolor sit amet, </p>
          <h3>Coming up soon...</h3>
          <p>Lorem ipsum dolor sit amet, ne sea vocent </p>
          <!-- TemplateEndEditable --></div>
        </div>
        <div class="affinity-column percent30 reverse-float">
          <div class="column-content p7ehc-1"><!-- TemplateBeginEditable name="Sidebar" -->
          <p><img class="p7-animate zoom-out" src="../3D/art/mobius-art-04.jpg" width="520" height="713" alt=""></p>
          <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Quisque congue tristique eros. Nulla facilisi. Quisque sem mauris, ullamcorper ac, gravida id, mattis id, sapien. Nullam adipiscing enim dapibus felis.</p>
          <!-- TemplateEndEditable --></div>
        </div>
      </div>
    </div>
        <?php include('../3D/includes/footertext.php'); ?>
    </div>
    </body>
    </html>
    Will send child separately

  • I have adobe premiere elements 13 and i imported my video to my computer i click edit video, then it tells me to sign in. so i sign in then accept agreement and nothin happens after that could you tell me whats going on please

    i have adobe premiere elements 13 and i imported my video to my computer i click edit video, then it tells me to sign in. so i sign in then accept agreement and nothin happens after that could you tell me whats going on please

    i have adobe premiere elements 13 and i imported my video to my computer i click edit video, then it tells me to sign in. so i sign in then accept agreement and nothin happens after that could you tell me whats going on please

  • Dreamweaver Template Editable Region Old Problem

    Hello,
    Please, I need urgent help regarding the Adobe Dreamweaver
    CS3 program for Mac OS X. It is, unfortunately, driving me crazy,
    because I have now a problem that is not letting me edit any
    editable region in the child pages I create and apply the template
    to that page. I have tried to restart the computer, restart
    Dreamweaver and even reinstalled Dreamweaver and made my Template
    from scratch and nothing worked. The problem keeps there and
    doesn't let me edit any editable region.
    Here is what happens: I have created a Editable Region called
    "Page Content". Also, another 2 editable regions called "Section
    Navigation" and "Sub Navigation". These editable regions are just
    there to make my job easier. In the Page Content part, I put the
    content I want to add to that page, like text and a heading. For
    the Navigations, I simply change the class of one list item to
    "current", so that my CSS rule can be applied to that list item and
    change the font, so that the users can tell in what page they are
    now, you get it?
    So, what happens? Everytime I try to make changes to the
    editable region Dreamweaver prompts this message:
    "You have made changes in the code in a region that is not
    marked as an Editable Region... You will lose all of your changes
    in the next update of your template. Do you want to retain all of
    the changes?"
    But IT IS A EDITABLE Region, so that is why I dont get it.
    And it gets even worse, because after I lose all of my changes and
    hours of work are wasted.
    I hope you guys, experts in Dreamweaver can make my life a
    lot easier by helping me solve this issue,
    Please help.
    Best regards,
    Thank you for reading this and for the help in advance,
    GB

    And, by the way, such messages are usually triggered by
    improper code usages
    on the page - that's why we need to see your code.
    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
    ==================
    "dreamweaver_pro" <[email protected]> wrote
    in message
    news:[email protected]...
    > Hello,
    >
    > Please, I need urgent help regarding the Adobe
    Dreamweaver CS3 program for
    > Mac
    > OS X. It is, unfortunately, driving me crazy, because I
    have now a problem
    > that
    > is not letting me edit any editable region in the child
    pages I create and
    > apply the template to that page. I have tried to restart
    the computer,
    > restart
    > Dreamweaver and even reinstalled Dreamweaver and made my
    Template from
    > scratch
    > and nothing worked. The problem keeps there and doesn't
    let me edit any
    > editable region.
    >
    > Here is what happens: I have created a Editable Region
    called "Page
    > Content".
    > Also, another 2 editable regions called "Section
    Navigation" and "Sub
    > Navigation". These editable regions are just there to
    make my job easier.
    > In
    > the Page Content part, I put the content I want to add
    to that page, like
    > text
    > and a heading. For the Navigations, I simply change the
    class of one list
    > item
    > to "current", so that my CSS rule can be applied to that
    list item and
    > change
    > the font, so that the users can tell in what page they
    are now, you get
    > it?
    >
    > So, what happens? Everytime I try to make changes to the
    editable region
    > Dreamweaver prompts this message:
    >
    > "You have made changes in the code in a region that is
    not marked as an
    > Editable Region... You will lose all of your changes in
    the next update of
    > your
    > template. Do you want to retain all of the changes?"
    >
    > But IT IS A EDITABLE Region, so that is why I dont get
    it. And it gets
    > even
    > worst, because after I lose all of my changes and hours
    of work are
    > wasted.
    >
    > I hope you guys, experts in Dreamweaver can make my life
    a lot easier by
    > helping me solve this issue,
    > Please help.
    > Best regards,
    >
    > Thank you for reading this and for the help in advance,
    >
    > GB
    >

  • 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

  • How to Display a message after inserting row in table............

    Hi
    I want to display a message after inserting rows in table like *'you have inserted a new row successfully*'.
    i am using the createinsert ADF Button to insert the rows in table.after that i am comitting it.
    after commiting i want to display message for the user.for this what i need to do.
    Please help me.
    Sailaja.

    user10860137
    Can you please explain me the each line in the code briefly.
    +public String saveButton_action(){+
    BindingContainer bindings = getBindings();
    OperationBinding operationBinding = bindings.getOperationBinding("Commit");
    Object result = operationBinding.execute();
    +// note "!" operator has been removed from the default code.+
    +if(operationBinding.getErrors().isEmpty()){+
    FacesContext ctx = FacesContext.getCurrentInstance();
    FacesMessage saveMsg = new FacesMessage("Record Saved Successfully");
    ctx.addMessage(null,saveMsg);
    +}+
    return null;
    +}+
    And i have requirement to show the message on favcet "status bar".not in a popup window.(from the above code the message is showing in popup window. )the Layout i am using is PanelCollection.
    can you tell me what i need to do.
    Thanks
    Sailaja.
    Edited by: sj0609 on Mar 19, 2009 8:03 AM

Maybe you are looking for