Edit region teal colour tag "editableregion" is messing up layout.

Hi I have developed a Photoshop layout.
I carved up vertical menu bar (6 options) and made three different buttons for different states. up down pressed
so I can calculate 6 x button height (52) and 138 width.
So i have an area of   312 x 138
So I create a slice of this size.
So i save for web
Now when in dreamweaver i create template ..
Now for the navigation area of size  312 x 138  i create a div and then i insert a editable region.
I get a bulky teal coloured tag at top
Finally i create my navigation bar and insert 6 images. ... but the bottom is being push by what seems to be the height of the bulky tag.
Any suggestions please

Sure, you can turn off the invisible items, and turn them back on when you need them. Go to View > Visual Aids > Invisible Elements and turn them off.
They only mess up the Design View, they should not be messing up your actual Live View or Browser View.
Beth

Similar Messages

  • Editable regions and UL tags

    I notice that D8 design view can corrupt the view of a page
    element if an editable region is included. I.e.
    <div class="leftsideCol"><!-- TemplateBeginEditable
    name="sideNav" -->
    <ul>
    <li class="title">In-Page links</li>
    <li><a href="#">Navigation
    Title</a></li>
    <li><a href="#">Navigation
    Title</a></li>
    <li><a href="#">Navigation
    Title</a></li>
    <li><a href="#">Navigation
    Title</a></li>
    <li><a href="#">Navigation
    Title</a></li>
    <li><a href="#">Navigation
    Title</a></li>
    <li><a href="#">Navigation
    Title</a></li>
    </ul>
    <!-- TemplateEndEditable -->
    <!-- Main title -->
    <p class="sidebarTitle">?! Notices !?</p>
    <!-- Textbox -->
    <div class="sideMssgeBoxCntnr"><!--
    TemplateBeginEditable name="leftSideCol" -->
    <p class="sideMessageTitleBkgrndYel">Subject
    Title</p>
    <p class="sideMessageBoxText">Put your message here. Be
    succinct to avoid overcrowding the sidebar. Here is a <a
    href="#">link</a> which can be removed by normal text
    delete.</p>
    <!-- TemplateEndEditable --></div>
    </div>
    The first region statements corrupt the view (remove them and
    all displays correctly). This does not affect the final page.
    If I try to solve this by putting the region just inside the
    UL and /UL tags the design view is good. BUT the resulting page has
    an extra UL opening tag. Why is this, it upsets the styling?
    Where can I find a definitive set of rules for putting
    regions around tags other than <p> which seems to work OK? I
    want to make a set of LIs editable and be able to add another LI to
    the list.

    >I notice that D8 design view can corrupt the view of a
    page element if an
    > editable region is included.
    There must be something else going on. Your posted code would
    be quite
    normal. Why not upload this page and post a link to it so I
    can see the
    whole picture, please.
    > Where can I find a definitive set of rules for putting
    regions around
    > tags
    > other than <p> which seems to work OK? I want to
    make a set of LIs
    > editable and
    > be able to add another LI to the list.
    The regions must be properly nested. That's about it. In
    other words, you
    could not have this -
    <div><!-- TemplateBeginEditable name="foo" -->
    </div>
    <!-- TemplateEndEditable -->
    > I want to make a set of LIs editable and
    > be able to add another LI to the list.
    Exactly what you have would do that.
    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
    ==================
    "ROGM" <[email protected]> wrote in message
    news:[email protected]...
    >I notice that D8 design view can corrupt the view of a
    page element if an
    > editable region is included. I.e.
    >
    > <div class="leftsideCol"><!--
    TemplateBeginEditable name="sideNav" -->
    >
    > <li class="title">In-Page links</li>
    >
    <a href="#">Navigation Title</a></li>
    >
    <a href="#">Navigation Title</a></li>
    >
    <a href="#">Navigation Title</a></li>
    >
    <a href="#">Navigation Title</a></li>
    >
    <a href="#">Navigation Title</a></li>
    >
    <a href="#">Navigation Title</a></li>
    >
    <a href="#">Navigation Title</a></li>
    >
    > <!-- TemplateEndEditable -->
    > <!-- Main title -->
    > <p class="sidebarTitle">?! Notices !?</p>
    > <!-- Textbox -->
    > <div class="sideMssgeBoxCntnr"><!--
    TemplateBeginEditable
    > name="leftSideCol"
    > -->
    > <p class="sideMessageTitleBkgrndYel">Subject
    Title</p>
    > <p class="sideMessageBoxText">Put your message
    here. Be succinct to avoid
    > overcrowding the sidebar. Here is a <a
    href="#">link</a> which can be
    > removed
    > by normal text delete.</p>
    > <!-- TemplateEndEditable --></div>
    > </div>
    >
    > The first region statements corrupt the view (remove
    them and all displays
    > correctly). This does not affect the final page.
    >
    > If I try to solve this by putting the region just inside
    the UL and /UL
    > tags
    > the design view is good. BUT the resulting page has an
    extra UL opening
    > tag.
    > Why is this, it upsets the styling?
    >
    > Where can I find a definitive set of rules for putting
    regions around
    > tags
    > other than <p> which seems to work OK? I want to
    make a set of LIs
    > editable and
    > be able to add another LI to the list.
    >

  • Adding text to editable region creates space in the rest of my layout

    I created my layout in PS, sliced the images and then imported to DW (html and images).
    Layout looks great.
    I created editable regions in the template I created from the .html
    One I start inserting text into these regions, my container moves and it throws the rest of the layout off by adding space between the editable region and the area above it (a big black line horizontally through the page).
    Is there a way to keep the container/editable region from moving or growing with the text so that it doesn't change my layout?
    On a side note, this change doesn't appear in live view. When I preview in browser, Safari layout looks great, but text doesn't appear. In firefox, text appears, but layout is a mess.
    Here is the code from the editable region to which I am trying to add text:
    <!-- TemplateBeginEditable name="main_content_area" -->
            <div id="site_layout_contentmain">Content for  id "site_layout_contentmain" Goes Here</div>
          <!-- TemplateEndEditable --></td>
    ANY help is GREATLY appreciated!!!!!

    MHarvey2001 wrote:
    Yes, the design is appearing to pull apart when I add content, but only in the Firefox preview.
    If it pulls apart in Firefox, chances are it pulls apart in all browsers when text size is increased.
    The problem with Photoshop code is that it is a) rigid, b) unstable and c) invalid.  
    To illustrate, run your code through the on-line validation tools below.
    CSS - http://jigsaw.w3.org/css-validator/
    HTML - http://validator.w3.org/
    Photoshop is OK for designing quick comps to show the client but they won't hold up on a real site.
    IMO, the benefits of starting over far outweigh the inconvenience.
    HTML & CSS Tutorials - http://w3schools.com/
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb
    http://alt-web.blogspot.com/

  • Ap divs in editable regions

    Hi, I have a site using several pages from templates. I have
    3 different templates used for groups of different pages. In the
    editables regions of my pages, I have several ap divs, depending on
    page content. All looks fine until I update a template. After that,
    all the ap divs turn into boxes with a dotted outline that fits
    across the ed region.
    No matter which template I update, the ap divs in their
    associated pages disappear and wreak havoc with the layout in my
    editable regions. My updates dates can be as simple as adding a
    button or or enlarging the edit regions. Each time I have to
    re-layout my edit regions.
    Do you if this is a bug or am I just doing something wrong?
    Any help would be greatly appreciated.

    > Do you if this is a bug or am I just doing something
    wrong? Any help would
    > be
    > greatly appreciated.
    I am pretty sure we can find the answer by looking at your
    code. Can you
    show us one of the child pages on which this trouble occurs
    by posting a
    link to the page?
    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
    ==================
    "Fran in Brig" <[email protected]> wrote in
    message
    news:gqbl2f$eml$[email protected]..
    > Hi, I have a site using several pages from templates. I
    have 3 different
    > templates used for groups of different pages. In the
    editables regions of
    > my
    > pages, I have several ap divs, depending on page
    content. All looks fine
    > until
    > I update a template. After that, all the ap divs turn
    into boxes with a
    > dotted
    > outline that fits across the ed region.
    >
    > No matter which template I update, the ap divs in their
    associated pages
    > disappear and wreak havoc with the layout in my editable
    regions. My
    > updates
    > dates can be as simple as adding a button or or
    enlarging the edit
    > regions.
    > Each time I have to re-layout my edit regions.
    >
    > Do you if this is a bug or am I just doing something
    wrong? Any help would
    > be
    > greatly appreciated.
    >

  • Adding editable region tags moves my content in non-editable regions

    I have a template based on a template (the first with my navigation, and the second is based on the first with a sidebar added). When I add an editable region to the second template, it moves my sidebar down to leave a gap between the nav bar and the top of the sidebar. On the second template I want to add editable regions to the content area and to the sidebar. Even if I don't add any content to the editable reagions and just place the editable regions tags, my sidebar still moves down. I have tried adding two seperate editable regions and also adding one large editable region covering the content area and sidebar and the sidebar moved both times. My content area is a div floated left and the sidebar is a div floated right.
    I don't understand why anything is moving when I am only adding tags to make an area editable

    Do you have a container that the two divs are in and if so, are you clearing the floats? It's hard to give an answer without seeing the problem page.
    Jim

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

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

  • Template error when pasting code between editable region tags

    Hi everyone,
    The following code snippet is part of the code in my template file:
      <div id="content">
      <div id="content_main">
        <div id="content_inner"><!-- InstanceBeginEditable name="inner" --><!-- InstanceEndEditable --></div>
        <div id="sidebar">
        <h3 class="round2">Categories</h3>
    Note that the above code contains an editable region as follows:
    <!-- InstanceBeginEditable name="inner" --><!-- InstanceEndEditable -->
    Back in my file that's attached to this template, I tried to paste code between these two tags:
    <!-- InstanceBeginEditable name="inner" --> A whole heap of code was pasted here <!-- InstanceEndEditable -->
    But I'm getting the following error:
    "You have made changes to code that is not marked as editable. If you retain those changes, they will be lost the next time you apply a template update to this file. Do you want to retain the changes until then?"
    I don't know why it's saying this since I'm adding code in between the two instance editable tags.
    Does anyone know what's going on here?
    Appreciate any help.

    Hello hth
    Just so you'll know, although 'hth' looks like a signature, it's really an abbreviation for "hope this helps"!
    I have put the code in that you suggested, (via new style sheet I named paradent) enclosed the text within the <p>...</p> but still not working:
    P
    .twoColLiqLtHdr #container #mainContent .paradent {
    font-family: Arial, Helvetica, sans-serif;
    font-size: medium;
    font-weight: normal;
    text-indent: 35px;
    word-spacing: normal;
    <span class="paradent">No color flagged the coming of spring to the Lowveld. The rains were late again, and from the Limpopo to the Sabi River and beyond into Mozambique, the mopani trees were leafless and grey; the wide rivers dry and white under the relentless sun.<br />
    This is not valid code - it's not how you use CSS.
    All CSS needs to either be placed in an external stylesheet which is linked in the head of the document, embedded between <style> tags in the head of the document, or placed inline in the target tag.  Examples of each would be -
    LINKED -
    <link rel="stylesheet" href="path_to_CSS_file.css" type="text/css">
    </head>
    EMBEDDED -
    <style type="text/css">
    body { margin:0; }
    </style>
    INLINE -
    <body style="margin:0;">
    Yours is not only in the wrong place (within the body content), but it's also between <p> tags rather than <style> tags.  That's not going to work at all.  Can you handle getting that rule into the right place in your code?

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

  • Modifying a template resulted in all child pages with repeating editable regions - Help !

    Good morning,
    I have recently been appointed to update a website designed in Dreamweaver by an employee who is no longer here. I have read books on the software and practiced an insane amount which permitted me to update child pages, links, documents etc... however:
    I was asked to add a new button to an "non-editable" region of a template. Trying to do so resulted in a massive mess (with massive anxiety).
    Even thou the new template had all the same text and editable regions, all my pages look completely different from the template itself. The editable regions appears 2-3 times in different locations ex: Header is showed on the bottom, top etc... and the Editable region titles (EditableRegion1 etc...) repeat themselves as well.
    I really need help and not sure what to do, I have tried everything and I am only making it worse and worse. All I want/need is for all my html pages created with this template, match the template.
    Please note that this site is local, not online.
    Since I noticed on other threads that the code is needed; here it 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">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>QMS: AFM</title>
    <style type="text/css">
    <!--
    body  {
    font: 100% Verdana, Arial, Helvetica, sans-serif;
    background: #666666;
    margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
    padding: 0;
    text-align: center; /* this centers the container in IE 5* browsers. The text is then set to the left aligned default in the #container selector */
    color: #000000;
    background-color: #D7D7D7;
    background-repeat: repeat-x;
    border-top-color: #066;
    border-right-color: #066;
    border-bottom-color: #066;
    border-left-color: #066;
    /* Tips for Elastic layouts
    1. Since the elastic layouts overall sizing is based on the user's default fonts size, they are more unpredictable. Used correctly, they are also more accessible for those that need larger fonts size since the line length remains proportionate.
    2. Sizing of divs in this layout are based on the 100% font size in the body element. If you decrease the text size overall by using a font-size: 80% on the body element or the #container, remember that the entire layout will downsize proportionately. You may want to increase the widths of the various divs to compensate for this.
    3. If font sizing is changed in differing amounts on each div instead of on the overall design (ie: #sidebar1 is given a 70% font size and #mainContent is given an 85% font size), this will proportionately change each of the divs overall size. You may want to adjust based on your final font sizing.
    .twoColElsLtHdr #container {
    width: 46em;  /* this width will create a container that will fit in an 800px browser window if text is left at browser default font sizes */
    background: #FFFFFF;
    margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
    border: 30px none #C4C4C4;
    text-align: left; /* this overrides the text-align: center on the body element. */
    padding-left: 10px;
    background-color: #FFF;
    border-top-color: #C4C4C4;
    border-right-color: #C4C4C4;
    border-bottom-color: #C4C4C4;
    border-bottom-style: outset;
    border-left-style: outset;
    border-top-width: thick;
    border-right-style: outset;
    border-top-style: outset;
    border-left-color: #C4C4C4;
    border-right-width: thick;
    border-bottom-width: thick;
    border-left-width: thick;
    .twoColElsLtHdr #header {
    padding: 0 10px;  /* this padding matches the left alignment of the elements in the divs that appear beneath it. If an image is used in the #header instead of text, you may want to remove the padding. */
    background-color: #FFF;
    .twoColElsLtHdr #header h1 {
    margin: 0; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
    padding: 10px 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
    /* Tips for sidebar1:
    1. Be aware that if you set a font-size value on this div, the overall width of the div will be adjusted accordingly.
    2. Since we are working in ems, it's best not to use padding on the sidebar itself. It will be added to the width for standards compliant browsers creating an unknown actual width.
    3. Space between the side of the div and the elements within it can be created by placing a left and right margin on those elements as seen in the ".twoColElsLtHdr #sidebar1 p" rule.
    .twoColElsLtHdr #sidebar1 {
    float: left;
    width: 12em; /* the background color will be displayed for the length of the content in the column, but no further */
    padding: 15px 0; /* top and bottom padding create visual space within this div */
    background-color: #066;
    background-repeat: repeat-x;
    border-top-width: thin;
    border-top-style: none;
    border-right-style: none;
    border-bottom-style: none;
    border-left-style: none;
    border-right-width: thin;
    border-bottom-width: thin;
    border-left-width: thin;
    color: #FFF;
    padding-left: 0px;
    clear: left;
    .twoColElsLtHdr #sidebar1 h3, .twoColElsLtHdr #sidebar1 p {
    margin-left: 10px; /* the left and right margin should be given to every element that will be placed in the side columns */
    margin-right: 10px;
    background-color: #066;
    text-decoration: inherit;
    /* Tips for mainContent:
    1. If you give this #mainContent div a font-size value different than the #sidebar1 div, the margins of the #mainContent div will be based on its font-size and the width of the #sidebar1 div will be based on its font-size. You may wish to adjust the values of these divs.
    2. The space between the mainContent and sidebar1 is created with the left margin on the mainContent div.  No matter how much content the sidebar1 div contains, the column space will remain. You can remove this left margin if you want the #mainContent div's text to fill the #sidebar1 space when the content in #sidebar1 ends.
    3. To avoid float drop, you may need to test to determine the approximate maximum image/element size since this layout is based on the user's font sizing combined with the values you set. However, if the user has their browser font size set lower than normal, less space will be available in the #mainContent div than you may see on testing.
    4. In the Internet Explorer Conditional Comment below, the zoom property is used to give the mainContent "hasLayout." This avoids several IE-specific bugs that may occur.
    .twoColElsLtHdr #mainContent {
    margin: 0 1.5em 0 13em; /* the right margin can be given in ems or pixels. It creates the space down the right side of the page. */
    color:#069;
    background-color:#FFF;
    border-top-style: none;
    border-right-style: none;
    border-bottom-style: none;
    border-left-style: none;
    .twoColElsLtHdr #mainContent a:link {
    text-decoration: none;
    color: #069;
    .twoColElsLtHdr #mainContent a:visited {
    text-decoration: none;
    color: #069;
    .twoColElsLtHdr #mainContent a:hover {
    text-decoration: underline;
    color: #069;
    background-color:#FFF
    .twoColElsLtHdr #mainContent a:active {
    text-decoration: none;
    color: #069;
    .twoColElsLtHdr #footer {
    padding: 0 10px;
    line-height: 0pt;
    color: #069;
    background-color: #FFF;
    font-size: 10px;
    .twoColElsLtHdr #footer p {
    margin: 0; /* zeroing the margins of the first element in the footer will avoid the possibility of margin collapse - a space between divs */
    padding: 10px 0; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
    background-color: #FFF;
    /* Miscellaneous classes for reuse */
    .fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
    float: right;
    margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page */
    float: left;
    margin-right: 8px;
    .clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
    clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    h1 {
    color: #069;
    font-size: 16px;
    border-top-color: #069;
    border-top-width: thin;
    border-right-width: thin;
    padding-right: 0px;
    padding-left: 0px;
    body,td,th {
    font-family: verdana;
    text-decoration: none;
    color: #069;
    border-top-color: #069;
    border-right-color: #069;
    border-bottom-color: #069;
    border-left-color: #069;
    border-top-style: solid;
    border-right-style: solid;
    border-bottom-style: solid;
    border-left-style: solid;
    border-top-width: thin;
    border-right-width: thin;
    border-bottom-width: thin;
    border-left-width: thin;
    a:link {
    text-decoration: none;
    color: #FFF;
    a:visited {
    text-decoration: none;
    color: #FFF;
    a:hover {
    text-decoration: underline;
    color: #FFF;
    background-color: #;
    background-repeat: repeat-x;
    background-position: center;
    border-top-color: #069;
    border-right-color: #069;
    border-bottom-color: #069;
    border-left-color: #069;
    a:active {
    text-decoration: none;
    color: #FFF;
    border-color: #FFF;
    padding-left: 20px;
    -->
    </style><!--[if IE]>
    <style type="text/css">
    /* place css fixes for all versions of IE in this conditional comment */
    .twoColElsLtHdr #sidebar1 { padding-top: 30px; }
    .twoColElsLtHdr #mainContent { zoom: 1; padding-top: 15px; }
    /* the above proprietary zoom property gives IE the hasLayout it needs to avoid several bugs */
    </style>
    <![endif]-->
    <link href="file:///U|/AFM/Dreamweaver/Left sidebar.css" rel="stylesheet" type="text/css" />
    </head>
    <body link="#006699" class="twoColElsLtHdr">
    <div id="container">
    <div id="header">
        <h1><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/pwgsc-e.gif" width="364" height="33" align="left" alt="wordmark" /><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/wordmark_canada.gif" width="83" height="21" align="right" alt="wordmark2" /></h1>
        <p> </p>
        <p><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/AFM QMS banner.jpg" width="709" height="80" alt="banner" border="0"/><a href="mailto:[email protected]"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Contactus-e.JPG" width="110" height="21" alt="contactus-e" border="0" /></a><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/French-e.JPG" width="115" height="21" alt="french-e" border="0" /> <a href="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Continual Improvement/QMSTeamMembers-e.html"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Help-e.JPG" width="115" height="21" alt="help-e" border="0" /> <img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Search-e.JPG" width="115" height="21" alt="search-e" border="0" /></a><a href="http://source.tpsgc-pwgsc.gc.ca"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/thesource.jpg" width="120" height="21" alt="TheSource" border="0" /> <img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Home-e.jpg" width="104" height="21" alt="home-e" border="0" /></a></p>
        <p> </p>
      </div>
    <div class="twoColElsLtHdr" id="sidebar1">
        <p><a href="../QMS HOME/QMSHome-e.html"><strong>QMS Home</strong></a></p>
        <hr />
        <p><a href="../ABOUTAFM/AboutAFM-e.html"><strong>About AFM</strong></a></p>
    <hr />
    <p><a href="../AdminProcedures/AdminProcedure-e.html"><strong>Administrative Procedures</strong></a></p>
    <hr />
    <p><a href="../BusinessUnits/BusinessUnits-e.html"><strong>Business Units</strong></a></p>
    <hr />
    <p><a href="../POINTSOFINTEREST/pointsofinterest-e.html"><strong>Points Of Interest</strong></a></p>
    <hr />
    <p><a href="../Achievements/Achievements-e.html"><strong>Achievements</strong></a></p>
    <hr />
    <p><strong><a href="../MeasuringPerformance/measuringperformance-e.html">Measuring Performance</a></strong></p>
    <hr />
    <p><a href="../References/references-e.html"><strong>References</strong></a></p>
    <hr />
    <p><a href="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/ContinualImprovement-e.html"><strong>Continual Improvement</strong> </a></p>
    </div>
    <div id="mainContent">
        <h2>Header</h2>
        <p>Paragraph</p>
        <h1>Sub Header </h1>
        <p> </p>
        <h1> </h1>
        <h2> </h2>
        <h1> </h1>
        <p> </p>
        <h2> </h2>
        <!-- end #mainContent -->
      </div>
      <!-- This clearing element should immediately follow the #mainContent div in order to force the #container div to contain all child floats -->
           <br class="clearfloat" />
      </p>
      <div id="footer">
        <hr width="100%" size="8" noshade="noshade" color="#006666" id="color=&quot;069&quot;" colour="#069"/>
        <p><strong>Maintainted by: ASQM </strong></p>
        <p><strong>Date Modified: 2013-03-25</strong></p>
        <!-- end #footer -->
      </div>
      <script type="text/javascript">
    <!--
    //-->
    </script>
      </h3>
        <!-- end #container -->
    </h3>
    </div>
    <script type="text/javascript">
    <!--
    //-->
    </script>
    </body>
    </html>

    I am not suprised, the previous employee tried to recreate the English version of the site in another folder structure and did not change all links and was still using a template in the wrong location.
    I think I created the mess by trying to modify the existing template's non-editable region in order to add a new button. When trying to update all the pages, the fiasco started.
    Do you think the best option would be to create a new template in the correct folder structure and apply it? Would it fix the current pages or will I have to fix them all manualy on by one?
    I understand it is difficult to deal with a newbie of my magnitude and thanks again.

  • Quick Question regarding an error with editable regions

    Hello,
    I am a co-op student and I work with other students as well, on our large company website. I have always been considered the cheif coder, and nobody knew the wesite layout and file directory as well as me. However, something terrible has happened while somebody was updating some information on one of your HTML pages.
    I logged in to Dreamweaver CS3 on afternoon to make a very simple text error change on our website. As soon as I hit "synchronize sitewide", it stated that there was no synchronization necessary, although I had already made a change. So then, on the template (.DWT) page, I thought I would backspace any character, and then retype it again in order for the "save" option to appear, so that I could save the template, and have it update all HTML pages, as well as the page that had just said "no synchronization necessary". I thought that I had to update the template first, which was strange, as I never had to do this before.
    When I clicked update, the error message that I got was that I have placed an editable region inside of a block tag. I checked the HTML pages as well as our template (.DWT) pages, and indeed, the <!--TemplateBeginEditable-->"Page Header"<!--TemplateEndEditable--> was embedded in a <h1></h1> pair. The pair appears black and delete-able in the template files, and grey in the HTML files, which is expected. However, I have been working at this institution for four months, and I recall that the <h1> tag pair had always been there since I remember. (How badly did this other person mess up?! =S)
    I tried to delete it from the .DWT file (the small editable region, and the <h1> tags), and now, what happens is that if I try to save a template so it updates all other HTML pages before synchronization, the template simply does not update anything, and I get no message whatsoever after clicking Save.
    Any help would be greatly appreciated. Thank you in advance for coping with these many details. I simply want to be able to update HTML pages again, because my boss really needs it, and I have never had such a problem before (having made much larger changes to this same website in the past)
    Thanks again,
    Mr. V

    How many child pages are you supporting with this DWT?   Hopefully less than 50 pages.
    Is your code valid?  HTML Validator - http://validator.w3.org
    Can you post a link to your DWT page, or copy and paste your code here?
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists
    www.alt-web.com/
    www.twitter.com/altweb
    www.alt-web.blogspot.com

  • How do you change the background in an editable region?

    I have created a template with an editable region in it.  I then created a web page based on the template and have added text to the editable region.  I would like to change the background color of just the editable region and just for this web page.  How can I do that?
    Thanks.

    Well... am sure others will correct me if i'm wrong, but it seems fairly simple.
    1/ There must be a tag identifying that editable area. Either a <div>, or a <table>, or whatever...
    2/ Create a class in you stylesheet with the background colour you want to use and assign it to the tag
    3/ Alternatively, if you'd rather use an inline style, then go to the tag in code view, right click, select style from the menu and then in the quotes right click again and select background-color. Choose your color and you're done.
    If the editable area is a <div> for instance, your inline css should look like this:
    <div style="background-color:#CCCCCC"> This will give you a grey background</div>
    Cheers,
    JJ
    PS: If you can put the page up it'll be easier to help you

  • Duplicate Editable Regions (DW,CS5)

    Hi, every time i try and save my file as a template an error message pops up saying: There is an error at line 165, column 8 (absolute position 6235): Duplicate editable regions of name "Document Head"
    Please help
    Thanks:)

    The error message you are getting should be translated to read "Oops - your code is a mess".
    You have two <head> tags and three </head> tags, and you have an embedded CSS styles sheet between </body> and </html>!
    You also have this code in place - it should be deleted -
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    Fix that, validate your page at http://validator.w3.org, and when it validates, then you can save it without error.

  • 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

Maybe you are looking for

  • Dynamic Structure Creation

    Hello Expert, My requirement is like i have a selection screen where user can put any database table name and once he execute then all the records whatever stored in the table can download in a .TXT file. I am trying this by using field symbol but i

  • How do I delete visited sites from my address bar.

    I can't delete visited websites from my address folder and if I type in a website other websites pop up. I had it set for private browsing but that doesn't work either. I've cleared the history to no avail. I've delete some of the websites if they we

  • Date format is connected to time format

    I am following the Help menu that explains how I should be able to set the date and time format. In the Inspector, I have "Cell Format" and under that I can choose "Date and Time". Now, under Date and Time, I have two separate drop lists, one for Dat

  • Upgrade W530 nonbacklit keyboard to backlit

    Hey folks, I bought a slightly used W530 back this summer. I love this thing, it has all the power I need, an SSD+1TB HDD expansion, 1080p screen, etc. It checked all the boxes in what I wanted in a laptop. The only thing I forgot to check on was bac

  • Uninstalling Adobe Photoshop 3.0

    I installed Adobe Photoshop 3.0 from a free download on the Adobe site. I wish to uninstall it now. How do I go about the Uninstall process?