Editable Region going Crazy

Good Morning All,
I have created a template that I can use for several pages.
I added a layer so I can place my editable region, I have try
to move the editable region but it adds where my cursor is located.
Can I resize editable regions and move them in place? (it
does not let me do it)
Is there a editable region options, will it be locked that
prevents me moving it and placing it in the possition I want.
Did I did this correctly by adding a layer in the main
template and placing the editable region inside that layer? (when I
add text it wont follow the pages margins, meaning if I resize my
browser it will just stay as is)
I try by using one of the prebuilt templates in dreamweaver
8, and it does the same thing, It wont let me possition that
editable region where I need it to be...
Thanks so much for any help.

> I have created a template that I can use for several
pages.
> I added a layer so I can place my editable region, I
have try to move the
> editable region but it adds where my cursor is located.
What?
> Can I resize editable regions and move them in place?
(it does not let me
> do
> it)
It seems you are thinking of template regions as if they were
layout
devices - they are not. They are sized to contain whatever
you put into
them. The size that you see them render in Design view has no
effect on the
layout whatsoever. They are rendered within the container
into which you
place them, so, if you want to move one, delete it and then
re-insert it.
> Did I did this correctly by adding a layer in the main
template and
> placing
> the editable region inside that layer?
You can place editable regions inside any HTML element that
can otherwise
contain page content.
> (when I add text it wont follow the
> pages margins, meaning if I resize my browser it will
just stay as is)
Of course - that's how absolutely positioned elements behave
(layers).
> I try by using one of the prebuilt templates in
dreamweaver 8, and it does
> the
> same thing, It wont let me possition that editable
region where I need it
> to
> be...
You 'position' an editable region by positioning its
container, e.g.,
If you put it into an absolutely positioned div (Layer) then
you would place
that div where you want the content to appear on the page.
If you put it into a table cell, then you would structure the
table so that
the cell appears where you want it on the page.
Get it?
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
==================
"Dreamerinweaver" <[email protected]> wrote
in message
news:[email protected]...
> Good Morning All,
>
> I have created a template that I can use for several
pages.
> I added a layer so I can place my editable region, I
have try to move the
> editable region but it adds where my cursor is located.
>
> Can I resize editable regions and move them in place?
(it does not let me
> do
> it)
>
> Is there a editable region options, will it be locked
that prevents me
> moving
> it and placing it in the possition I want.
>
> Did I did this correctly by adding a layer in the main
template and
> placing
> the editable region inside that layer? (when I add text
it wont follow the
> pages margins, meaning if I resize my browser it will
just stay as is)
>
> I try by using one of the prebuilt templates in
dreamweaver 8, and it does
> the
> same thing, It wont let me possition that editable
region where I need it
> to
> be...
>
> Thanks so much for any help.
>

Similar Messages

  • 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

  • When using Live View, site looks great, browser testing goes crazy

    I am creating a new website (and I am really unexperienced with Dreamwaver CS5).  But when I check my site using "Live View" everything looks great, the way it is supposed to.  Then when I go to test it in my browswer (Primary browser is Chrome) it goes crazy:  I at first noticed that I had saved one copy as an .asp but then resaved it to .xhtml  I did delete the first line of code already that the .asp file created as it kept giving me an error on line 1.
    Then I tried to do a spry drop-down menu bar, which I have deleted since I thought I was doing something wrong with that and I should just stick to what I half-way know.
    If I were to preview the template page it gives me this error:
    This page contains the following errors:
    error on line 150 at column 76: error parsing attribute name
    Below is a rendering of the page up to the first error.
    Here is line 150:
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    If I were to test the index.xhtml page in the browser, it ignores most images (all but one), and the first nav-bar (an editable region) appears to the left instead of under the header.  The layout is totally ignored and everything is on the left-hand side of the screen instead of in a two column layout.
    I am not testing this on a server just off of my computer.
    I am assuming that the error has something to do with the .asp file I first did and when I resaved it, since I don't know what I would be looking for, is still in there screwing it up.
    Here is the code from the template page:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Midwest Window Brokers | Page</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    <style type="text/css">
    <!--
    body {
              font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
              margin: 0;
              padding: 0;
              color: #000;
              background-image: url(/images/bkg.jpg);
              background-repeat: repeat;
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
              padding: 0;
              margin: 0;
    h1, h2, h3, h4, h5, h6, p {
              margin-top: 0;           /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
              padding-right: 15px;
              padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
              text-align: left;
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
              border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
              color: #060;
              text-decoration: none; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
    a:visited {
              color: #666;
              text-decoration: underline;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
              text-decoration: none;
    /* ~~this fixed width container surrounds the other divs~~ */
    .container {
              width: 960px;
              background: #FFF;
              margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout */
    /* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
    .header {
              background-color: #FFF;
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
              float: right;
              width: 300px;
              background: #ffffff;
              padding-bottom: 10px;
    .content {
              padding: 10px 0;
              width: 650px;
              float: right;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
              padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
              list-style: none; /* this creates the space between the navigation on the content below */
    ul.nav li {
              border-bottom: 1px solid #666; /* this creates the button separation */
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
              padding: 5px 5px 5px 15px;
              display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
              width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
              text-decoration: none;
              background-color: #DDDECB;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
              background: #ADB96E;
              color: #FFF;
    /* ~~ The footer ~~ */
    .footer {
              padding: 10px 0;
              position: relative;/* this gives IE6 hasLayout to properly clear */
              clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
              background-color: #DDDECB;
              font-size: small;
    /* ~~ miscellaneous float/clear classes ~~ */
    .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. The floated element must precede the element it should be next to on the page. */
              float: left;
              margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
              clear:both;
              height:0;
              font-size: 1px;
              line-height: 0px;
    #h-navbar {
              font-weight: bold;
              height: auto;
              font-size: 18px;
              line-height: 50px;
              background-image: url(/images/navbar2.jpg);
    #h-navbar1 {
              background-image: none;
              background-repeat: repeat-x;
    -->
    </style>
    <script type="text/javascript">
    function MM_preloadImages() { //v3.0
      var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
        var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    function MM_swapImgRestore() { //v3.0
      var i,x,a=document.MM_sr; for(i=0;a&&i<a.length&&(x=a[i])&&x.oSrc;i++) x.src=x.oSrc;
    function MM_findObj(n, d) { //v4.01
      var p,i,x;  if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
        d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);}
      if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
      for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document);
      if(!x && d.getElementById) x=d.getElementById(n); return x;
    function MM_swapImage() { //v3.0
      var i,j=0,x,a=MM_swapImage.arguments; document.MM_sr=new Array; for(i=0;i<(a.length-2);i+=3)
       if ((x=MM_findObj(a[i]))!=null){document.MM_sr[j++]=x; if(!x.oSrc) x.oSrc=x.src; x.src=a[i+2];}
    </script>
    </head>
    <body onload="MM_preloadImages('/images/home2.jpg')">
    <div class="container">
      <div class="header"><a href="/index.xhtml"><img src="../images/heading.jpg" alt="Midwest Window Brokers, Windows, Siding, Roofing, 605-791-5352" name="Insert_logo" width="950" height="200" align="right" id="Insert_logo" style="background: #FFFFFF; display:block;" /></a>
        <div id="h-navbar1"><a href="/index.xhtml"><img src="/images/home.jpg" alt="home" width="159" height="51" id="Image1" onmouseover="MM_swapImage('Image1','','/images/home2.jpg',1)" onmouseout="MM_swapImgRestore()" /></a><a href="/windows.html"><img src="/images/services.jpg" width="151" height="51" alt="services" /></a><a href="/freebay.xhtml"><img src="/images/specials.jpg" width="153" height="51" alt="specials" /></a><a href="/gallery.html"><img src="/images/gallery.jpg" width="152" height="51" alt="gallery" /></a><a href="/roofing.xhtml"><img src="/images/order.jpg" width="152" height="51" alt="order" /></a><img src="/images/blank.jpg" width="75" height="51" /><img src="/images/facebook.jpg" width="38" height="51" alt="facebook" longdesc="http://facebook.com/midwestwindowbrokers" /><img src="/images/twitter.jpg" width="37" height="51" alt="twitter" longdesc="http://twitter.com/midwestwindow" /><img src="/images/google.jpg" width="42" height="51" alt="google+" longdesc="http://https://plus.google.com/u/0/b/108071947231835835141/108071947231835835141/posts" /></div>
      <!-- end .header --></div>
      <!-- TemplateBeginEditable name="navbar" -->
      <div id="h-navbar">
        <div id="h-navbar2">  Content for  id "h-navbar2" Goes Here</div>
      </div>
      <!-- TemplateEndEditable -->
      <div class="sidebar1">
        <ul class="nav">
        </ul>
        <p> <div id="wufoo-z7x3k1">
    Fill out my <a href="http://midwestwindow.wufoo.com/forms/z7x3k1">online form</a>.
    </div>
    <script type="text/javascript">var z7x3k1;(function(d, t) {
    var s = d.createElement(t), options = {
    'userName':'midwestwindow',
    'formHash':'z7x3k1',
    'autoResize':true,
    'height':'601',
    'async':true,
    'header':'show'};
    s.src = ('https:' == d.location.protocol ? 'https://' : 'http://') + 'wufoo.com/scripts/embed/form.js';
    s.onload = s.onreadystatechange = function() {
    var rs = this.readyState; if (rs) if (rs != 'complete') if (rs != 'loaded') return;
    try { z7x3k1 = new WufooForm();z7x3k1.initialize(options);z7x3k1.display(); } catch (e) {}};
    var scr = d.getElementsByTagName(t)[0], par = scr.parentNode; par.insertBefore(s, scr);
    })(document, 'script');</script></p>
        <!-- end .sidebar1 --></div>
      <!-- TemplateBeginEditable name="Body" -->
      <div class="content">
        <h1>Instructions</h1>
        <p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
        <h2>Clearing Method</h2>
        <p>Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule.  This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
        <h3>Logo Replacement</h3>
        <p>An image placeholder was used in this layout in the .header where you'll likely want to place  a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
        <p><span style="font-size: 18px; color: #C00; font-weight: bold; font-style: italic;">Logo Replacement</span></p>
        <p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
        <p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
        <h4>Backgrounds</h4>
        <p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.</p>
        <!-- end .content -->
      </div>
      <!-- TemplateEndEditable -->
      <div class="footer">
        <p class="footer"><strong>  <em>References Available!</em>     We accept cash, check, Visa, Discover, MasterCard</strong></p>
          Copyright 2012 Midwest Window Brokers Inc. All Rights Reserved.
        <!-- end .footer --></div>
      <!-- end .container --></div>
    </body>
    </html>

    I had saved one copy as an .asp but then resaved it to .xhtml 
    I'm assuming this is a static web site.  Rename (F2) all your pages with .html or .htm extension. 
    .xhtml is not a valid extension.
    Nancy O.

  • Kernel 2.6.32-ARCH slows down and syslog-ng goes crazy *

    Hi, it's a month now that randomly my computer slows down.
    I took a look with "iotop" and found that syslog-ng was going crazy writing continuosly to the logfile.
    taking a look at these files i found this message that gets written over and over again:
    ACPI: EC: input buffer is not empty, aborting transaction
    ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424)
    ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.AMW0.WMCA] (Node ffff8800bf4182c0), AE_TIME
    here is my computer info
    2.6.32-ARCH #1 SMP PREEMPT x86_64 Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz GenuineIntel GNU/Linux
    Any ideas on what's causing this error??
    Last edited by .:B:. (2010-09-30 08:21:58)

    Taking a look at dmesg i found this
    ACPI: I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f]
    ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    ACPI Warning for \_SB_.PCI0.PEGP.VGA_.MXMI: Excess arguments - needs 1, found 2 (20090903/nspredef-303)
    ACPI Warning for \_SB_.PCI0.PEGP.VGA_.MXMS: Excess arguments - needs 1, found 2 (20090903/nspredef-303)
    Don't know if it could be of any use..
    here is my dmesg|grep ACPI
    BIOS-e820: 00000000bfd64000 - 00000000bfd9f000 (ACPI NVS)
    BIOS-e820: 00000000bfde3000 - 00000000bfdfe000 (ACPI data)
    modified: 00000000bfd64000 - 00000000bfd9f000 (ACPI NVS)
    modified: 00000000bfde3000 - 00000000bfdfe000 (ACPI data)
    ACPI: RSDP 00000000000f7160 00024 (v02 PTLTD )
    ACPI: XSDT 00000000bfdf47ec 0005C (v01 ACRSYS ACRPRDCT 06040000 INNA 00000000)
    ACPI: FACP 00000000bfde5000 000F4 (v03 INTEL CRESTLNE 06040000 ALAN 00000001)
    ACPI: DSDT 00000000bfde6000 0939E (v02 Intel CANTIGA 06040000 MSFT 03000000)
    ACPI: FACS 00000000bfd9efc0 00040
    ACPI: HPET 00000000bfdfdd86 00038 (v01 INTEL CRESTLNE 06040000 LOHR 0000005A)
    ACPI: MCFG 00000000bfdfddbe 0003C (v01 INTEL CRESTLNE 06040000 LOHR 0000005A)
    ACPI: SLIC 00000000bfdfddfa 00176 (v01 ACRSYS ACRPRDCT 06040000 ANNI 00000001)
    ACPI: APIC 00000000bfdfdf70 00068 (v01 PTLTD ? APIC 06040000 LTP 00000000)
    ACPI: BOOT 00000000bfdfdfd8 00028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001)
    ACPI: SSDT 00000000bfde4000 00655 (v01 PmRef CpuPm 00003000 INTL 20050624)
    ACPI: Local APIC address 0xfee00000
    ACPI: PM-Timer IO Port: 0x408
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Using ACPI (MADT) for SMP configuration information
    ACPI: HPET id: 0x8086a201 base: 0xfed00000
    ACPI: Core revision 20090903
    ACPI: bus type pci registered
    ACPI: EC: Look up EC in DSDT
    ACPI: BIOS _OSI(Linux) query ignored
    ACPI: Interpreter enabled
    ACPI: (supports S0 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 10 *11)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 10 *11)
    ACPI: PCI Interrupt Link [LNKC] (IRQs *10 11)
    ACPI: PCI Interrupt Link [LNKD] (IRQs *10 11)
    ACPI: PCI Interrupt Link [LNKE] (IRQs 10 *11)
    ACPI: PCI Interrupt Link [LNKF] (IRQs *10 11)
    ACPI: PCI Interrupt Link [LNKG] (IRQs 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKH] (IRQs *10 11)
    PCI: Using ACPI for IRQ routing
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 10 devices
    ACPI: ACPI bus type pnp unregistered
    ACPI: SSDT 00000000bfd1aca0 00223 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    ACPI: SSDT 00000000bfd19620 00549 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    ACPI: Lid Switch [LID0]
    ACPI: Sleep Button [SLPB]
    ACPI: WMI: Mapper loaded
    acer-wmi: Acer Laptop ACPI-WMI Extras
    ACPI: Thermal Zone [TZS0] (55 C)
    ACPI: Thermal Zone [TZS1] (56 C)
    ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
    ACPI: I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f]
    ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    ACPI: Power Button [PWRF]
    ACPI: SSDT 00000000bfd1aa20 001CF (v01 PmRef ApIst 00003000 INTL 20050624)
    ACPI: SSDT 00000000bfd1af20 0008D (v01 PmRef ApCst 00003000 INTL 20050624)
    ACPI: Battery Slot [BAT0] (battery absent)
    ACPI: AC Adapter [ADP1] (on-line)
    HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
    ACPI Warning for \_SB_.PCI0.PEGP.VGA_.MXMI: Excess arguments - needs 1, found 2 (20090903/nspredef-303)
    ACPI Warning for \_SB_.PCI0.PEGP.VGA_.MXMS: Excess arguments - needs 1, found 2 (20090903/nspredef-303)
    EDIT:
    keeping an eye on kernel.log, i got these errors before it started going nuts
    Jan 27 12:31:32 deathstar kernel: CE: hpet increasing min_delta_ns to 15000 nsec
    Jan 27 12:32:03 deathstar kernel: CE: hpet increasing min_delta_ns to 22500 nsec
    Jan 27 12:52:55 deathstar kernel: CE: hpet increasing min_delta_ns to 33750 nsec
    Jan 27 13:26:00 deathstar kernel: CE: hpet increasing min_delta_ns to 50624 nsec
    Jan 27 14:01:08 deathstar kernel: ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424)
    Jan 27 14:01:08 deathstar kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.TZS0._TMP] (Node ffff8800bf41c700), AE_TIME
    Jan 27 14:01:09 deathstar kernel: ACPI: EC: input buffer is not empty, aborting transaction
    Jan 27 14:01:09 deathstar kernel: ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424)
    Last edited by z3r0 (2010-01-27 13:03:23)

  • 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

  • Mac Os 10.6.6 update start the fans goes crazy

    Hi to all
    Some months ago (almost a year from now) my mac start to become hot after only a few minutes it started up and the fan goes crazy but I never realize why. I made some search on the internet but the only answer I found was using some software to reduce fan speed. It didn't work. I run the Hardware test but nothing strange. I also took my macbook to an apple certified repair center but they told me that nothing was wrong. I also ask to another repair center but same thing. So I left my macbook as it was with this super fan noise all the time. A quite disturbing thing but there was no solution and for what I'm doing my machine is ok so why change it? (It was the only solution they gave me)
    Last day my hd broke down so I had to replace it. I took my macbook pro a1211 model to an apple repair center they change the hd with a new one.
    So I reinstall everything for the beginning. I took my snow leopard dvd formatted the new hd, installed the os, iWork 2008, iLife 2008, Mamp, CSS Edit, Espresso, Pixelmator and few other application such as Firefox, Camino, Etc...
    I use the macbook with mac os 10.6, because I had to finish some work, and with my big surprise for two days the machine was super silent no fans, no hot body ..... nothing. I never reboot it and still no fans and hot body wow.
    Today I wanted to install the developer kit with ios 4.2 and so I had to update the Mac os x to version 10.6.6 as soon as I made the update after the reboot the fans start again to go like crazy and after 15 minutes of work the macbook body become very hot.
    The question is why?
    Anyone can help me?
    Thanks in advance
    Gianfranco

    HI R C-R.
    The apps i've installed are just a few. Espresso, CSS Edit, MAMP, TextWrangler,Firefox, Camino, Chrome, Opera,BetterZip, Stuffit Expander, Pixelmator, 1Password, Dropbox, Xslimmer, VLC, CyberDuck, littlesnitch, iworks, iLife, wacom tablet driver.
    Nothing more. All the software is updated.
    Here the data but as you can see nothing strange but fans are on at the maximum speed!
    PIDProcess Name % CPU Threads Real Mem Kind Sudden Term.
    ## Firefox 2,1 15 106,3 MB Intel
    ## Activity Monitor 1,2 2 20,0 MB Intel (64 Yes
    ## activitymonitord 0,9 1 1,3 MB Intel (64 No
    0 kernel_task 0,9 57 138,0 MB Intel
    ## Finder 0,3 9 36,1 MB Intel (64 Yes
    81 WindowServer 0,2 5 53,4 MB Intel (64 No
    ## Dock 0,1 3 15,5 MB Intel (64 No
    ## Little Snitch Network Mo 0,1 4 4,4 MB Intel No
    14 configd 0,1 7 3,3 MB Intel (64 Yes
    1 launchd 0 3 1,1 MB Intel (64 bit)
    ## SystemUIServer 0 3 19,5 MB Intel (64 Yes
    ## Apple80211Agent 0 3 9,5 MB Intel (64 No
    ## Safari 0 12 236,2 MB Intel (64 No
    16 distnoted 0 3 1,3 MB Intel (64 Yes
    11 DirectoryService 0 6 4,7 MB Intel (64 No
    ## launchd 0 2 1.000 KB Intel (64 No
    13 diskarbitrationd 0 3 1,4 MB Intel (64 No
    44 mds 0 5 31,4 MB Intel (64 No
    17 blued 0 3 4,7 MB Intel (64 Yes
    10 kextd 0 3 2,5 MB Intel (64 No
    22 securityd 0 2 3,0 MB Intel (64 No
    33 ntpd 0 1 1,1 MB Intel (64 Yes
    34 cupsd 0 3 2,9 MB Intel (64 Yes
    19 mDNSResponder 0 3 2,2 MB Intel (64 No
    35 httpd 0 1 3,9 MB Intel (64 No
    ## UserEventAgent 0 3 5,6 MB Intel (64 Yes
    62 coreservicesd 0 4 18,8 MB Intel (64 Yes
    60 lsd 0 3 3,8 MB Intel No
    ## TextEdit 0 2 12,0 MB Intel (64 No
    57 autofsd 0 2 940 KB Intel (64 Yes
    ## pboard 0 1 832 KB Intel (64 Yes
    ## fontd 0 2 6,4 MB Intel (64 Yes
    51 dynamic_pager 0 1 788 KB Intel (64 Yes
    49 fseventsd 0 13 1,9 MB Intel (64 No
    48 hidd 0 2 948 KB Intel (64 Yes
    46 KernelEventAgent 0 3 988 KB Intel (64 Yes
    45 loginwindow 0 2 8,2 MB Intel (64 No
    42 RFBRegisterMDNS 0 2 1,7 MB Intel (64 Yes
    ## mdworker 0 3 11,2 MB Intel (64 No
    ## TextWrangler 0 3 27,9 MB Intel No
    38 usbmuxd 0 3 1,6 MB Intel (64 Yes
    36 krb5kdc 0 2 1,9 MB Intel (64 Yes
    ## Preferenze di Sistema 0 2 25,7 MB Intel (64 Yes
    97 coreaudiod 0 3 3,2 MB Intel (64 No
    ## WebKitPluginAgent 0 2 992 KB Intel (64 Yes
    ## mdworker 0 4 3,1 MB Intel (64 No
    ## TabletDriver 0 2 4,4 MB Intel (64 No
    ## ConsumerTouchDriver 0 2 5,5 MB Intel (64 No
    84 cvmsServ 0 1 856 KB Intel (64 Yes
    ## iTunesHelper 0 3 2,8 MB Intel (64 Yes
    83 httpd 0 1 620 KB Intel (64 bit)
    ## AppleSpell.service 0 2 7,0 MB Intel (64 Yes
    15 syslogd 0 4 684 KB Intel (64 No
    ## 1PasswordAgent 0 2 9,3 MB Intel (64 No
    12 notifyd 0 2 596 KB Intel (64 Yes
    ## Little Snitch UIAgent 0 3 5,9 MB Intel No
    ## Quick Look Helper 0 6 8,6 MB Intel (64 Yes
    ## PenTabletDriver 0 3 9,3 MB Intel (64 No
    ## Agente base AirPort 0 3 5,5 MB Intel (64 Yes
    ## AppleVNCServer 0 4 3,7 MB Intel (64 Yes

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

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

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

  • Templates in DW CS5.5 and editable regions

    I have a template page that has an editable region defined as follows:
    <div class="sidebar1">
        <nav>
          <ul>
            <li><a href="#">Home</a></li>
            <li><a href="#"></a></li>
            <li><a href="#"></a></li>
            <li><a href="#"></a></li>
            <li><a href="#">Members Only</a></li>
            <li><a href="#"> Gallery</a></li>
            <li><a href="#">Constitution</a></li>
            <li><a href="#">Links</a></li>
          </ul>
        </nav>
        <!-- InstanceBeginEditable name="all" -->
    </div>
          <!-- end .sidebar1 -->
      <article class="content">
        <h1>BCEF Clubs</h1>
        <section>
    other code goes here
    </section>
    <!-- InstanceEndEditable -->
    Note the </div> tag  after the start of the editable region. This is a proper tag, as it is needed to close the sidebar1 div.
    When it is not in an editable region, the </div> does not show up in yellow in design veiw and it works in every repect.
    When the editable region is introduced, the </div> shows yellow in design view, and it works in every respect.
    It validates using the W3C validation page.
    Pages built with it also show the tag as yellow but they do not display it when live or in a browser.
    If I delete the </div> as dreamweaver suggests, the css breaks and the page will not work.
    It seems that DW thinks that this is an illegal tag. If I click my mouse on the <!-- InstanceBeginEditable name="all" --> tag, and collapse the tag, all the code in the editable region + that in the sidebare 1 div, ( even that before the editable region begins) collapses. The editable region does not allow edits in the sidebar1 code outside the region.
    I need to put the editable region within part of the sidebar 1 div so that I can add aditional floated items in the sidebar 1 div if needed later.
    Is this a bug or am I missing something?

    This would make more sense.
    </nav>
    <!-- InstanceBeginEditable name="sidebar1" -->
    <p>Some unique sidebar1 content goes here</p>
    <!-- InstanceEndEditable -->
    </div><!-- end .sidebar1 -->
    <article class="content">
    <!-- InstanceBeginEditable name="content" -->
    <h1>Unique heading here</h1>
    <section>
    other code
    </section>
    <!-- InstanceEndEditable -->
    </div> <!--end .content-->
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    Message was edited by: Nancy O.  Forgot to close the .content div.

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

  • Can't edit any editable region but the first one!

    I have a CSS layout and I am trying to edit documents that
    are based on a template that has CSS only layout, the only Editable
    Region I can edit from within Dreamweaver seems to be the first
    one, with a Flash object in it, all the other ones I can
    double-click until I am blue in the face and I cannot get DW to let
    me into edit the area, it's driving me crazy.
    What can I do to fix this!
    Please help.

    Show me the template, please.
    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
    ==================
    "edoggie" <[email protected]> wrote in
    message
    news:eak466$54e$[email protected]..
    >I have a CSS layout and I am trying to edit documents
    that are based on a
    > template that has CSS only layout, the only Editable
    Region I can edit
    > from
    > within Dreamweaver seems to be the first one, with a
    Flash object in it,
    > all
    > the other ones I can double-click until I am blue in the
    face and I cannot
    > get
    > DW to let me into edit the area, it's driving me crazy.
    >
    > What can I do to fix this!
    >
    > Please help.
    >
    >

  • Help with template locked and editable regions

    I have been using templates for years in a very simplified way, my programing skills are not great. Today I seem to have screwed up a template beyond my ability to fix it and possibly all 46 pages attached to it (have not uploaded any of these files though).
    The body tag needs to be editable because of the preload images that are part of the tag. The next section needs to be editable for content which is different on all pages. The last part is a table with text navigation to each page which needs to be locked so I can change it from one place.
    DW keeps inserting an extra body tag and putting an end body tag after the editable content region (before the locked table), depending on where I try to put the tags. Then it won't let me change areas of the content on individual pages and it's not displaying the bottom nav table (although it does show up in safari, but I know the code is wrong).
    Basically what I would like to do is simply have the whole body region editable, except for the one table toward the bottom of each page. Can I do this with out having any content thrown off my pages? I really don't know what code to post at this point since it's all in various stages of "not-working", but the version I am using is DW8.
    Here is a link to an online page which might help you see what I am talking about, this is from before I started trying to change the template:
    http://www.janosklanyi.com/dresden.html
    Thanks,
    Kaylee

    Hi, AZ,
    Templates imply locked regions and editable regions...usually WITHIN the body, so having the entire body editable might be what is throwing things  off.
    It is possible to make attributes of tags editable, but I don't believe that is supported in DW8. You would make the body tag editable so that the id can be changed to match the page (#contactuspage, #homepage, etc.), and by doing that you can focus your CSS on each page. I use that technique to influence the navigation to highlight the page that I am on (of course, I also put ids on the nav links, viz. #contactus, #home, etc., and #contactus2, #home2, etc. for the footer links). All these you would style in the CSS file. I'm pretty sure you can't pass actual content that way yet, but you can define background images.
    I see that you are doing that sort of thing in your pages.
    While you are in the template, look at the code just before the <body> tag. There should be something that says
    <!-- InstanceBeginEditable name="head" -->
    <!-- InstanceEndEditable -->
    </head>
    Copy the two commented lines and change the word "head" to "body" [<!-- InstanceBeginEditable name="body" -->]. Then put the BeginEditable line just before the <body> tag and the EndEditable line just after it. That should leave your body tag open for editing in Code View. Remember, all you want editable here is the <body> tag, not the whole <body> of the document.
    Be sure to add editable regions in the rest of the page, controlling them as you wish.
    At any rate, have courage...once you have fixed your template, the other 46 pages will fall into line!
    Understand that I am working in DWCS4, so I don't know how this is going to work in DW8. Hopefully, it will work fine.
    (Have you considered upgrading to CS4? You may still be able to do that from DW8 at an upgrade price.)
    Z

  • Spry tool tip does not work in template or child pages within an editable region. Why not?

    Ok. so I am getting pretty frustrated. I take the time to learn how to use CSS and to create a template page for a Contractor Site (www.ContractorInsurance.net). The idea is to create a page that I can use for different classes of Contractors...right?
    Then I get all happy about being able to insert ToolTip onto pages to help the user. Great!
    LIfe to turn to Sorrow after nearly five hours of searching for a "eeking" answer.
    So what good does it do to have an Editable region to update if we cannot have the flexibility to insert a tool tip on child pages?  Ok so the fast solution is to what... Have a question mark image, insert another apDiv, name it toolTip_Not and provide it with a show=hide behavior?
    RRRRRrrr...
    This really sucks not being able to find a solution within a reasonable amount of time.

    I have tried thank you. However...it is still not working.
    www.ContractorInsurance.net/course_of_construction.php
    The error message is "Making this change would require code that is locked by a template translator"
        Re: Spry tool tip does not work in template or child pages within an editable region. Why not?
        created by altruistic gramps in Spry Framework for Ajax - View the full discussion
    If you have a look at the following simple document with a tooltipTooltip trigger goes here.
    Tooltip content goes here.
    you will notice that a couple of lines have been placed in the HEAD section of the document. When using DW templates, the HEAD section is usually not editable, hence the error mesaage. By default, your template should have an editable region in it just before the closing tag. It looks like this: <!-- TemplateBeginEditable name="head" > <! TemplateEndEditable --> Dreamweaver should be able to find that editable region and insert the
    <script> tag there automatically. Because you don't have an editable region like that in the <head>, open the master template, and paste the code above just before the closing </head>
    tag. Gramps
    Edited to remove personal data

  • DWCS3 Template Editable Regions and Editable Attributes?

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

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

  • "locked by a template or translator" in Editable Region - CS4

    Hello,
    I am working on a series of ASP homepages using repeating regions in Dreamweaver CS4. However, I am encountering "Making this change would require changing code that is is locked by a template or translator. The change will be discarded." errors.
    On each homepage, I have two levels of nested repeating regions set up as "slides" (Top level) that contain "news blurbs".
    Inside each news blurb repeat instance is an editable region.
    A version of the news spotlight markup can be found at http://www-personal.umich.edu/~pborisov/etc/snippet.html
    When I attempt to  add any new paragraphs inside a news item (<li class="blurb"></li>) in design mode, I get
    an error message telling me that the area is locked by a template and/or translator. However, I can still type additional text
    into pre-existing paragraphs, as well as insert images. Attempting editing in code view works also works.
    Individuals that will be updating each page are going to be using design mode, so I can't go for the obvious work-around. I have no idea why the error keeps occurring. Could anyone clarify this?
    Fixes suggested in other threads that haven't worked:
    making sure the page has valid markup ( passes XHTML 1.0 Transitional)
    ensuring that the region is marked as editable ( it is editable )
    Current ideas as to potential causes:
    something I missed in the code that's triggering dreamweaver to throw errors
    nested repeating regions are somehow creating the issue
    I am mostly sure that ASP is not causing this, as I have been able to reproduce the issue in an XHTML-only child page of the same template.
    Thank you for your help,
    Pabori

    When the code looked like this, my editable regions were locked when I made a page off the template.
    <p><strong><!-- TemplateBeginEditable name="EditRegion3" -->EditRegion3<!-- TemplateEndEditable --></strong></p>
    <p><strong><!-- TemplateBeginEditable name="EditRegion4" -->EditRegion4<!-- TemplateEndEditable --></strong></p>
    When I changed it to this, it worked fine.
        <!-- TemplateBeginEditable name="EditRegion3" -->EditRegion3<!-- TemplateEndEditable -->
        <p> </p>
        <!-- TemplateBeginEditable name="EditRegion4" -->EditRegion4<!-- TemplateEndEditable -->
    I think it didn't like the <p></p> because it is a block element.
    It didn't like <strong></strong> either, but I'm not sure why.
    I am struggling with this myself so I hope you can let me know how this works.

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

Maybe you are looking for

  • Need help Setting up Multiple Static Ip , 1 for each port of the fios router

    Need help Setting up multiple Static Ip on my fios router I have been trying to figure out how to set up multiple ip in my fios router. However I kind of managed how to set up multiple static ip However the way I want it is for each port of my router

  • Problem while using select

    I am using the <select>[ tag to display a pull down in my jsp.. I have a menu bar which has another pull down...When i try to select something from the menu if there is a select pull down below it then the select pull down overlaps the menu pull down

  • How change the name

    Dear all In tcs certificate we want change the full name-xyz designation-xyz then we have go to the se71 then j_1iewt_cert then change the name and desgination show the change but when we taken a tdc print out shows a old one how we can change please

  • I can't open ftp url's in safari

    safari can't open ftp:// url's such as ... ftp://www.apcmedia.com:21/salestools/STRH-6D5PA3R0EN.pdf i've tried with and without "use passive ftp mode" in network settings / proxies. i always get ... Safari can’t open the page “ftp://www.apcmedia.com:

  • Unhappy With Change To the Calendar With iOS7!

    I am very unhappy with the change to the calendar since I updated to iOS7! It took away the ability to change a previously entered all day event to a start & finish time! I am a single parent with three kids & live by my calendar! I put all day event