Templates, backgrounds and editable regions.

A simple question with, hopefully, a simple answer!
I designed a site that uses a background image (800 x 600) with links mapped offshore. So far so good. I then added an editable region, and in fact a model. My problem is the positioning of parts. My background image is set to the absolute center, but the combo box takes its location between the corner of the screen, not the background, so continues to move in different size screens. Is there a way to anchor the editable region in the background, so when one moves, the other not?

Thanks in advance,

Hmm, tried, and everything went to pot. But after combining the first two sets of advice, everything works fine. Thanks for the help.
P.S. I don't know the size, will sort that and other small pieces now, the site works!

Tags: Dreamweaver

Similar Questions

  • Templates and editable regions < body >

    I have a model for the site with all the div, as I would like.

    If I area-editable regions, then where it says < body > in the template - it can be changed in a single page to say

    < body onload = "DoThis (); ">

    because as soon as you open the template, it is up to the page back to the < body > and the onload bit is lost.

    I wanted to use templates to maintain consistency, but when you have problems with the editable regions all the time that I wonder if this is a feature implemented there to help or harm us.

    I tried to put the tabs html in an editable area, but then the said model id had not.

    Please how can I do the < body > tag editable in the various documents because I want this function to launch the load on one page only.

    The only way around this would be to have an onload for each page and have only a function empty on the pages that is not required, but it's unprofessional.

    I think that there is another thing like document.ready but don't know where to put it in the document, and if it is as effective.

    THANK you for any comments.

    TERRY

    Try this, you can use it in any region can be changed as thesection of the page.

  • How to remove the template and editable regions?

    Hello world

    I posted this question earlier in the area of discussion web to ignore a specific Dreamweaver forum. Sorry for posting in two places.

    Since last week, I learned Dreamweaver CS4 to an on-line tutorial. I got to the place where I have generated a model (index.dwt) homepage (index.html) and created boxes on it. At that moment, I realized that I had done all the steps of the Rota and that he didn't really absorb what I was doing. I wanted to delete the model to repeat and acquire a better understanding of the process. When I tried to remove the editable regions (change-models-remove editable regions), I was unable to do so because 'remove the editable regions' is gray. Nor I was able to remove the html code. I tried to delete the template itself, but when I did, the index.html page kept these editable regions! Can someone tell me if there is a way to get back to the place I was forward to create the model?

    Thank you for any assistance.

    All you need to do is detach the template index.html file.  Then you can remove the template and start all over again.

    Go to the menu change--> models--> detach the model

  • Templates in DW CS5.5 and editable regions

    I have a model 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 - >

    < section class = "content" >

    CBEF clubs < h1 > < / h1 >

    < section >

    other code goes here

    < / section >

    <! - InstanceEndEditable - >

    Note the < / div > tag after the beginning of the editable region. It's a tag that is appropriate, it is necessary to close the div sidebar1″

    When he is not in an editable area, the < / div > shows no upward in yellow in design veiw and it works in every respect.

    When the combo box is introduced, the < / div > shows yellow in design mode, and it works in all respects.

    It validates using the W3C validation page.

    Pages built with it also show the yellow label, but they do not display it when live or in a browser.

    If I delete the < / div > as dreamweaver indicates, breaks css and page do not work.

    It seems that DW thinks that it is an illegal tag. If I click my mouse on the <!-InstanceBeginEditable name = 'all'-> tag and collapse of the tag, all the code in the edit box + than in the sidebare 1 div (even starting before the editable) collapses. The editable area does not allow changes in the sidebar1″ outside the region code.

    I need to put the editable region in the part of the sidebar div 1 so that I can add aditional items floated in box 1 div if necessary later.

    Is this a bug or am I missing something?

    It would be more logical.

    Some unique sidebar1″ content goes here

    The unique position here

    another code

    Nancy O.

    ALT-Web Design & Publishing

    Web | Graphics | Print | Media specialists

    http://ALT-Web.com/

    Post edited by: Nancy O.  I forgot to close the div. I'm glad

  • Footer does not drop down at the bottom of page template when the editable regions are met. Desperate!

    I tried everything I can think and have implemented several tutorials walk pasting without result.  Foot of page in the template seems to stick to the bottom of my sidebar divs when I want to stick to the bottom of the editable content in the html page.  Here is a screenshot and my code.  I am desperate for help. I intend using this model for several pages, then, how the footer to drop down the length of the main editable?  Help!

    footerproblem.jpg

    Here is the template code:

    < ! DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional / / IN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" > ""

    " < html xmlns =" http://www.w3.org/1999/xhtml ">

    < head >

    < content meta = text/html"; Charset = UTF-8 "http-equiv ="Content-Type"/ >"

    < meta http-equiv = "X-UA-Compatible" content = "IE = 9" / >

    < content meta = "width = device-width, original scale = 1.0, minimum scale = 1.0" name = "viewport" / > "

    <!-TemplateBeginEditable name = "doctitle"--> < title > < / title > <! - TemplateEndEditable - > <!-TemplateBeginEditable name = "head"--> <! - TemplateEndEditable - >

    "" < link type = "text/css" rel = "stylesheet" href = "... / stylesheets/master.css" / >

    < / head >

    < body >

    < div id = "container" >

    < div id = "header" >

    < h1 id = "logo" > Escalante Law < / h1 >

    < div id = "topnavcontainer" >

    < ul id = "topnavlist" >

    < li > < a href = "#" > home < /a > < /li >

    < li > < a href = "#" > Law Office Information < /a > < /li >

    < li > < a href = "#" > contact us < /a > < /li >

    < li > < a href = "#" > News < /a > < /li >

    < /ul >

    <!-end #topnavcontainer--> < / div >

    <!-end #header--> < / div >

    < div id = "mainmedia" > <! - end .mainmedia - > < / div >

    < div id = "middlenavcontainer" >

    < table width = "960" border = "1" align = "left" cellpadding = "10" >

    < tbody >

    < b >

    < style td = "" width: 176px; "> how can we help you?" < table >

    < style td = "" width: 182px; "> I need help with a green card < table >"

    < style td = "" width: 162px; "> I want to apply for citizenship < table >"

    < style td = "" width: 158px; "> I want to learn more about the dream Act < table >"

    < style td = "" width: 160px; "> do you currently have < br / >"

    having a green card < br / >

    and need help? < table >

    < /tr >

    < / tbody >

    < /table >

    <!-end #middlenavcontainer--> < / div >

    < div id = 'hand' >

    < div id = "sidebar1″" >

    < div class = "sidebar1_block" >

    Family Immigration < h2 > < / h2 >

    < ul class = "leftcolumnnav" >

    < li > < a href = "#" > < /a > family Visa Services < /a > < /li >

    < li > < a href = "#" > < /a > interim waiver < /a > < /li >

    < li > < a href = "#" > < /a > K1 Visa or Visa fiance < /a > < /li >

    < li > < a href = "#" > < /a > Visa K3 and K4 Visa < /a > < /li >

    < li > < a href = "#" > < /a > change status < /a > < /li >

    < /ul >

    <! - end .sidbar1_block - > < / div >

    < div class = "sidebar1_block" >

    Map green < h2 > < / h2 >

    < ul class = "leftcolumnnav" >

    < li > < a href = "#" > < /a > < /a > < /li > green card renewal

    < li > < a href = "#" > < /a > map green replacement < /a > < /li >

    < li > < a href = "#" > < /a > green card - family < /a > < /li >

    < li > < a href = "#" > < /a > removal of Conditions < /a > < /li >

    < li > < a href = "#" > < /a > Services consular processing < /a > < /li >

    < /ul >

    <! - end .sidbar1_block - > < / div >

    < div class = "sidebar1_block" >

    Dream Act < h2 > < / h2 >

    < ul class = "leftcolumnnav" >

    < li > < a href = "#" > Deferred Action < /a > < /li >

    < /ul >

    <! - end .sidbar1_block - > < / div >

    < div class = "sidebar1_block" >

    citizenship < h2 > < / h2 >

    < ul class = "leftcolumnnav" >

    < li > < a href = "#" > naturalization < /a > < /li >

    < /ul >

    < / div >

    <! - end .sidebar1 - > < / div >

    < div id = "content" > <!-TemplateBeginEditable name = "ContentArea"-> {tag_pagecontent} <! - TemplateEndEditable - > < / div >

    < div id = 'sidebar2' >

    the placeholder < div id = "rigtnavcontent" > < / div >

    the placeholder < div id = "rigtnavcontent" > < / div >

    the placeholder < div id = "rigtnavcontent" > < / div >

    <! - end .sidebar2 - > < / div >

    <! - end .main - > < / div >

    < div id = "footer" >

    < div class = "Section" >

    article a < /p > < p > Site map

    < ul id = "footernav" >

    Family based Immigration

    < li > < a href = "#" > < /a > < /li >

    < li > < /li >

    < li > < /li >

    < li > < /li >

    < li > < /li >

    < /ul >

    < / div >

    < div class = "Section" >

    < p > Section Site map two < /p >

    < ul id = "footernav" >

    Citizenship and naturalization

    < li > < a href = "#" > < /a > < /li >

    < li > < a href = "#" > application for citizenship < /a > < /li >

    < li > < a href = "#" > reviews of citizenship < /a > < /li >

    < li > < /li >

    < /ul >

    < / div >

    < div class = "Section" >

    < p > Section Site Map 3 < /p >

    < ul id = "footernav" >

    < li > < a href = "#" > map green < /a > < /li >

    < li > < a href = "#" > green card renewal < /a > < /li >

    < li > < a href = "#" > green card application < /a > < /li >

    < li > < a href = "#" > green card - family < /a > < /li >

    < li > < /li >

    < /ul >

    < / div >

    < div class = "Section" >

    < p > Section Site map 4 < /p >

    < ul id = "footernav" >

    < li > < a href = "#" > employment based Immigration < /a > < /li >

    < li > < a href = "#" > review Types of Visas work < /a > < /li >

    < li > < a href = "#" > apply for Visa to work < /a > < /li >

    < li > < a href = "#" > adjust the status of Visa work < /a > < /li >

    < /ul >

    < / div >

    <! - end .footer - > < / div >

    <! - end .container - > < / div >

    < / body >

    < / html >

    Here is my CSS:

    @charset "UTF-8";

    {body

    margin: 0;

    padding: 0;

    Color: #000;

    do-family: Verdana, Arial, Helvetica, without serif.

    do-size: 100%;

    line-height: 1.4;

    background-color: #FFFFFF;

    }

    / * ~ ~ This container fixed-width surrounds all the other div tags ~ ~ * /.

    #container {}

    Width: 960px;

    background: #FFFFFF;

    margin-right: auto;

    left margin: auto;

    }

    #content {}

    float: left;

    height: 100px;

    Width: 580px;

    margin-right: 0px;

    left margin: 0px;

    overflow: visible;

    }

    / * ~ ~ Footer styles ~ ~ * /.

    #footer {}

    background: #CCC49F;

    position: relative; / * This clear property forces the .container to understand where the columns end up and contain them * /.

    height: 300px;

    Width: 960px;

    margin-right: auto;

    left margin: auto;

    Clear: both;

    }

    #footer. {Section}

    height: 250px;

    Width: 200px;

    margin left: 14px;

    position: relative;

    float: left;

    padding: 10px;

    margin-top: 10px;

    border: thin solid #000;

    }

    H1 {}

    do-size: 16px;

    padding-left: 10px;

    }

    H2 {}

    do-size: 14px;

    padding-left: 10px;

    }

    H3 {}

    do-size: 14px;

    padding-left: 10px;

    }

    H4, h5, h6 {}

    margin-top: 0;

    text-align: left;

    padding-left: 10px;

    padding-right: 10px;

    }

    / * ~ ~ Tag of the element selectors ~ ~ *.

    UL, ol, dl {/ * because of variations between the browsers, it's best practices to zero padding and the margin on lists.} For consistency, you can specify the amounts you want to here, or on the list (LI, DT, DD) items they contain. Don't forget that what you're doing here cascade to the .nav list unless you write a more specific selector. */

    Padding: 20;

    margin: 0;

    }

    {p}

    do-size: 14px;

    padding-right: 10px;

    padding-left: 10px;

    }

    #container #content ul {}

    do-size: 14px;

    list-style-type: square;

    list-style-position: inside;

    }

    an img {/ * this switch how to remove the default blue border displayed in some browsers around an image when it is surrounded by a link * /}

    border: none;

    }

    / * ~ ~ Style for your site links must remain in this order - including the Group of selectors that create the hover effect. ~~ */

    a: link {}

    color: # 42413.

    text-decoration: none; / * unless you style your links appear to be extremely unique, it is best to predict stresses quick visual identification * /.

    }

    a: visited {}

    color: #6E6C64;

    text-decoration: underline;

    }

    a: hover, a: active, a: focus {/ * this group of selectors will give a browser keyboard the same experience of hovering as the person using a mouse. * /}

    text-decoration: none;

    }

    / * ~ ~ The header is not given a width. It will extend to the entire width of your layout. It contains an image placeholder to be replaced by your own logo linked. ~~ */

    #header {}

    background: #ADB96E;

    height: 60px banner;

    }

    / * ~ ~ These are the columns for page layout. ~~

    (1) padding is only placed on the top and/or bottom of the divs. The elements contained in these divs have padding on their sides. This avoids any «mathematical model of box» Keep in mind, if you add lateral pads or border to the div itself, it will be added to the width that you set to create the * total width. You can also remove the padding of the element inside the div tag, and place a second div inside it with no width and padding necessary for your design.

    (2) no margin was given to the columns, because they all floated. If you need to add the margin, avoid placing on the side you're floating into (for example: a right margin on a div set to float to the right). Many times, padding can be used instead. For divs where this rule needs to be broken, you must add a statement of ' display: inline ' to the rule of the div to tame a bug where some versions of Internet Explorer double the margin.

    (3) given that the classes can be used several times in a document (and an element can also have several classes applied), the columns have received the names of classes instead of IDs. For example, two sidebar div could be stacked if necessary. These can easily be changed to the ID if that's your preference, as long as you don't use them once per document.

    (4) If you prefer your nav on the right instead of the left, simply float those columns as the opposite direction (straight instead of left all) and they will return in reverse order. There is no need to move the div in the HTML source code.

    */

    {#sidebar1}

    float: left;

    Width: 200px;

    background: #EADCAE;

    }

    {.sidebar1_block}

    padding: 5px;

    margin: 5px;

    }

    {#sidebar2}

    float: left;

    Width: 180px;

    background: #EADCAE;

    padding-right: 0px;

    padding-left: 0;

    padding-top: 0px;

    padding-bottom: 0px;

    height: 100%;

    }

    / * ~ ~ This group selector gives the lists in the domain content space ~ ~ * /.

    . Content ul, ol {} content

    padding: 0 15px 15px 40px; / * This padding reflects the right padding in the titles and the paragraph above net. Padding was placed on the bottom for the space between the other elements in the lists and on the left to create the withdrawal. These can be adjusted as desired. */

    }

    / * ~ ~ The list of navigation styles (can be removed if you choose to use a contextual menu premade as Spry) ~ ~ * /.

    UL. NAV {}

    list-style: none; / * This command deletes the list marker * /.

    border-top: 1px solid #666; / * This creates the top border for the links - all the others are placed using a bottom border on the LI * /.

    margin-bottom: 15px; / * This creates space between the following content browsing * /.

    }

    {ul li. NAV

    border-bottom: 1px solid #666; / * This creates separation button * /.

    }

    UL. NAV, the ul.nav: visited {/ * these selectors of grouping allows you to ensure that your links to retain their look button even after the ongoing visit * /}

    padding: 5px 5px 5px 15px;

    display: block; / * Gives the anchor block properties, so it meets all LI that contains that whole area responds to a mouse click. */

    Width: 160px;  / * This width makes all the clickable button for IE6. If you do not need to support IE6, it can be removed. Calculate the width by subtracting the padding on this link of the width of your sidebar container. */

    text-decoration: none;

    background: #C6D580;

    }

    UL. NAV a: hover, ul.nav one: ul.nav active,: focus {/ * this changes the background and color of text for browsers of the mouse and the keyboard * /}

    background: #ADB96E;

    color: #FFF;

    }

    / * ~ ~ Various float/clear classes ~ ~ * /.

    .fltrt {/ * this class can be used to float right to the item in your page.} The floating element must precede the element it should be next to the page. */

    float: right;

    left margin: 8px;

    }

    .fltlft {/ * this class can be used to float an element on your page.} The floating element must precede the element it should be next to the page. */

    float: left;

    right margin: 8px;

    }

    .clearfloat {/ * this class can be placed on a < br / > or div empty as the final element after the last div floating (inside the .container) if the .footer is removed or put off the .container * /}

    Clear: both;

    height: 0;

    font size: 1px;

    line-height: 0px;

    } #mainmedia {}

    height: 300px;

    Width: 960px;

    float: left;

    }

    {#nav_tier_2}

    height: 60px banner;

    Width: 960px;

    }

    {#lower_nav}

    height: 60px banner;

    Width: 100%;

    float: left;

    }

    {#topnavcontainer}

    list-style-type: none;

    list-style-image: none;

    float: right;

    Width: 500px;

    height: 47px;

    padding-top: 13px;

    }

    #container #header #logo {}

    float: left;

    do-family: Arial, Helvetica, without serif.

    make-weight: normal;

    color: #FFF;

    }

    #topnavlist li {}

    display: inline;

    list-style-type: none;

    padding-right: 20px;

    text-decoration: none;

    }

    }

    #container #middlenavcontainer {}

    float: left;

    height: 100px;

    Width: 960px;

    do-family: Arial, Helvetica, without serif.

    do-size: 12px;

    }

    #container #middlenavcontainer table tr {}

    text-align: center;

    }

    #container #sidebar1 h2 {}

    do-size: 14px;

    line-height: normal;

    margin-bottom: 10px;

    top of the margin: 5px;

    }

    {.leftcolumnnav}

    list-style-type: none;

    Color: #000;

    do-size: 12px;

    }

    {#footernav}

    list-style-type: none;

    do-size: 12px;

    }

    #container #footer. Section p {}

    do-size: 12px;

    }

    {#sidebar2 #rigtnavcontent #container

    height: 160px;

    }

    {#contact_form}

    top of the margin: 20px;

    border: thin solid #000;

    margin-bottom: 0px;

    Width: 420px;

    margin-right: auto;

    left margin: auto;

    padding-top: 10px;

    padding-right: 10px;

    padding-bottom: 0px;

    padding-left: 10px;

    height: 600px;

    }

    {.p_content}

    do-size: 14px;

    }

    {content-column

    } {#container #main

    height: 100%;

    overflow: visible;

    }

    Hello

    The 'content' div's style to have 100px in height and visible from overflow. So the text overflows the div, but the footer "ignores" / ignore it is positioned after 'sidebar2 '.

    Change the height of the 'content' to 100% and it should work.

    Kind regards

    Alex

  • CSS, DIV and editable regions

    Hi all

    I am having trouble about a fairly simple dreamweaver model in combination with an external css file. For design purposes, it should be all done using DIV (without tables).

    That's what I am looking for: page 80% width, centered:

    1 (editable) left header - the header right

    2 menu

    3 content (editable)

    4 footer

    It is particularly important that the content (3) can be changed WITHOUT interfering with the other DIV or anything else. Also, the left of the header (1) must be editable, but it is only text or banner or so.

    I really hope that someone can help me here, because after hours of research, I'm kindof see letters, no words more ;-)

    <!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>Testing</title>
<!-- TemplateEndEditable -->
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
<link href="../Style/Main.css" rel="stylesheet" type="text/css" />
<script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
</head>
<body class="MainCssClass">
<div id="container">
<div id="header">
<div align="right"><!-- TemplateBeginEditable name="Header" --><!-- TemplateEndEditable -->Header</div>
</div>
<div id="Menubar">
<ul id="MenuBar1" class="MenuBarHorizontal">
  <li><a href="../index.html" title="Home" target="_self">Home</a></li>
  <li><a href="#">Contact</a></li>
  <li><a href="#">About</a></li>
</ul>
</div>
<div id="container">
  <div align="center"><!-- TemplateBeginEditable name="MainContent" -->
    <p align="center"> </p>
    <p align="center"> </p>
    <p align="center"> </p>
    <div id="mainContent">
      <p> </p>
    </div>
    <!-- TemplateEndEditable -->
    <!-- end #mainContent -->
  </div>
</div>
  <div id="footer">
    <p align="center">Footer</p>
<!-- end #footer --></div>
<!-- end #container --></div>
<script type="text/javascript">
<!--
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
//-->
</script>
</body>
</html>

    And here is the external STYLE sheet that I use:

    @charset "utf-8";
body {
 font: 100% Verdana, Arial, Helvetica, sans-serif;
 background: #666;
 /* margin: 0; it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
 padding 0 0 0 0;
 text-align: center; /* this centers the container in IE 5* browsers. The text is then set to the left aligned default in the #container selector */
 color: #CCC;
}
.MainCssClass #container {
 width: 80%;  /* this will create a container 80% of the browser width */
 height: 100%;
 background: #000;
 margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
 padding: 0; /* remember that padding is the space inside the div box and margin is the space outside the div box */
 border: 0px;
 text-align: right; /* this overrides the text-align: center on the body element. */
}
.MainCssClass #header 
{
 margin: 0 0 0 0;
 background-color: #FFF;
 color:#000;
 width:100%;
}
.MainCssClass #mainContent {
 padding: 10px 10px 10px 10px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
 background: #000;
 color:#CCC;
 text-align:center;
 height:auto;
}
.MainCssClass #footer 
{
 margin: 0; /* zeroing the margins of the first element in the footer will avoid the possibility of margin collapse - a space between divs */
 padding: 0 0 0 0; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
 font-size: small;
 background-color:#666;
}
#divLeft { 
 float:left; 
 width:50%;
} 
#divRight { 
 float:right; 
 width:20%;
}

    I've been trying and troubleshooting all afternoon, but I can't seem to find what I'm doing wrong. Can someone advise me on this? I'm afraid it's the nested DIV I mix it up.

    Any help would be really appreciated!

    Thank you

    Mich

    CSS:

    {body
    Police: 100% Verdana, Arial, Helvetica, without serif.
    Background: #666;
    / * margin: 0; It is advisable to zero, the margin and the filling of the body to hold element has a different default browser * /.
    fill 0 0 0 0;
    text-align: center; / * This centers the container in IE 5 * browsers. The text is then set left aligned by default in the #container selector * /.
    color: #CCC;
    }
    . MainCssClass #container {}
    Width: 80%;  / * This will create one that contains 80% of the width of the browser * /.
    Background: #000;
    margin: 0 auto; / * margins (in conjunction with a width) auto Center the page * /.
    padding: 0; / * Remember that the fill is space inside the box of div and margin is the space outside the div box * /.
    border: 0px;
    text-align: left; / * This setting overrides the text-align: center on the body element. */
    overflow: hidden; / * encapsulates container around the floating elements inside * /.
    }
    . MainCssClass #header
    {
    background-color: #0F3;
    Color: #000;
    overflow: hidden;
    }
    {#divHeaderLeft}
    float: left;
    Width: 50%;
    }
    {#divHeaderRight}
    float: right;
    Width: 20%;
    }
    . MainCssClass #content {}
    padding: 10px 10px 10px 10px; / * Remember that the fill is space inside the box of div and margin is the space outside the div box * /.
    Background: #000;
    color: #CCC;
    text-align: center;

    }
    . MainCssClass #footer
    {
    margin: 0; / * zero setting the margins of the first element in the footer will avoid the possibility of the collapse of the margin - a space between the div tags * /.
    padding: 0 0 0 0; / * padding on that element will create space, just as it would the margin, free margin collapse question * /.
    font size: small;
    background-color: #666;
    }

  • Error in adding an editable region in the nested template header

    I have a basic model for the website (creation of main menus) and a secondary model using this basic model, which establishes a common table, on the one hand of the site layout. After you create the PHP to drive page, I need to lock this secondary nested region - otherwise any edit I make on my secondary & quot; -definition of table & quot; model is not passed to the last pages using the secondary model. I created a secondary edit box successfully in every part of the & lt; body & gt; region, and of course, it locks text outside the secondary editable help DW says it should. So far so good.

    Now the problem - I can not create a region inside the & lt; head & gt; combo box to lock this region too. Normally we'd like keywords and so on to be variable from one page to another, but as I am filling variable keywords from a database, it makes sense to lock the & lt; head & gt; Too much. Does anyone know why that generates an error & quot; failed to create an optional region here & quot;? Is there anything we can do about it?

    > by whom?
    This is DW CS3 help on nested models:

    A nested template is a template whose design and editable regions is based on another model. Nested models are useful for the control of content in the pages of a site that share many design elements, but have some differences between pages. For example, a basic model can contain broader design areas and be usable by many contributors of content on site, while a nested model can further define the editable regions in the pages of a specific section of a site.

    > the solution
    I just figured out how to lock the header in the document of reference to TechNote 16416. It is referenced in the called DW CS3 help page

    Prevent an editable region to a nested model

    In summary - insert the marker @@("") @ in the editable area.

    I tried it and it works perfectly! The cephalic region is now locked in the nested template, so the changes in this area went from child pages. That's the answer.

    > your book
    Yes, I saw it on Amazon. Kudos to you for publication.

    > your suggestion extracted
    Thanks for that. This looks like a more manual approach, however.

    > mysteriously missing paragraphs
    Very strange, I can see them on my screen in Firefox and IE7.

    Best regards
    Richard

  • Messed up the editable regions in the documents based on templates

    Y at - there no way to fix corrupt editable regions in a document?

    We have 2 editable regions in a template: -.

    <!-TemplateBeginEditable name = "MidText"->

    < p > < / p >

    <! - TemplateEndEditable - >

    <!-TemplateBeginEditable name = "LowText"->

    < p > < / p >

    <! - TemplateEndEditable - >

    In several documents based on these models, the name has been deleted by mistake: -.

    <!-TemplateBeginEditable name = ""-> "

    < p > < / p >

    <! - TemplateEndEditable - >

    <!-TemplateBeginEditable name = ""-> "

    < p > < / p >

    <! - TemplateEndEditable - >

    If we try to update the documents in an attempt to fix, we get the following error message:

    There is an error on line..., column... (absolute position...) of "nomDuDocument": name missing for InstanceBeginEditable ""

    If we try to update using the templates, we get the following error message:

    no update, error in the file of template or instance

    Is there a 'fix' for this?

    Thank you.

    Looks like you know what you're doing.

    Assuming your child pages are incorrect, try closing DW and open the problem page in a simple editor like Notepad or Simpletext ascii text, add in the missing name values (remember to use the proper case) and save & close them.

    Then see if DW is happy.

  • Nesting templates: child-model Pages does not fully to the Editable vs a-Editable regions

    Me kay, so first of all, it's all done within Dreamweaver CS5. How can I explain this, is that I have a series of Master-models for my site, then accompanied by child-models related to offshore of / nested my master-models. So far it's going wonderfully, until what I'm trying to make a page of one of my children-models.

    The page of my child-model accurately comment on an non editable (region in which is editable in the master model, but left as ONLY editable within the child-model) as long as I add an EDITABLE area it contains. In the circumstances I have DO NOT add an editable region in the editable area of the master model, the area within the Page is appearing always editable.

    For example:

    __________________

    Model Master:

    <!-TemplateBeginEditable name = "ChildTemplateCSSLinks"->

    Model child CSS links here.

    <! - TemplateEndEditable - >

    _____

    Child model:

    <!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->

    Model child CSS links here.

    <!-TemplateBeginEditable name = "ChildPageCSSLinks"->

    Child CSS PAGE links here.

    <! - TemplateEndEditable - >

    <! - InstanceEndEditable - >

    _____

    The child page:

    Model child CSS links here. (Precisely appearing not editable - {editable area of the master model tags appearing exactly invisible})

    <!-InstanceBeginEditable name = "ChildPageCSSLinks"->

    Child CSS PAGE links here. (Accurately appearing editable)

    <! - InstanceEndEditable - >

    __________________

    It is a WORKING example of editable regions. In the child Page "Template CSS child links here." Appearing in comment and therefore not editable in the child Page, as if it was supposed to be. This time allows the 'child PAGE CSS links here' to be editable with PRECISION within the child-Page.

    Now for an example of what does not work:

    __________________

    Model Master:

    <!-TemplateBeginEditable name = "ChildTemplateCSSLinks"->

    Model child CSS links here.

    <! - TemplateEndEditable - >

    _____

    Child model:

    <!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->

    Model child CSS links here.

    (As you can see, I've added an extra editable within the editable area of the master model. This is an area which is supposed not to be editable within the child-model and NOT the child-Page, which seems to be up to NOW accurate.)

    <! - InstanceEndEditable - >

    _____

    The child page:

    <!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->

    Model child CSS links here.

    (For a reason, THAT as long as I DO NOT add an additional child-model - edit box in the editable area of the master model, this area is appearing ALWAYS visible but also editable in the child Page.)

    <! - InstanceEndEditable - >

    __________________

    So, in this circumstance, it seems that the only way I can leave ALONE the editable region of the master model can be changed within the child-model and NOT editable in the child Page is leaving an ADDITIONAL editable produced through the child-model somewhere within the editable region EVERY SINGLE, produced by the master model. Unless I do something bad, it seems this until a potential defect/bug in Dreamweaver CS5. I can't imagine how this would be correct, otherwise child/Nested-Templates would be not possible to do. What could I do it wrong? Is it possible that I can specify in the master model is an editable editable ONLY within the child-model and NOT yet child-Pages (A Page based on the template of the child)? Or maybe is it possible that I can specify the child-model that an area can be changed WILL NOT be editable in the child Page? Furthermore, no, I DON'T want to make "Optional Regions", so please do not suggest that.

    I know it's all probably a little confusing, but I hope the examples above more than descriptions aside. As you can probably assume, it is definitely a HUGE complication in my site if it does not end up being a solution, especially with all the time I put into making the child models, which I hope to rely on. It would be really silly if I had to script - in an editable region extra in each master-model-editable-region unique available within my child-model just so that I can update my child-model, in addition to my changes to my child-Pages, to fall as much as it would maintain the content that I never wanted to be editable in the child Page in the FIRST place.

    Some help would be appreciated sincerely, as soon as possible, if I could ask politely.

    Thank you. Sincerely,

    ~ Miss Cat

    = _ = I can't believe that I say this, after having written ALL that a period, but thanks to 'Dreamweaver CS5 for Dummies,' I just found out that if you place: @@("") @ in the editable area of the desired child/Nested model DO NOT passed down for your child-Pages, it won't appear not editable. God knows why such a discrete formula was the answer, but I guess that everything works. ... WHY WAS IT SO DIFFICULT TO FIND INFORMATION? @_ @ Information about nested templates in general seems quite hard to find, however, so I'm glad that I thought that this output /not/ never a full hour / after writing all this upward and detachment. #__#  ... At least my child models can work perfectly now, though. Then... FIXED scenario. ^^

    I hope that now this information will appear useful to someone else hunting for that information via Google or other search engine in the future. And if there is nothing at all that I'm still officially missing, then do feel free to add to food and let me know, because the last thing I need now of law are more surprising difficulties also slow down the productivity of this vast project I worked on... @_ @... But so far things seem to be going well. ^^ So I can just incredibly grateful that he will eventually be a solution to this ridiculous after all.

    Sincerely,

    Miss Cat

    [info promo signature removed by Moderator]

  • Make editable regions in a template

    I have a model in which I want to make an editable region uneditable.  Is this possible?

    Appreciate any input

    Gilbert

    Yes.

    With the model of open file, select the area you want to make editable and go to insert > template objects > editable region and then give it a meaningful name.

    Alternatively, wrap the code around the area you want to be editable and name, below, both do exactly the same thing: just in different ways.

  • Editable regions, nested on template

    The model has 2 elements of library, each container javascript rollovers and a couple of editable regions. He recorded without error and fine views. But when I try to create a file based on the template, the error reads: ' there is an error on line 152, 190 (absolute position 8582) column of... ". Filename. nested editable regions.

    http://www.aptcoweb.com/templates/aptcopage.dwt

    Now I see it. Open your model, go to line 152 and remove this block of code:

    It is a repetition of thetag and it confuses your model.

    You should also validate your model. I see several incorrect entries for XHTML. For example, images tags should be closed with a "" / > "(space-bar oblique-angled support), not just ' > '."

  • How can I create CSS for the editable regions in the documents based on templates?

    I created a template in Dreamweaver CS4 by using their set of 3 columns, header and Footer option available. The model works fine in the browser. I inserted an editable region in the empty middle of the model column. I created a new page based on this template and want to be able to format the text that I entered in the editable using CSS. Any time, I try to create a new CSS rule I get the following dialog:

    "This change should change the code which is locked by a model or a translator. The changes will be rejected. »

    Is it possible to create new CSS, which will apply to the information entered in the regions be modified of a document based on a template? Simple step by step instructions would be appreciated.

    Thanks for reading

    Do not know what is the 'id' of the middle column, but you must target the text inside that

    .

    Example:

    {#whatever}

    color: #639;

    do-size: 12px;

    }

    It is better if the text in the middle column is paragraphs and target you them as as follows:

    #whatever p {}

    color: #639;

    do-size: 12px;

    padding: 0 15px 15px 0 / * top, bottom, right, left * /.

    }

    You must make sure that you include the above in the editable page css region and HE MUST come after any link to the style sheet css main.

    If in doubt post the code for the page here and say what you want to be purple and I'll have a look.

    The tip is stop created with the css dialog box in DW, it's a load of bollocks and started writing some simple css directly in the page itself. It is easier and gives you more control than any interface automated half cooked in the oven.

    Start learning some simple css. There is absolutey zillions of resources on the net. A couple of hours well spent and your miles further. If you keep pressing DW to do everything for you, then I'm afraid you'll just be going around in circles.

    Enter the code and don't be afraid of him, take it apart and see how it works. Slowly step by step and little by little you will realize how simple structures are and how simple css really is.

  • My editable region appears to be transformed "template".

    http://www.laserlines.co.UK/htm/Corp/newsandpress.htm

    "Design" view of this page indicates that the 'News' and ' press release: "section is part of the model, however the code apears to indicate it is still editable. What is stop access to this space? Also when I update my model through the site, I receive a report indicating that there is a problem felt with the editable area of 'Quick Link', "InstanceBeginEditable tag inside the editable region" on this page, but the code does not seek to be different than on other pages. Clues?

    > Many thanks, you've been a
    > great help.

    You are welcome! I am pleased that we were able to work through this.

    > Is
    > there a better system for tracking site traffic?

    Success counters are usually the worst way to do this. The best way is to
    analyze log files from your site, managed by the server session. Most of the guests
    This ability - ask them. This means that you don't need a
    counter on your page at all.

    --
    Murray - ICQ 71997575
    Adobe Community Expert
    (If you * MUST * write me, don't don't LAUGH when you do!)
    ==================
    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
    ==================

    "Haberdashery" wrote in message
    News:e3sh12$66N$1@forums. Macromedia.com...
    > There is that Word to describe you - genius! Thank you very much, you have
    > summer a
    > great help.
    >
    > A thing, you ask using the Red Toolbox meter but don't say why?
    > Is
    > there a better system for tracking site traffic?
    >

  • The editable regions and Flash animation

    Hello

    I'm trying to insert a flash movie into an editable region of a page of the child, but I get the following error: "this change should change the code which is locked by a model or a translator. The changes will be rejected. »

    I read the previous posts on the same topic, but none of them does answer my question. I tried to create a new model and a child by him as a test by removing the css links (as someone suggested to do) to try to identify troubled css and I kept getting the same error in the new pages. I hope someone can help identify the problem and the solution. The area where I want to insert the movie is called "FinalMainContent".

    BTW, I don't know how to write the code... Sorry!

    Thanks in advance for any help you can provide!

    Here is the code:

    <! DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional / / IN".
    " http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" > ".
    <!-saved from url = (0014) subject: internet->
    "< html xmlns =" http://www.w3.org/1999/xhtml "> <! - model InstanceBegin =" / models/hand Pages.dwt "codeOutsideHTMLIsLocked =" false "- >"
    < head >
    <!-InstanceBeginEditable name = "doctitle"-->
    < title > TotusMundus - video/Film < /title >
    <! - InstanceEndEditable - >
    < meta http-equiv = "Content-Type" content = text/html"; Charset = UTF-8 "/ >"
    <!-target fireworks 8 Dreamweaver 8. Created Sat Jan 13 16:43:41 GMT - 0500 () 2007->
    < link href = "TotusMundus_Styles.css" rel = "stylesheet" type = "text/css" / > "
    <!-InstanceBeginEditable name = "head"->
    < link href = "Templates/TotusMundus_Styles.css" rel = "stylesheet" type = "text/css" / > "
    <! - InstanceEndEditable - >
    < script language = "JavaScript1.2" type = "text/javascript" >
    <!--
    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]) & & copyrights) x = d.all [n]; for (i = 0;! x & & I < d.forms.length; i ++) x = d.forms [n];
    for (i = 0;! x & & d.layers & & I < d.layers.length; i ++) x = MM_findObj(n,d.layers    .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 (un ))! = null) {document. MM_sr [j ++] = x; if(!x.oSrc) x.oSrc = x.src; x.SRC = a [i + 2] ;}
    }
    function MM_swapImgRestore() //v3.0 {}
    var i, x = offline. MM_sr; for (i = 0; a & & I <.) Length & & (x = a    ) & & x.oSrc; i ++) x.src = x.oSrc;
    }

    function MM_preloadImages() {//v3.0
    var d = document; If (d.images) {if(!d.MM_p) d.MM_p = new Array();
    var i, j is d.MM_p.length, a = MM_preloadImages.arguments; for (i = 0; i <.) Length; i ++)
    If (one .indexOf("#")! = 0) {d.MM_p [j] = new Image; d.MM_p [j ++] .src = a;}}}
    }

    ->
    < /script >
    < script type = "text/javascript" src = "p7pm/p7popmenu.js" > < / script >
    < style type = "text/css" >
    TD img {display: block ;} < / style >}

    < style type = "text/css" media = "screen" >
    <!--
    @import url("p7pm/p7pmv0.css");
    a: link {}
    color: #999999;
    text-decoration: none;
    }
    a: visited {}
    text-decoration: none;
    Color: #666666;
    }
    a: hover {}
    text-decoration: none;
    Color: #666666;
    }
    a: active {}
    text-decoration: none;
    Color: #666666;
    }
    ->
    < / style >
    < script src = "Scripts/AC_RunActiveContent.js" type = "text/javascript" > < / script > "
    < / head >
    < body onload = "P7_initPM (0,0,1,0,-8); "MM_preloadImages (" Images/LinesBtn_f2.jpg','Images/SmallFlow erBtn_f2.jpg','Images/SquigliBtn_f2.jpg','Images/StarBtn_f2.jpg','Images/DoubleSquigliBtn_ f2.jpg','Images/BigFlowerBtna_f2.jpg','Images/PrevBtn_f2.jpg','Images/NextBtn_f2.jpg'");" > < table align = "center" border = "0" cellpadding = "0" cellspacing = "0" width = "800" >
    "<!-fwtable fwsrc ="Index.png"fwbase =" TotusMundus.jpg "fwstyle ="Dreamweaver"fwdocid ="1262947761"fwnested ="0"->
    < b >
    "< td > < img src ="Images/spacer.gif"width ="116"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="8"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="182"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="109"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="102"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="180"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="7"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="96"height ="1"border ="0"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="1"height ="1"border ="0"alt =" "/ > < table >
    < /tr >

    < b >
    "< td rowspan ="2"colspan ="7"> < a href =" index.htm "> < img name ="LogoAnfTagLine"src = Images/LogoAnfTagLine.jpg" "width ="704"height ="100"border ="0"id ="LogoAnfTagLine"alt =" "/ > < /a > < table >
    "< td > < img name ="MusicTitle"src ="Images/MusicTitle.jpg"width ="96"height ="74"border ="0"id ="MusicTitle"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="1"height ="74"border ="0"alt =" "/ > < table >
    < /tr >
    < b >
    < td rowspan = "4" > < a href = "" javascript:; "" MM_swapImgRestore; "onmouseover =" MM_swapImage ('LinesBtn', ", ' Images/LinesBtn_f2.jpg', 1);" "" > < img name = "LinesBtn" src = "Images/LinesBtn.jpg" width = "96" height = "57" border = "0" id = "LinesBtn" alt ="" / > < / a > < table >
    "< td > < img src ="Images/spacer.gif"width ="1"height ="26"border ="0"alt =" "/ > < table >
    < /tr >
    < b >
    "< td colspan ="7"> < img name ="CushionforPath"src ="Images/CushionforPath.jpg"width ="704"height ="13"border ="0"id ="CushionforPath"alt =" "/ > < table >
    "< td > < img src ="Images/spacer.gif"width ="1"height ="13"border ="0"alt =" "/ > < table >
    < /tr >
    < b >

    OK, I thought about it: the problem is that in the window options, when I tried to insert Flash video, I ticked the box: 'invite users to download Flash Player if necessary.' It was not allowing me to insert. When I unchecked, the error message disappears. I guess, I have to add this option to download in a different way.

    Thank you for taking the time to answer. Much appreciated!

    MS

  • How to apply a template with a new editable region to a group of existing pages

    Hello

    Here's my question:

    1. I have a group of web pages that were created by using a template with editable regions.

    2. I added a new editable region to a template that should be added to the previous pages.

    What is the procedure to add the new editable region to previous web pages?

    Thanks for your advice

    Juan

    When you have saved the model, you have been invited by Dreamweaver to ask if you want to update pages based on the template. As long as you click Update, the new editable region should be in the pages of the child.

Maybe you are looking for