Replacing existing template - need to add editable regions

I've created a new design for my website and created a new template that uses the same editable regions so it will correctly update all of the existing pages based on the old template.  How can I add new editable regions to the template?  I was told that the editable regions have to matach exactly. Is there a way around this where I can add new ones? 

It all depends on how you set-up your original template.  Can we see a link to your template or the code from it?
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media  Specialists 
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com/

Similar Messages

  • Need to add editable regions

    How can I add editable regions to an existing template that has hundreds of child pages?  There is one editable region for page content (in a box) in the old template, now I want to have 3 different boxes for editable content.  When I update all of the pages by saving the template, the existing content (in the original editable reigion) should show up in one editable region, and the new editable regions will show up as empty boxes (until I fill them).

    It all depends on how you set-up your original template.  Can we see a link to your template or the code from it?
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb
    http://alt-web.blogspot.com/

  • Can't manually add editable regions to head in template

    When I created my main template in Dreamweaver CS6 for my website, I had copied most of the page code from another layout I already had, including the head code.  I did not realize there were already editable regions built into the head section of the Dreamweaver template and deleted them when I pasted my previous code without adding new ones.  I then added an editable region to the body and started created pages using the template.
    Everything works well and updates properly when I make changes to the template but now that I am trying to add those editable regions back to the head section so I can change the page title (and possibly add more responsive code), it doesn't work.  I copied and pasted the following code into my template file in Dreamweaver and it saves in the template telling me it's updating the related pages, but when I open those individual pages in Dreamweaver, the code isn't there and those regions are not editable; only the original editable region I created in the body exists and works properly.  Everything else continues to work perfectly.
    Here is the code I pasted into the head around the <title> tag:
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Collings Document Database</title>
    <!-- TemplateEndEditable -->
    And here is the code I pasted into the head just before the </head> tag:
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    </head>
    Any help would be appreciated.  From everything I've read on these forums after searching, it sounds like pasting that code should work but I continue to get the results mentioned.  Thank you.

    Thanks for the response.  I've run the template code through the validator and the following two errors are the only ones that showed up.  I don't see how either of these would cause this issue.  Thoughts?
    Line 5, Column 53: Bad value X-UA-Compatible for attribute http-equiv on element meta.
    <meta http-equiv="X-UA-Compatible" content="IE=Edge">

    Line 27, Column 127: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images. …gs_guitars_stroke_clear.png" width="184" height="81" class="scalable">  </div>

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

  • I saved as template , and created one editable region in the content area

    I have four pages from the template; the index, services, products and services.  Now if i want to create a sidebar for the services page only. How do I do that without the template updating to all the pages. I just need the service page with the sidebar.
    Your contribution is greatly appreciated.

    Create a #Sidebar style in your external CSS and a place for it in your main Template.dwt.
    On child pages where you don't want the #Sidebar to appear, embed a page specific CSS rule like this:
    <style type="text/css">
    /**PAGE SPECIFIC STYLES GO HERE**/
    #sidebar {display:none}
    </style>
    Nancy O.

  • Automator - meaning of "replace existing files" needed please!!!

    Have just set up automator to back up to my external hard drive but there is an option to replace exisiting files. Will this replace ALL the files on my hard drive or just replace files which have been changed?
    Help greatly appreciated,
    Sgtbash17

    It replaces files of the exact same name.
    Files that have the exact same name, including the extension, will be replaced when you have that chosen.
    Without it checked, it won't overwrite files that have the exact same name. That means those files won't be written out at all, and the files of the exact same name will still contain the previous content. Therefore, you won't have a revised backup of those particular files.
    Other files that don't share the same name with any other file will be written.
    Does that make sense? If a file with the same name as another file already exists in that folder, then that file will be replaced. Other files that don't have the same name as any other file will continue to exist.
    The best thing to do is to try it out on a test sample before you start relying it so it won't matter if it messes up.

  • I have an existing application need to add LabVIEW OPC Server

    I have an existing application written in LabVIEW which controls a Device. The data from the device is currently logged to the local drive. 
    It is desired to upgrade this application to become an OPC Server so that the manager can remotely acquire data and control the Application.
    What would be the easiest approach to accomplish this task?
    Thanks and Best Regards,
    Gary

    Hello Dan,
    1. The operator specifies a time interval to save the data to disk. The data is stored in a csv file.
     2. The manager is the Engineer who is managing the data collection system remotely.
    3.The desired end result is to have the LabVIEW with an OPC server provide the connectivity to an OPC client so that they can collect the data, that they desire from the system, and control the system.
    4. Controlling the system is secondary. Providing the connectivity so that an OPC client can specify what data is to be sent and the update interval is the first priority.  For example, they may only be interested
    in 10 of say 30 parameters, and want that data sent over every 10 seconds or so. The data once they receive it will be logged to a central data base.
    We suggested using TCP/IP but they do not want a custom interface.
    We also suggested Modbus, but they perfer to use OPC. The want to integrate it with their OSI PI.
     Thanks and Best Regards,
    Gary

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

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

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

  • 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

  • Error adding editable region in nested template Header

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

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

  • Cannot add layers/tables to an editable region

    I created a template the other day, and then created pages
    from that template. The main editable region which was meant to be
    for all my info, pictures, wont let me add layers or tables to
    position my text/images.... Have I missed something here?
    \Robert

    Yes, there would be no restriction on what you can place in
    that editable
    region. But I don't like the way you have started with this
    page. Layers
    should not be used as a primary layout methodology....
    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
    ==================
    "the full monty" <[email protected]> wrote
    in message
    news:epqp0m$lrc$[email protected]..
    > This is the code: The whole of the layer region should
    be editable... ie.
    > be
    > able to add layers/tables to position text?
    >
    > <!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=iso-8859-1" />
    > <!-- TemplateBeginEditable name="doctitle" -->
    > <title>Untitled Document</title>
    > <!-- TemplateEndEditable -->
    > <!-- TemplateBeginEditable name="head" --><!--
    TemplateEndEditable -->
    > <style type="text/css">
    > <!--
    > #Layer1 {
    > position:absolute;
    > left:382px;
    > top:30px;
    > width:329px;
    > height:268px;
    > z-index:1;
    > }
    > -->
    > </style>
    > </head>
    >
    > <body>
    > <div id="Layer1"><!-- TemplateBeginEditable
    name="EditRegion1" --> <!--
    > TemplateEndEditable --></div>
    > </body>
    > </html>
    >
    > \Robert
    >

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

  • Editable regions in templates. How do I edit the CSS in a new page from the template?

    I am new to Dreamweaver and Web design. I have made a template and have two editable regions they work fine. When I create a page from this template, I can't edit the CSS. What do I need to do to edit the div tags that are specific to the editable regions? Thank you, I appreciate any help I am just about to give up with templates.

    Hi, thank you here is my code. Maybe I am trying to do too much advanced stuff to soon!
    <!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>Untitled Document</title>
    <!-- TemplateEndEditable -->
    <link href="file:///C|/Users/Roxane/Desktop/Brown County Indiana/images/favicon.ico" rel="shortcut icon"/>
    <!--jquery -->
    <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4/jquery.min.js"></script>
    <script type="text/javascript" src="file:///C|/Users/Roxane/Desktop/brown county indiana/scripts/automanualslideshow.js"></script>
    </script>
    <!-- End jquery-->
    <style type="text/css">
    #container {
        width: 960px;
        margin-right: auto;
        margin-left: auto;
    #header {
        height: 80px;
        width: 100%;
        background-color: #222;/*Some browsers will not recognize RGBA colors*/
        background-color: rgba(0,0,0,0.6);/*RGBA fourth value for opacity, if there are two rules that apply to the same element, the latter of the two takes priority.*/
    .jld_logo {
        float: left;
        padding-left: 70px;
        display: block;
        padding-top: 10px;
    #navigation {
        height: 27px;
        width: 100%;
        background-color: #C00;
        margin-left: 0px;
        padding-left: 0px;
        padding-right: 0px;
        left: 0px;
        color: #FFF;
        background: rgb(192,0,0); /* Old browsers */
        background: -moz-linear-gradient(top,  rgba(192,0,0,1) 0%, rgba(144,0,0,1) 51%, rgba(144,0,0,1) 56%, rgba(192,0,0,1) 100%); /* FF3.6+ */
        background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,rgba(192,0,0,1)), color-stop(51%,rgba(144,0,0,1)), color-stop(56%,rgba(144,0,0,1)), color-stop(100%,rgba(192,0,0,1))); /* Chrome,Safari4+ */
        background: -webkit-linear-gradient(top,  rgba(192,0,0,1) 0%,rgba(144,0,0,1) 51%,rgba(144,0,0,1) 56%,rgba(192,0,0,1) 100%); /* Chrome10+,Safari5.1+ */
        background: -o-linear-gradient(top,  rgba(192,0,0,1) 0%,rgba(144,0,0,1) 51%,rgba(144,0,0,1) 56%,rgba(192,0,0,1) 100%); /* Opera 11.10+ */
        background: -ms-linear-gradient(top,  rgba(192,0,0,1) 0%,rgba(144,0,0,1) 51%,rgba(144,0,0,1) 56%,rgba(192,0,0,1) 100%); /* IE10+ */
        background: linear-gradient(top,  rgba(192,0,0,1) 0%,rgba(144,0,0,1) 51%,rgba(144,0,0,1) 56%,rgba(192,0,0,1) 100%); /* W3C */
    filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#c00000', endColorstr='#c00000',GradientType=0 ); /* IE6-9 */
    #sideleft {
        float: left;
        width: 19.0%;
        font-family: eurofurence, "Tekton Pro", Tahoma, sans-serif;
        font-size: 18px;
        font-weight: bold;
        color: #FFF;
        background-color: #222;/*Some browsers will not recognize RGBA colors*/
        background-color: rgba(0,0,0,0.6);/*RGBA fourth value for opacity, if there are two rules that apply to the same element, the latter of the two takes priority.*/
        text-align: center;
        height: 300px;
        border-radius: 10px;
        border:1px solid #888;
        padding-top: 0px;
        margin-top: 25px;
    .mywork {
        font-family: eurofurence, "eurofurence light", tahoma, sans-serif;
        font-size: 30px;
        font-style: normal;
        font-weight: bold;
        font-variant: normal;
        text-transform: none;
        color: #C00;
        text-align: center;
        line-height: 60px;
    .categoriessmall {
        font-family: eurofurence, "eurofurence light", tahoma, sans-serif;
        font-size: 16px;
        font-style: normal;
        line-height: normal;
        font-weight: normal;
        font-variant: normal;
        text-transform: uppercase;
        color: #FFF;
        text-align: left;
        display: block;
        margin-left: 15px;
        border-bottom-width: 1px;
        border-bottom-style: solid;
        border-bottom-color: #C00;
        margin-right: 10px;
    .sideleft-text {
        padding-top: 75px;
    a.sideleft, a.sideleft:link, a.sideleft:visited {
        display:block;
        margin-top:4px;
        text-align:left;
        text-decoration:none;
        font-family:eurofurence, "eurofurence light", tahoma, sans-serif;
        font-size:14px;
        color:#FFF;
        line-height:20px;
        overflow:hidden;
        border-top-style: none;
        border-right-style: none;
        border-bottom-style: none;
        border-left-style: none;
        font-style: normal;
        font-weight: normal;
        font-variant: normal;
        text-transform: none;
        margin-left: 15px;
        white-space: nowrap;
    a.sideleft:hover {
        color:#999;
    a.sideleft:active {
        color:#C00;
    #mainright {
        float: right;
        width: 75.5%;
        font-family: eurofurence, "eurofurence light", tahoma, sans-serif;
        color: #FFF;
        text-decoration: none;
        height: 700px;
        text-align: left;
        background-color: #000000;/*Some browsers will not recognize RGBA colors*/
        background-color: rgba(0,0,0,0.6);
        margin-left: 0px;
        margin-top: 25px;
        margin-right: 0px;
        margin-bottom: 10px;
        border-radius: 10px;
        border:1px solid #888;
        z-index: -3;
        padding: 0px;
    .categories {
        font-family: eurofurence, "eurofurence light", tahoma, sans-serif;
        font-size: 36px;
        font-style: normal;
        font-weight: normal;
        font-variant: normal;
        text-transform: uppercase;
        color: #808080;
        text-decoration: none;
        border-bottom-width: 2px;
        border-bottom-style: solid;
        border-bottom-color: #C00;
        float: none;
        position: relative;
        clear: none;
        left: 0px;
        z-index: auto;
        margin-right: 50px;
        margin-left: 20px;
    .img
        height:auto;
        width:auto;
        float:left;
        text-align:center;
        border-top-style: none;
        border-right-style: none;
        border-bottom-style: none;
        border-left-style: none;
        color: #FFF;
        font-family: eurofurence, "eurofurence light", tahoma, sans-serif;
        font-size: 18px;
        padding: 0px;
        margin-top: 0px;
        margin-right: 10px;
        margin-bottom: 0px;
        margin-left: 10px;
    .img img
        display:inline;
        margin:10px;
        border:1px solid #333;
    .img a:hover img
        border:1px solid #900;
    .image desc
        text-align:center;
        font-weight:normal;
        width:120px;
        margin:2px;
        font-family: eurofurence, "eurofurence light", tahoma, sans-serif;
        font-size: 16px;
        color: #FFF;
        text-decoration: none;
        font-style: normal;
        line-height: normal;
        font-variant: normal;
        text-transform: none;
    #footer {
        clear: both;
        width: 100%;
        font-family: eurofurence, "Tekton Pro", Tahoma, sans-serif;
        font-size: 12px;
        font-style: normal;
        font-weight: normal;
        text-align: center;
        margin-left: 0px;
        color: #FFF;
        margin-bottom: 0px;
        margin-top: 10px;
        padding-left: 10%;
        padding-right: 15px;
    body {
        background-image: url(../images/background_large.jpg);
    </style>
    </script>
    <script src="../spryassets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="../spryassets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    <link href="../styles/automanualslideshow.css" rel="stylesheet" type="text/css" />
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    </head>
    <body>
    <div id="container">
      <div id="header">
      <div class="jld_logo">
      <a href="file:///C|/Users/Roxane/Desktop/index.html">
      <img src="../images/jeff_danielson_logo_reverse.png" alt="Jeff Danielson logo" name="jld_logo" width="60" height="60" id="jld_logo" longdesc="images/jeff_danielson_logo_reverse.png" />
        </a>
      </div></div>
      <div id="navigation">
        <ul id="MenuBar1" class="MenuBarHorizontal">
          <li><a href="#">Home</a>      </li>
          <li><a href="#" class="MenuBarItemSubmenu">About Jeff</a>
            <ul>
              <li><a href="#">Biography</a></li>
              <li><a href="#">News</a></li>
            </ul>
          </li>
          <li><a class="MenuBarItemSubmenu" href="#">My Work</a>
            <ul>
              <li><a href="file:///C|/Users/Roxane/Desktop/recent_photographs.html">Recent Photographs</a></li>
            <li><a href="file:///C|/Users/Roxane/Desktop/flowers_leaves_moss.html">Flowers/Leaves/Moss</a></ li>
            <li><a href="file:///C|/Users/Roxane/Desktop/forests_trees_valleys.html">Forests/Trees/Valleys</ a></li>
            <li><a href="file:///C|/Users/Roxane/Desktop/deer_dogs_creatures.html">Deer/Dogs/Creatures</a></ li>
            <li><a href="file:///C|/Users/Roxane/Desktop/lakes_rivers_streams.html">Lakes/Rivers/Streams</a> </li>
            <li><a href="file:///C|/Users/Roxane/Desktop/clouds_skis_fog.html">Clouds/Skies/Fog</a></li>
            <li><a href="file:///C|/Users/Roxane/Desktop/birds_butterflys_insects.html">Birds/Butterflys/Ins ects</a></li>
            <li><a href="file:///C|/Users/Roxane/Desktop/panoramas.html">Panoramas</a></li>
            <li><a href="file:///C|/Users/Roxane/Desktop/fall_winter_spring_summer.html">Fall/Winter/Spring/ Summer</a></li>
            </ul>
          </li>
          <li><a href="#" class="MenuBarItemSubmenu">Pricing</a>
            <ul>
              <li><a href="#url">Size</a></li>
            <li><a href="#url">Mats</a></li>
            <li><a href="#url">Frames</a></li>
            <li><a href="#url">Frames & Mats</a></li>
            </ul>
          </li>
          <li><a href="#">Contact</a></li>
          <li><a href="#" class="MenuBarItemSubmenu">Runciple Spoon</a>
            <ul>
              <li><a href="#">The 1970's</a></li>
              <li><a href="#">The 1980's</a></li>
              <li><a href="#">The 1990's</a></li>
              <li><a href="#">The 2000's</a></li>
            </ul>
          </li>
        </ul>
      </div>
      <!-- TemplateBeginEditable name="Sideleft" -->
      <div id="sideleft"> <span class="mywork">My Work</span> <span class="categoriessmall">Categories</span> <a class="sideleft" href="../recent_photographs.html" title="">Recent Photographs</a> <a class="sideleft" href="../flowers_leaves_moss.html" title="Flowers/Leaves/Moss">Flowers/Leaves/Moss</a> <a class="sideleft" href="../Forests/Trees/Valleys.html" title="Forests/Trees/Valleys">Forests/Trees/Valleys</a> <a class="sideleft" href="../Deer/Dogs/Creatures.html" title="Deer/Dogs/Creatures">Deer/Dogs/Creatures</a> <a class="sideleft" href="../Lakes/Rivers/Streams.html" title="Lakes/Rivers/Streams">Lakes/Rivers/Streams</a> <a class="sideleft" href="../Clouds/Skies/Fog.html" title="Clouds/Skies/Fog">Clouds/Skies/Fog</a> <a class="sideleft" href="../Birds/Butterflys/Insects.html" title="Birds/Butterflys/Insects">Birds/Butterflys/Insects</a> <a class="sideleft" href="../Panoramas.html" title="Panoramas">Panoramas</a> <a class="sideleft" href="../Fall/Winter/Spring/Summer.html" title="Fall/Winter/Spring/Summer">Fall/Winter/Spring/Summer</a></div>
      <!-- TemplateEndEditable --><!-- TemplateBeginEditable name="Mainright" -->
      <div id="mainright"></div>
      <!-- TemplateEndEditable -->
      <div id="footer">
      © 2012 Jeff Danielson Brown County Indiana Photography</div>
    <!--Content for container goes here--></div>
    <script type="text/javascript">
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    </script>
    </body>
    </html>

  • Template: Adding Site Wide Code To Editable Region

    I have a template
    I have an editable region called content
    I would now like to add a navigation bar within the editable region, so that it can be managed from the Template and thereon aplies to the child pages
    Q:
    How do I insert a site wide section within an editable region, which is only edited via the template, so that I can set up my navigation bar?
    woolf

    So, here's a sample page: http://www.gravenimagedesign.net/levnav/
    Here's the 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>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Untitled Document</title>
    <!-- TemplateEndEditable -->
    <style type="text/css">
    <!--
    #header {
         background-color: #333;
         height: 200px;
         width: 800px;
         position: relative;
         margin: 0 auto;
    #header h1 {
         color: white;
    #content {
         background-color: #FFC;
         height: 500px;
         width: 800px;
         margin: 0 auto;
         border: 1px solid red;
         position: relative;
    #content h1 {
         color: red;
         text-align: center;
    #apDiv1 {
         position:absolute;
         width:663px;
         height:115px;
         z-index:1;
         left: 63px;
         top: 438px;
         background-color: #FCF;
    -->
    </style>
    <script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    </head>
    <body>
         <div id="header"><!--begin header-->
           <h1>This header div is position: relative;</h1>
           <div id="apDiv1">
             <ul id="MenuBar1" class="MenuBarHorizontal">
               <li><a class="MenuBarItemSubmenu" href="#">Item 1</a>
                 <ul>
                   <li><a href="#">Item 1.1</a></li>
                   <li><a href="#">Item 1.2</a></li>
                   <li><a href="#">Item 1.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 2</a></li>
               <li><a class="MenuBarItemSubmenu" href="#">Item 3</a>
                 <ul>
                   <li><a class="MenuBarItemSubmenu" href="#">Item 3.1</a>
                     <ul>
                       <li><a href="#">Item 3.1.1</a></li>
                       <li><a href="#">Item 3.1.2</a></li>
                    </ul>
                  </li>
                   <li><a href="#">Item 3.2</a></li>
                   <li><a href="#">Item 3.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 4</a></li>
            </ul>
             <p><br />
            This menu bar is <strong>position: absolute;</strong></p>
             <p>It is  nested in the code inside the &quot;header&quot; div (the dark grey one), which is positioned &quot;relative.&quot;</p>
          </div>
         </div><!--end header-->
         <div id="content">
           <!--begin content-->
           <!-- TemplateBeginEditable name="EditRegion3" -->
           <h1>This text (really an h1) is appearing within the div with id of "content"</h1>
           <!-- TemplateEndEditable --></div>
         <!--end content-->
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
        </script>
    </body>
    </html>
    And here's a child 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"><!-- InstanceBegin template="/Templates/maintemplate.dwt" codeOutsideHTMLIsLocked="false" -->
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- InstanceBeginEditable name="doctitle" -->
    <title>Untitled Document</title>
    <!-- InstanceEndEditable -->
    <style type="text/css">
    <!--
    #header {
         background-color: #333;
         height: 200px;
         width: 800px;
         position: relative;
         margin: 0 auto;
    #header h1 {
         color: white;
    #content {
         background-color: #FFC;
         height: 500px;
         width: 800px;
         margin: 0 auto;
         border: 1px solid red;
         position: relative;
    #content h1 {
         color: red;
         text-align: center;
    #apDiv1 {
         position:absolute;
         width:663px;
         height:115px;
         z-index:1;
         left: 63px;
         top: 438px;
         background-color: #FCF;
    -->
    </style>
    <script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    <!-- InstanceBeginEditable name="head" -->
    <!-- InstanceEndEditable -->
    </head>
    <body>
         <div id="header"><!--begin header-->
           <h1>This header div is position: relative;</h1>
           <div id="apDiv1">
             <ul id="MenuBar1" class="MenuBarHorizontal">
               <li><a class="MenuBarItemSubmenu" href="#">Item 1</a>
                 <ul>
                   <li><a href="#">Item 1.1</a></li>
                   <li><a href="#">Item 1.2</a></li>
                   <li><a href="#">Item 1.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 2</a></li>
               <li><a class="MenuBarItemSubmenu" href="#">Item 3</a>
                 <ul>
                   <li><a class="MenuBarItemSubmenu" href="#">Item 3.1</a>
                     <ul>
                       <li><a href="#">Item 3.1.1</a></li>
                       <li><a href="#">Item 3.1.2</a></li>
                    </ul>
                  </li>
                   <li><a href="#">Item 3.2</a></li>
                   <li><a href="#">Item 3.3</a></li>
                </ul>
              </li>
               <li><a href="#">Item 4</a></li>
            </ul>
             <p><br />
            This menu bar is <strong>position: absolute;</strong></p>
             <p>It is  nested in the code inside the &quot;header&quot; div (the dark grey one), which is positioned &quot;relative.&quot;</p>
          </div>
         </div><!--end header-->
         <div id="content">
           <!--begin content-->
           <!-- InstanceBeginEditable name="EditRegion3" -->
           <h1>This text (really an h1) is appearing within the div with id of &quot;content&quot;</h1>
           <!-- InstanceEndEditable --></div>
         <!--end content-->
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
        </script>
    </body>
    <!-- InstanceEnd --></html>
    I arbitrarily positioned the nav in the middle of the action. You can play with its positioning, but remember that it is positioned "absolutely" from the left and top of the "header" div. (in this case)
    If this is unclear, let me know! By the way, the CSS is in the head of the Template, and the child page, but I didn't print out the other auxiliary files, which you will get automatically if you insert a SpryMenuBar. But the sample on my site will work...
    Beth

  • HOW TO LINK PAGE IN TEMPLATE EDITABLE REGION

    Hi to all friends out there .I am new to this .I want to know how to link existing page or link in editable region of template.Please guide me.
    My template is ready but i do not know how to link existing pages in editable region of template.
    Every help is appreciated.if code also you can show me than it will be helpfull.
    Thanks in advance.

    Editable regions are for content that will change from page to page.
    Anything outside the editable regions will appear in all pages spawned from the Template.  This gives your site a consistent look.
    Ideally, you want to put common menus, headers, footers and sidebars into NON-EDITABLE regions, right?
    Open main Template (.dwt) file.
    Highlight menu item.
    On the properties panel there is a link field with a small folder icon next to it.
    Click the folder icon and browse to the site page.  Click OK.
    Repeat with additional links.  Save your main Template.dwt file and populate changes to child pages.
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

Maybe you are looking for

  • Itunes purchases are gone on my iPhone 5.

    I've purchased 3 audiobooks on iTunes. When clicking on purchases in iTunes the purchases are gone. If i search for the book and click on purchase I get the message that I already bought them but I still can't download them without repurchasing. What

  • Can v run dunning for vendors

    Hi , where can v link dunning area and dunning procedure and how can v use dunning for vendors Points wil b assigned Umesh

  • Install New SD Card

    I'm replacing the 1GB card with a 16 GB card,  Whats the easiest way to transfer the data to the new card? Copy and paste everything via Windows Explorer? Backup and Restore via Desktop Manager? Device Switch Wizard via Desktop Manager? Or something

  • WRT600N and AIM service disconnects

    I've been diagnosing a problem related to my Palm Pre on Wifi connected to my WRT600N router, Firmware revision 1.01.36 build 4.  It seems to be that when the Palm is idling and not sending data over AIM for quite a few minutes that it'll disconnect

  • Actions - Time of Processing

    Hi CRM Gurus, I have 2 questions. 1. In CRM config,(crmc_action_conf) , we have Time of Processing where we can tell when to process the action based on following options.   1. Immediate processing.   2. When Saving   3. Process using Selection Repor