Can a div be an editable region in a template?

This is my first attempt to work with templates. I have a main area in the center of the page where I want to be able to adjust font-size, and perhaps other text properties. I use a div called "textbox" I set it up as an editable region, but every time I try to change font-size, I am told that this is an uneditable region and the change will be discarded. Here is the code in my program:
<!-- InstanceBeginEditable name="textbox" -->
    <div id ="textbox">
      <p>Here is some text in the box</p>
      <p> </p>
    </div>
    <!-- InstanceEndEditable -->
Any suggestions?

Okay - all is well.  Yet again I find myself spend as much or more time in Code view, than Design view. With the cursor inbetween a couple of divs, I could make it editable.  I found in a couple of cases the editable region was stuck in an odd random place in the page - Code view helped me figure it out.
<div id="mainContent">
  <!-- InstanceBeginEditable name="mainContent" -->
/* all the below is editable */
<div id="featureBox1"><h3>Feature box one</h3>
    <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at, odio.</p>
    </div><div id="featureBox2"><h3>Feature box two</h3>
    <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at, odio.</p>
    </div>
/* all the above is editable */
<!-- InstanceEndEditable --> 
  </div><!-- end #mainContent -->

Similar Messages

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

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

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

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

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

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

  • Can't load swf into editable region

    Am using DW CS4 in W7 64.
    Have designed an html site with one page that has a swf to control dynamic content with php.
    All the pages are created based on one template and al is fine until I try to place the flash file in the editable area of the html page. It seems that no swf files can me placed in this or any other editable area of the page.
    When the swf is put in the follwoing error comes up "While executing object Tag in Flash htm, a JavaScript error occurred"
    Any one else had this issue? More to the point anyone found a work around?

    Cevema wrote:
    To test the theory, as I had previously loaded CS4 onto my old XP pro machine, following a fresh install of XP Pro, and as Dreamweaver had never been started on the is machine before, I then created a brand new page from the template and tried to load in a swf file, but got the same error message. For a fresh install this couldn't be a corrupt file. A friend also tried this on his machine and had the same result.
    I don't normally use either templates or SWFs, but I have just done a quick test in Dreamweaver CS4 on Windows Vista 32-bit. Dreamweaver inserted the SWF into an editable region without demur. It's definitely not a Dreamweaver bug.
    Did your friend use the same template?
    Since a JavaScript error is being generated, I suspect you have invalid code somewhere in your template, or perhaps you have given more than one element the same ID. Validate your page with the W3C validator (http://validator.w3.org/), and eliminate any errors it finds.

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

  • Inputting a list into an alternative to inputting it into an editable region in a template

    Hello all,
    I did ask this question yesterday but only got partial feedback so I'm hoping someone can help as I can't find the answer anywhere.
    I'm hoping you can help me.
    I am creating an online clothing shop website and am having trouble.
    I have created a main template from scratch that reflects in the mens and womens pages, and the contact, about etc pages with all headers, logos, footer, a spry menu etc. I made these pages from the main template via new - Page from template etc so any changes I made to the header, logo etc will easily reflect in all of these pages.
    This part is all fine.
    This is my issue - in the main template I have an editable region so that I can input different content ie. 'about' info on the 'about' page, and product info on the mens / womens pages etc.
    Basically in each page Mens / Womens I need category pages - tops, shirts etc. These are all in the drop down spry menu but I also want them as a list in the mens and womens pages.
    From the template I created the mens and womens pages and have now saved these as a template as there will be around 10 categories for each mens and womens (tops, shirts etc) that I want to be able to replect any changes, ie. in the 'mens template' instead of having to do it in each category page - as this will take a long time.
    The problem is that I put the list in the editable region in the mens template, but I now know any changes I make wont be relfected in the category pages I have made from the mens template as this is an editable region.
    How can I make a category list in the mens template page that will be reflected in each category page?
    I'm really stuck and have no idea how to do this, I'd appreciate any help.
    Thankyou in advance

    I don't recommend using multiple or nested Templates.  There are much better ways to do what you want without going down this very slippery slope.
    Use Server-Side Includes alone or with your main Template.
    Build a Dynamic Site with databases and server-side programming.
    E-commerce Solutions:
    Cartweaver (extension for Dreamweaver)
    http://www.cartweaver.com/
    Web Assist
    http://www.webassist.com/support/ecommerce-options.php
    Building an e-comm site with DW & PHP (video training) 
    http://www.lynda.com/Web-Interactive-Web-Design-Projects-tutorials/Building-eCommerce-Web- Site-Using-Dreamweaver-PHP/83091-2.html?utm_medium=affiliate&utm_source=ldc_affiliate&utm_ content=524&utm_campaign=CD4386&bid=524&aid=CD4386&opt=
    Nancy O.

  • Error adding editable region in nested template Header

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

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

  • Open a QT movie in editable region of page (template)

    I am using templates for my site.  I'd like a movie link to open in a dependent page in the editable region of the page if possible.  Can't seem to make it happen.  The movie always opens in its own blank page.

    Did you embed a QT Player on the page? 
    http://www.mediacollege.com/video/format/quicktime/streaming/
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

  • Can only edit one editable region

    Hi,
    I have defined two editable regions in a template. I can edit one fine, but not the other. The one I cannot edit is for a submenu and picture on this site: 67.199.64.241/
    Any ideas? Any help would be greatly appreciated.
    This is the code (which I cannot edit in InContext):
    <ul id="navleft">
    <li id="nav_hom"><a href="/index.asp">Home</a></li>
    <li id="nav_do"><a href="/whatwedo.asp">  Who We Are</a></li>
    <li id="nav_cabout"><a href="/consumers/login.asp">Current Consumers</a></li>
    <li id="nav_pabout"><a href="/pa/about.asp">Current PAs</a></li>
    <li id="nav_cal"><a href="http://www.calendarwiz.com/calendars/calendar.php?crd=cdchoices&" target="_blank">Calendar</a></li>
    <li id="nav_pro"><a href="/profiles/profiles.asp">Profiles</a></li>
    <li id="nav_news"><a href="/news.asp">CDC in the News</a> </li>
    <li id="nav_lnk"><a href="/links.asp">Links</a></li>
    <li id="nav_blank"><a href="/message.asp"> Message from CEO</a></li>
    <!-- TemplateBeginEditable name="OptionalMenuPicture" --> <a name="submenu" id="MainContent2"></a>
    <li class="c2">
      <div ice:editable="css_styles,media,hyperlink">
        OptionalMenuPicture
        </div>
    <!-- TemplateEndEditable -->
      </ul>

    Use this:
    <ul id="navleft">
    <li id="nav_hom"><a href="/index.asp">Home</a></li>
    <li id="nav_do"><a href="/whatwedo.asp">  Who We Are</a></li>
    <li id="nav_cabout"><a href="/consumers/login.asp">Current Consumers</a></li>
    <li id="nav_pabout"><a href="/pa/about.asp">Current PAs</a></li>
    <li id="nav_cal"><a href="http://www.calendarwiz.com/calendars/calendar.php?crd=cdchoices&" target="_blank">Calendar</a></li>
    <li id="nav_pro"><a href="/profiles/profiles.asp">Profiles</a></li>
    <li id="nav_news"><a href="/news.asp">CDC in the News</a> </li>
    <li id="nav_lnk"><a href="/links.asp">Links</a></li>
    <li id="nav_blank"><a href="/message.asp"> Message from CEO</a></li>
    <!-- InstanceBeginEditable name="OptionalMenuPicture" -->
    <div ice:editable="css_styles,media,hyperlink">
    <img src="/images/smallpics/cl_07_2425.jpg" width="170" height="174" alt="Constance Laymon, executive director, Consumer Directed Choices"><br><!-- #BeginLibraryItem "/library/new.lbi" --><ul id="navoptional">
    New? Learn More:
      <li><a href="/pgms.asp">&gt Potential Consumers</a></li>
      <li><a href="/empopps.asp">&gt Potential  Personal Assistants</a></li>
      <li><a href="/srchsite.asp">&gt Search site</a></li>
    </ul>
    <!-- #EndLibraryItem -->
    </div>
    <li><img src="/images/smallpics/staff_20081.jpg" alt="Staff 2008 picnic, welcome!" width="170" height="118"><br></li>
    <!-- InstanceEndEditable -->
      </ul>

  • Can't Delete Non-Editable Region in Template?

    Well, I can in existing templates but if I create a new one from an existing page using "Save as Template", when I try to delete a non-editable region in the template, DW won't let me.  I don't know why.  Aaaargh!
    It's my understanding I should be able to edit anything in a template.  I've tried existing DW and restarting.  I've tried using other pages as a basis for the template.  Every template I create won't let me delete non-editable regions.  I'm highlighting the non-editable region and pressing the delete key.  I can't delete.

    burro_mail wrote:
    Not sure DW is doing what you describe...
    But I am certain you could remove the region in code view.
    Even if you are a WYSIWYG-er and not a big code-head, it should be pretty easy to remove the region markers and everything between them...
    Trust me, it is.  I'm wondering if the problem is associated with the fact that the source page that I saved as a template was based on a template?  I just noticed that this new template refers to another template.  I'm thinking that means the other template is controlling what I'm trying to do in the current template.
    That's it.  I just tried saving a template under a different name (still retaining the correct template file extension) but did not do the save as template.  Now I can completely edit that template.  So you if you save a page that is controled by a template, as a template, that new template is controlled by the previous template.
    I've got a headache now.

  • 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

  • Editable region but not in code view

    EDIT: While cooking dinner I thought that the computer "fixes" itself when it reboots what about Dreamweaver?  I closed DW down.  Reopened the app and voila.  I CAN edit that section in code view now.  It's weird but it appears to be working.  I'll repost if something is amiss again regarding this issue.  I'll leave the post up in case it's helpful to anyone else.  thanks.
    I have new pages made from a template.  I can only edit in design view NOT in code view.  I get the standard error of I'm trying to edit where I'm not allowed.  I've made templates many times but never had this problem (I don't think!).  Does someone have a tip or help for me?  In addition to this issue I was not able to change the title of the page until I added the editable region in the template for title line.  That's always been default editable before.  Thanks a lot. I'm using DW8.
    begining code from template:
    <!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="title" --><title>Party Invitation Boutique</title>  <!-- TemplateEndEditable -->
    begining code from new pages:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="/Templates/index.dwt" codeOutsideHTMLIsLocked="false" -->
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- InstanceBeginEditable name="title" --><title>Baby Blue</title>  <!-- InstanceEndEditable -->
    -------------then further down on the page is the editable region-------------
    <!-- InstanceBeginEditable name="main_content" -->
    <div id="content_right">test only can type in design view. can't add div boxes
      even in this editable region. ugh. can't even type next this this text in the
      code view. </div>
    <!-- InstanceEndEditable -->

    Best thing you can do in the future is run your code through the validator if the editable region exists:
    http://validator.w3.org/
    If there are code errors with other tags on the page then it is possible DW is overlooking its own template code.  Unfortunately without seeing the whole page I cannot say this is definitely the case, but a likely possibility.

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

  • Template changes in editable region do not propagate to child pages??

    I have a website that was created using Dreamweaver CS4. I have copied the directory onto a machine running CS6 and set it up as a new site in DW. I want to make a change in the editable region of a template that feeds all the pages. However, when I make the change it appears to go through the motion of propagating the change across all the pages, but in fact - when checking 'detail' of the process - all it seems to be doing is identifying the child pages but not updating them. No changes occur. Any ideas? I did not have this problem previously, as far as I remember.
    Code snippet follows. I'm trying to add the phone number shown in BOLD below.
    Thanks for any help!!
    John
    <body class="twoColFixLtHdr">
    <div id="container">
    <div id="header">
        <h1><!-- TemplateBeginEditable name="EditRegion6" --><img src="../Graphics/TCMG Banner_Small3.jpg" alt="" name="Banner_Small" width="1000" height="100" border="0" usemap="#Banner_SmallMap" id="Banner_Small" /><!-- TemplateEndEditable -->
          <map name="Banner_SmallMap" id="Banner_SmallMap">
            <area shape="rect" coords="0,-6,103,97" href="/index.html" alt="Home" />
          </map>
        </h1>
        <!-- end #header -->
      </div>
    <!-- TemplateBeginEditable name="EditRegion_SdBar" -->
    <div id="sidebar1">
    <h3 class="Sidebar_Phone">OFC: +1 (704) 944-XXXX</h3>
      <h3 class="Sidebar_Phone"><strong>CELL: +1 (305) 283-XXXX</strong></h3>
      <hr />
    <h3 class="Sidebar_Title">Sidebar1 Content</h3>
      <ul>
        <li class="MainContent_Text">The background color on this div will only show for the length of the content. If you'd like a dividing line instead, place a border on the left side of the #mainContent div if it will always contain more content. </li>
        <li class="MainContent_Text">Donec eu mi sed turpis feugiat feugiat. Integer turpis arcu, pellentesque  eget, cursus et, fermentum ut, sapien. Fusce metus mi, eleifend  sollicitudin, molestie id, varius et, nibh. Donec nec libero.</li>
      </ul>
      <!-- end #sidebar1 -->
    </div>
    <!-- TemplateEndEditable -->

    Correct Ken.
    The content in editable regions of a DW Template are editable on a page by page basis in all child pages. Any content in an editable region in a Template will not propagate to child pages.
    Anything in a non-editable region of a Template can only be edited in the DW Template and those changes will propagate to child pages when the Template is saved.

Maybe you are looking for

  • Error "XML tag Main/@versionMinor has incorrect value 001; expected value."

    I'm going to describe our scenario. We have created an Abap proxy in a BW system to run a XI interface. The abap proxy in BW is connected to the IE of a XI 3.0 system. That scenario runs without problems with BW 3.5 (basis 6.40). Now, we are migratin

  • A proxy and in that proxy we will call the BAPI for creating Purchase Requi

    HI all, I am explaining a situation please resolve if possible. I got source data to create purchase requisition .  the source data was not cleaned and requires lot of validations and crossmapping with actual sap tables . I did it for testing and use

  • TS2972 Slow streaming home sharing

    In my configuration, I purchase and download TV shows on to my Mac mini. I then stream to my iPad or APple TV using Home Sharing. Everything was working fine until I upgraded OSX on the Mini. Despite all my devices being on the same network and all h

  • Derivation through "Move" in COPA

    Hi Experts Iam trying to derive relationships to avoid "unassigned data" in COPA. I have derivation between customer and salesman, sales office but this is not automatic, at the time of customer creation, the derivation rule has to be maintained in t

  • Can anyone get these to work??!!??!!  Airports don't work well together

    I have two airport expresses. I bought the second one to extend the range of my existing airport network. Both airports work fine when configured as a standalone main base station. But, when I set one up to be a remote/relay station, performance on b