Optional Editable Regions

In a  two column fixed, left sidebar, header and  footer layout I've designated the sidebar as an "optional editable region." My intent is for the sidebar to have no content on some pages, and on those pages to have the main content region fill the entire page. However, when the sidebar is empty it still occupies 200px on the left of the page. Are there any suggestions on how to have the sidebar completely disappear when there is no content in it?
Thanks.

Hi Nancy,
Thanks for your reply.
I took a quick look at your code, but it will require some time to analyze.
In the meantime I'll try and answer your question and provide some
additional description.
I'm experimenting with a new file before touching my real code and so the
file is the standard vanilla layout from DW CS4 - two column fixed, left
sidebar, header and footer. The CSS is the default generated by DW. Here's
the layout:
I've designated the sidebar as an optional editable region. On some pages I
don't intend to place contents in this region and would like it "disappear"
and have the main content region occupy the entire page. On other pages I'd
like to insert content into the sidebar and have it appear. However, even
though I have no content in the sidebar it still appears to occupy the first
200px of the page and push the main content over.
Steve

Similar Messages

  • Optional editable regions in head

    I'm trying to create a master template that will enable me to
    include or not include cross-fading photographs in pages based on
    that template.
    I know that with DW8 I can insert an editable region in the
    <head> (ie for description, keywords).
    I know that with DW8 I can insert an optional region in the
    <body> to show/hide content.
    But can I insert an optional editable region in the
    <head>?
    I want to have the option of including a javascript file in a
    <script> tag in the <head> of pages created from the
    template and if I exercise the option to include it in the
    <head>, I also want to be able to edit and change the name of
    the javascript file.
    All the help I've seen only talks about optional regions in
    the <body>.
    Do I use optional editable regions for this, or do it some
    other way?
    Urgent help appreciated - I'm stuck!
    DW8 | XHTML | CSS

    > But can I insert an optional editable region in the
    <head>?
    Not by way of the DW user interface, no.
    But if you have a parameter called optionJS, with a type of
    URL, and a
    default value of "" (i.e., null), you could have this in your
    template
    document's head -
    @@(optionJS==""?'':'<script src="'+optionJS+'"
    type="text/javascript"></script>')@@
    Then in each child page, as long as you leave the parameter
    alone, no script
    tag is written to the head. But to get the script tag, you
    would just use
    MODIFY | Template Properties, select the optionJS parameter,
    and browse to
    and select the desired script file, and it'll be there....
    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
    ==================
    "Digihound" <[email protected]> wrote in
    message
    news:[email protected]...
    > I'm trying to create a master template that will enable
    me to include or
    > not
    > include cross-fading photographs in pages based on that
    template.
    >
    > I know that with DW8 I can insert an editable region in
    the <head> (ie for
    > description, keywords).
    >
    > I know that with DW8 I can insert an optional region in
    the <body> to
    > show/hide content.
    >
    > But can I insert an optional editable region in the
    <head>?
    >
    > I want to have the option of including a javascript file
    in a <script> tag
    > in
    > the <head> of pages created from the template and
    if I exercise the option
    > to
    > include it in the <head>, I also want to be able
    to edit and change the
    > name of
    > the javascript file.
    >
    > All the help I've seen only talks about optional regions
    in the <body>.
    >
    > Do I use optional editable regions for this, or do it
    some other way?
    >
    > Urgent help appreciated - I'm stuck!
    >
    > DW8 | XHTML | CSS
    >
    >

  • Editable region

    Help! Is there a way to limit an editable region to a fixed size?
    I have a pretty simple design sliced into four pieces: Header, horizontal navbar, main body, footer. I've made the mainbody into an editable region. But if I add more text that the exact size of the mainbody divtag, my page breaks apart wehre the mainbody and footer meet.
    I have gone into CSS and typed in the height dimension in the div (#wrapper #mainBody #mainContent), but it didn't make a difference. When I added it to the paragraph div (#wrapper #mainBody #mainContent p), the type went crazy.
    I've spent hours trying to work this out. I'm now considering just working around this -- ie, inserting content until I see the page breaks up. But there must be a simpler and safer method to do this.
    Many thanks to anyone who can help. CSS and HTML coding is below:
    @charset "UTF-8";
        padding: 0px;
        margin-top: 0px;
        margin-right: auto;
        margin-bottom: 0px;
        margin-left: auto;
    #wrapper {
        background-color: #999;
        width: 800px;
    #wrapper #header {
        background-color: #999;
        height: 150px;
        width: 800px;
    #wrapper #navBar {
        height: 50px;
        width: 800px;
        background-image: url(../template%20images/navBar.jpg);
        margin: 0px;
    #wrapper #mainBody {
        height: 990px;
        width: 800px;
        background-image: url(../template%20images/body.jpg);
    #wrapper #footer {
        background-image: url(../template%20images/footer.jpg);
        height: 60px;
        width: 800px;
    #wrapper #mainBody #mainContent {
        padding-top: 25px;
        padding-right: 80px;
        padding-bottom: 0px;
        padding-left: 80px;
        margin-bottom: 0px;
        font-family: Arial, Helvetica, sans-serif;
        font-size: 14px;
        height: 965px;
    #wrapper #mainBody #mainContent p {
        height: 0px;
        margin: 0px;
    #wrapper #footer #pageNumber {
         font-size: 18px;
         font-weight: normal;
         padding-top: 10px;
         text-align: center;
         font-family: Arial, Helvetica, sans-serif;
    HTML:
    <body>
    10
    <div id="wrapper">
    <div id="header"><img src="template images/header.jpg" width="800" height="150" alt="project name" />
    </div><!--close header-->
    <div id="navBar">
      <ul id="MenuBar1" class="MenuBarHorizontal">
        <li><a href="#">home</a>      </li>
        <li><a href="#">about</a></li>
        <li><a href="#">menu</a></li>
        <li><a href="#">contact</a></li>
        <li><a class="MenuBarItemSubmenu" href="#">index</a>
          <ul>
            <li><a class="MenuBarItemSubmenu" href="#">Homeland</a>
              <ul>
                <li><a href="#">submenu</a></li>
                <li><a href="#">submenu</a></li>
              </ul>
            </li>
            <li><a href="#" class="MenuBarItemSubmenu">subject here</a>
              <ul>
                <li><a href="#">submenu</a></li>
              </ul>
            </li>
            <li><a href="#">submenu</a></li>
          </ul>
        </li>
    </ul>
    </div><!--close navBar-->
    <div id="mainBody">
    <div id="mainContent"> <!--Begin editable region-->
      <!-- TemplateBeginEditable name="2000Template1" -->
      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed nisl metus, aliquam et ultricies vitae, faucibus ut libero. Fusce molestie lectus nunc, vel interdum leo. Nunc gravida mattis leo, a laoreet felis tincidunt eget. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Donec et sapien in felis consequat vestibulum eu ac felis. Praesent pellentesque dolor vel mi euismod eget ultrices velit dignissim. Duis erat urna, aliquam vel malesuada eu, sollicitudin vel ante. Maecenas vitae dui nisi, ac molestie dolor. Suspendisse non neque odio, et dapibus lacus. Pellentesque bibendum justo non turpis tempor a porta risus pharetra. Etiam a felis quis orci molestie aliquet. Phasellus aliquam lacus sed magna venenatis et accumsan justo blandit. Sed id velit turpis. Nunc sit amet placerat libero. Nam sollicitudin, sem ut sollicitudin convallis, dolor tellus volutpat risus, quis lacinia diam purus nec tellus. Quisque at purus euismod lorem semper rhoncus. In hac habitasse platea dictumst. </p>
       <!-- TemplateEndEditable --></div><!--Close editable region-->
    </div><!--close mainBody-->
    <div id="footer">
    <div id="pageNumber"><!--Start optional edit region-->
    <p><< Previous Page 1 : 2 : 3 Continue >></p>
    </div><!--close optional edit region-->
    </div><!--close footer-->
    </div><!--close wrapper-->
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
    </script>
    </body>
    </html>

    Nancy and Paul,
    Many thanks for the quick reply.
    To clarify, I am building a website that will feature a series of essays, so the content is very text heavy. There will be a photo and occasional graphic to break up the text on each page, but otherwise it's just words, words, words. Even with such a large display space (ie, the mainContent <div>, 800x990 px), these essays will run two to five pages long.
    I have not yet gone live, so I cannot post a link. However, I've attached a jpg of the prototype:
    As you can see, I've used a non-repeatable textured background. Hence my problem: The type that I fit into the mainContent cannot run longer than what the <div> allows, as the main content section will not expand. Rather, text runs off the maincontent section and the design breaks where the footer begins (page number at the bottom). I was fooling around with the height rule in a failed effort to create a bottom margin or padding that would stop the type from overflowing.
    So, is there a way I can still work with this? Or as Nancy suggested, is my design too regid for the web?
    Thank you again for your help. I am brand new to webdesign, and am rather befuddled at the moment....
    PS to Gary: The mainContent <div> created a container that gave me my left, right and top padding for the text and photos. (The mainBody <div> margins ran into the black margins on both sides and up to the navBar at the top.)  I had hoped the same <div> would set the bottom padding, too, but it didn't work.

  • Problem with editing Editable Region - HELP!

    My website is www.yucholian.com
    I have created a template and have assigned a main body to be
    an Editable Region. However, I can't seem to use different fonts,
    sizes or styles as I wish. If I go to Text drop down, go to size,
    all options are greyed out. Can anyone help?
    BTW, I'm using 30 day trial.
    I find Dreamweaver to be very finicky. Even something simple
    as applying a template that I created, view doesn't update, showing
    doubles...
    Thanks in advance.

    > I find Dreamweaver to be very finicky. Even something
    simple as applying
    > a
    > template that I created, view doesn't update, showing
    doubles...
    The more you know about HTML, the less you will run into such
    things - but I
    have to say, I have no idea what you are describing here. It
    sounds to me
    like user error, but I can't say for sure.
    > However, I can't seem to use different fonts, sizes or
    styles as I
    > wish.
    Show me your template, tell me what you are trying to change,
    and I'll
    explain to you what is happening.
    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
    ==================
    "yucholian" <[email protected]> wrote in
    message
    news:edk7lr$73m$[email protected]..
    > My website is www.yucholian.com
    > I have created a template and have assigned a main body
    to be an Editable
    > Region. However, I can't seem to use different fonts,
    sizes or styles as
    > I
    > wish. If I go to Text drop down, go to size, all options
    are greyed out.
    > Can
    > anyone help?
    > BTW, I'm using 30 day trial.
    > I find Dreamweaver to be very finicky. Even something
    simple as applying
    > a
    > template that I created, view doesn't update, showing
    doubles...
    >
    > Thanks in advance.
    >

  • 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

  • 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

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

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

  • 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

  • Nesting Templates: Child-Template Pages not Fully Responding to Editable vs. Un-Editable Regions

    M'kay, so first and foremost, all of this is being done within Dreamweaver CS5. How I might explain this is that I have a series of Master-Templates for my website, accompanied then by Child-Templates linked off of / nested from my Master-Templates. So far this is going wonderfully, that is, until I try to make a page from one of my Child-Templates.
    The page from my Child-Template accurately comments-out an un-editable region (Region in which was editable within the Master-Template, but left as ONLY editable within the Child-Template) so long as I add an EDITABLE region WITHIN it. Under the circumstance that I DO NOT add an editable region within the Master-Template's editable region, the region within the Page is still appearing editable.
    For example:
    Master Template:
    <!-- TemplateBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
    <!-- TemplateEndEditable -->
    Child Template:
    <!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
         <!-- TemplateBeginEditable name="ChildPageCSSLinks" -->
              Child PAGE CSS Links Here.
         <!-- TemplateEndEditable -->
    <!-- InstanceEndEditable -->
    Child Page:
    Child Template CSS Links Here. (Accurately appearing Un-Editable - {Master-Template's editable region tags accurately appearing invisible})
    <!-- InstanceBeginEditable name="ChildPageCSSLinks" -->
         Child PAGE CSS Links Here. (Accurately appearing Editable)
    <!-- InstanceEndEditable -->
    This is an example of an editable regions that WORKS. In the Child-Page the "Child Template CSS Links Here." IS appearing commented out and therefore un-editable within the Child-Page, like it's supposed to be. This then allows the "Child PAGE CSS Links Here" to be ACCURATELY editable within the Child-Page.
    Now for an example of what DOESN'T work:
    Master Template:
    <!-- TemplateBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
    <!-- TemplateEndEditable -->
    Child Template:
    <!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
         (As you see, I have NOT added an additional editable region within this Master-Template's editable region. This is an area that is ONLY supposed to be editable within the Child-Template and NOT the Child-Page, which SO FAR appears to be accurate.)
    <!-- InstanceEndEditable -->
    Child Page:
    <!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
         Child Template CSS Links Here.
         (For some reason, ONLY so long as I DO NOT add an additional Child-Template-editable-region within this Master-Template's editable region, this area is STILL appearing visible as well as editable within the Child-Page.)
    <!-- InstanceEndEditable -->
    So, under this circumstance, it seems that the only way I can leave a Master-Template's editable region ONLY editable within the Child-Template and NOT editable within the Child-Page is by leaving an ADDITIONAL editable region produced via the Child-Template somewhere within EVERY SINGLE editable region produced via the Master-Template. Unless I am doing something seriously wrong, this so far appears to be a potential defect/bug within Dreamweaver CS5. I can't imagine how this would be accurate, otherwise Child/Nested-Templates would not be possible to make. What might I be doing wrong? Is there any way that I can specify in the Master-Template that an Editable Region is ONLY Editable within the Child-Template and NOT within further Child-Pages (A Page based off of the Child-Template)? Or perhaps is there a way that I can specify in the Child-Template that an editable region WILL NOT be editable within the Child-Page? Furthermore, no, I DO NOT want to make them "Optional Regions," so please do not suggest that.
    I know that this is all probably a bit confusing, but hopefully the examples above will help more than the descriptions aside. As you can probably assume, this is definitely a HUGE complication within my website if there doesn't end up being a solution, especially with all the time I have put into making the Child-Templates that I hope to rely on. It really would be a bit ridiculous if I had to script-in an additional editable region within every single Master-Template-editable-region available within my Child-Template just so that I may update my Child-Template, furthermore allowing my edits to drop down to my Child-Pages, especially since it would maintain content that I never wanted to be editable within the Child-Page in the FIRST place.
    Some help would be sincerely appreciated, and as soon as possible, if I might ask politely.
    Thank you. Sincerely,
    ~ Miss Cat

    =____= I cannot believe that I am saying this, after writing ALL of that up, but thanks to "Dreamweaver CS5 for Dummies," I just learned that if you place: @@(" ")@@ within the Child/Nested Template's editable region that you DO NOT want passed down to your Child-Pages, it won't appear editable. Goodness knows why such an inconspicuous formula was the answer, but I guess whatever works. ...WHY WAS THIS INFORMATION SO DIFFICULT TO FIND?!?!?!?! @____@ Information on Nested Templates in general seems rather difficult to find, however, so I'm glad I figured this out /not ever a full hour/ after writing all this up and posting it. #__#  ...At least my Child-Templates can work thoroughly now, though. So... Scenario FIXED. ^^
    I only hope now that such information will appear helpful to anyone else hunting for this information via Google or other Search Engine in the future. And if there is anything at all that I am still officially missing, then do feel free to add it to the feed and let me know, because the last thing I need right now are more surprise difficulties to equally slow down the productivity of this massive project I've been working on... @___@ ..But so far things seem to be going good. ^^ So I can settle myself unbelievably grateful that there ended up being a solution to this ridiculousness after all.
    Sincerely,
    Miss Cat
    [signature promo info removed by moderator]

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

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

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

  • 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

  • Ahhhhhh!!! I'm going to kill editable regions, help!!

    Why the heck is this happening ... I've searched the code very thoroughly ... every time I attempt to make a new editable region for the background image for my header (Welcome to Prodigy Piano Studios) , every thing I try it just says:
    "This area is already part of an editable, repeating, or optional region"
    So why isn't dreamTAKER allowing me to switch out the background image for my other pages?
    http://www.prodigypianostudios.com
    Each banner photo up top is a specific color ... and I need to switch out the background for the middle part of the body for a gradient image to match the banner color. 
    Please help!!
    Thanks!!

    I don't know much about DW templates but checking your page in the validator shows this going on:
    <td width="960" height="120" td>
    It doesn't like that and I supose there's a chance that the problem in there (the rougue td at the end) is screwing your tags.
    Martin

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

  • Hide the 'Show All' option in Region Selector

    Hi there,
    I just searched this forum and came to know that we can hide the show all option in region selector using jQuery as suggested by VC.
    $('ul[id$="_RDS"]').children('li').each(function(i, e){
    if ($(e).text()=='My Tab') {
    $(e).find('a').click();
    Any idea where this jQuery needs to be inserted?
    thanks.
    Sun

    Hi VC,
    <table class="tbl-body" cellspacing="0" cellpadding="0" border="0" summary="">
        <tbody>
          <tr>
            <td class="tbl-main" width="100%"><div class="apex-rds-container"><ul id="3388023453317532_RDS" class="apex-rds"><li class="apex-rds-first apex-rds-selected"><a href="#SHOW_ALL"><span>Show All</span></a></li><li><a href="#R3065313453780541"><span> MASTER DATA</span></a></li><li class="apex-rds-last"><a href="#R3375830763272358"><span>Edit  Data Dump</span></a></li></ul></div><div class="rounded-corner-region" id="R3065313453780541" >
      <div class="rc-gray-top"><div class="rc-gray-top-r">
        <div class="rc-title"> MASTER DATA<a class="eLink" title="Edit" href="javascript:popupURL('f?p=4000:374:132::::P374_ID,FB_FLOW_ID,FB_FLOW_PAGE_ID:30653,129,1');" tabindex="999"><img src="/i/e.gif" alt="Edit" class="eLink" /></a></div>
      </div></div>
      <div class="rc-body"><div class="rc-body-r">
    <div class="rc-content-buttons"><button value="Reset" onclick="apex.submit('RESET');" class="button-default" type="button"  id="B3068426845780551">
      <span>Reset</span>Anything specific that you want me to paste? Lots of content in the actual HTML source.
    thanks,
    Sun
    Edited by: sun1977 on May 29, 2012 5:50 AM

Maybe you are looking for

  • "Can not get a key" error when assigning the OAuthTokenIssuer certificate

    I am migrating from Lync Server 2010 to 2013. When deploying the 2013 server, it fails when assigning the OAuthTokenIssuer certificate. With the KeyException error below. I've tried "re-keying" the cert and confirmed that the key is exportable. Does

  • KE28 - Selection Criteria and Processing

    Hello Expert, we  will need, when we are executing transacction ke28 that  it runs  this process  excluding some products or this does not consider some records I review some recomendations but I dont found one solution. 1.   http://scn.sap.com/threa

  • Making a full StageWebView that resizes

    I'm having a lot of trouble getting a stagewebview to resize when the device is rotated. I don't understand how to get stage not null. How do you get the dimensions below the top navigation bar? (fxp file) <?xml version="1.0" encoding="utf-8"?> <s:Vi

  • Re: Satellite Pro 40 Synaptic Pointing device not working properly

    Good morning, I have a brand-new Satellite Pro L40 and the Synaptic mousepad has stopped operating. When I go to COntrol Panel > Mouse I get a message teling me that the system is "Unable to connect to the Synaptic Pointing Device Driver. I haven't i

  • Error: Inconsistent currency information J2I8

    Hi Experts, We are capturing the balance 50 % credit on capital goods using T-code J2I8 we are getting below error Inconsistent currency information Message no. F5725 Diagnosis Company code '6202' has currency type '10'. This currency type has the cu