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

Similar Messages

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

  • Making this change would require changing code that is locked by a template of translator.

    Hello,
    I see a lot of the same questions.
    In my case however I use no templates or translators in my file.
    I use several included files, but they have no head or body tags inside of them.
    The message popped up when I tried to convert this file:
    The International Lymphedema Guest Book: Behandeling
    in Dreamweaver from html strict to xhtml 1 transitional.
    What can be the problem?
    Thanks in advance,
    Yvon

    Hello Ken and  Snakeyez,
    Thank you for helping me.
    Here are the included files.
    Last night we thought it was a problem with the server settings.
    The settings are adapted, and now the included files do show up in the browser.
    But when I tried to convert the doctype in Dw just now, the same message turned up, so this problem isn't solved yet.
    Yvon
    bottom.html:
    <!--START OF BOTTOM-->
    <table border="0">
    <tbody>
    <tr>
    <td>
    <a href="#bottom"><img src="tekeningen/olifant1.gif" alt="[Image: Elephant]"></a>
    </td>
    <td style="color: #909; background-color: transparent;">
    <a href="#bottom">Go to the bottom of this page</a>
    </td>
    </tr>
    </tbody>
    </table>
    <!--END OF BOTTOM-->
    top.html:
    <!--START FILE TOP.HTML-->
    <table border="0">
    <tbody>
    <tr>
    <td>
    <a id="bottom" href="#top"><img src="tekeningen/olifant1.gif" alt="[Elephant]" width="80" height="60"></a>
    </td>
    <td style="color: #909; background-color: transparent;">
    <a href="#top">Go to the top of this page</a>
    </td>
    </tr>
    </tbody>
    </table>
    <!--END FILE TOP.HTML-->
    disclaimer.html:
    <!--DISCLAIMER-->
    <div style="background-color:#fef;color:#000;">
    <a id="disclaimer">DISCLAIMER</a>:
    THE OWNER OF THIS WEBSITE IS NOT RESPONSIBLE FOR THE CONTENT OF THE LINKS
    NOR FOR THE CONTENT OF THE MESSAGES IN THE GUESTBOOK.</div>
    <!--END OF DISCLAIMER-->
    copyright.html:
    <!--COPYRIGHT INFORMATION-->
    <p style="font-size:10pt;">
    This page is &copy;1999-2014,
    <a href="http://www.weezenhof.com">Weezenhof.com Webdesign</a>
    <br>
    Yvonne Janssen, Weezenhof 34-37, 6536 GP Nijmegen, the Netherlands
    </p>
    <!--END OF COPYRIGHT INFORMATION-->

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

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

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

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

  • Editable region in template not editable??

    I'm trying to add a Spry Image Slideshow (basic) to several files in Dreamweaver CS5. I have set up templates, and in the child pages, when I try to insert the widget it just says: "Making this change would require changing code that is locked by a template or translator. The change will be discarded." I have a Spry menu already on the page (although it doesn't show up on my laptop but does on my desktops).  What should I do?  A sample page is already uploaded here:  http://www.tomandlauriereese.com/bands/muzette/muzette.html.  I'm trying to add the photos to Col1 (an editable region).  Col2 allows me to add content, but Col1 won't.  Actually, I can't add anything to Col3 either (it's set up as an iframe right now).
    Please help!  Let me know what other information  you need; I'm new to this!
    Thanks,
    Laurie Reese, cellist

    I'm not really piling on here, but I'm confident your extensive use of absolute positioning is going to sadly return to bite you on this very nice looking layout.  Add some real-world content to one of those text regions, preview in the browser and start increasing the size of the text in the browser.  You'll get an overflowing mess in a hurry.
    I chose the doctype of xhtml 1.0 Transitional.  I'm not sure which type is best for this type of page.  I also tried html 4.0 Transitional, but still no luck.
    A doctype only does two things: a) it informs a validator of how to validate the code on the page, and b) it informs the browsers whether to render the page in quirks more or standards mode.  Because it's useful to be able to use validation as your first line of defense when encountering layout issues, you should therefore choose a doctype that is consistent with your skill and knowledge as a coder (as a first-order approximation).  In your case, I'm pretty sure that would be HTML 4.01 Transitional.  You can have DW do this for you by opening the template page and using FILE | Convert > HTML 4.01 Transitional.  Be aware that this will only affect the content in NON-editable regions of your child pages as is expected with any template changes.
    I did notice that the Head editable region is way underneath all the other code; it's at line 506; but there's nothing in there.  Should I move the "<!-- TemplateBeginEditable name="head" --> to the top somewhere?
    As long as that region is actually in a legal location between <head> and </head> it doesn't matter where it is.  Since it is, then you can just leave it.
    What should be in that region?
    This is the region that allows you to add javascript behaviors to child pages, like image swaps, or show/hide divs, or even page-specific stylesheet/javascript links.  Without it, you could not do that.
    Where is it you are trying to add this widget?  Which editable region?

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

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

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

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

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

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

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

  • 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

  • Fluid grid template - editable region - resize not possible

    Hi,
    After quitting DW the first resizing problem was gone.
    Now I saved the page as a template and inserted an editable region.
    Then it wasn't possible anymore to recize the divs.
    The lines are know yellow dotted.
    Do I have to make editable regions in a different way?
    See: http://www.ifacilityservices.nl/index.html
    Thanks again.
    Carla

    Hi Nancy,
    Thanks voor your reply!
    Is it now not possible anymore?
    I deleted the editable regions, but it stays with the yellow lines.
    Carla
    Van: Nancy O. [email protected]
    Verzonden: zaterdag 24 augustus 2013 21:59
    Aan: Carla Leliveld
    Onderwerp: fluid grid template - editable region - resize not possible
    Re: fluid grid template - editable region - resize not possible
    created by Nancy O. <http://forums.adobe.com/people/Nancy+O.>  in Dreamweaver CC - View the full discussion <http://forums.adobe.com/message/5623512#5623512

  • Blocked by template or translator

    Hi,
    Can someone please tell me what I have to do in order to be
    able to put a table on the page.
    If its reconstructing the template thats fine but what did i
    do wrong?
    Code attached.

    > Can someone please tell me what I have to do in order to
    be able to put a
    > table on the page.
    <p align="left"><!-- InstanceBeginEditable
    name="EditRegion3"
    --><font
    color="#FF9900" size="3"><br />
    <br />
    </font><!--
    InstanceEndEditable --><br />
    </p>
    The editable region is INSIDE of a <P> paragraph tag
    and a <blockquote> tag.
    Try this-
    Open the template file
    click into Editable Region 3
    In the quick tag selector (list of tags at bottom left of
    design window)
    right-click on that <p> tag and pick Delete tag. Same
    for the <blockquote>
    tag. Save the template. Can you insert a table now?
    Next issue:
    Most of the link paths have Templates/ in the path.
    <a href="Templates/photos.html">Photos</a> |
    <a
    href="Templates/Budget.html">Budget</a> | <a
    href="Templates/bylaws.html">Bylaws</a> | <a
    href="Templates/awards.html">Awards</a>
    1. Only .dwt template files go into the Templates folder. No
    other files. No
    images, no css, no html pages.
    2. The links should work IN the template file. so open the
    .dwt template,
    and File-->Check Page-->Check Links. Fix all the broken
    links by using the
    browse to file dialog box to pick the actual file you want to
    link to.
    If the file photos.html is in the root level of the local
    site folder, a
    link to it in the template should be either:
    <a href="/photos.html">
    or
    <a href="../photos.html">
    and not:
    <a href="photos.html">
    Alan
    Adobe Community Expert, dreamweaver
    http://www.adobe.com/communities/experts/

  • Reformatting editable region on template.

    I have several pages created off a template that has an editable region.  I want to reformat the editable region in the template, such as adding a new DIV, creating borders on it, and adding an image placeholder.
    When I do this, the pages created from the template don't change also.
    If I remove the editable region from the template, put in the format changes, then put the editable region back in, then all the pages I had created earlier lose their content.
    Is there a way to do these format changes, make them flow through to the dependent pages and not lose the content on those pages?
    Thanks,
    Aron

    Aron,
    To "reformat" an editable area on a template, create the div and structure OUTSIDE the editable area. That is, "wrap" the editable area in a div and apply style via CSS. The image placeholder is something you can place in the template, but it will not update on pages that have already been created from the template. The new div will be applied on all pages, because it will not be in the editable region.
    Beth

  • Can't edit editable region in frames

    Hello, my name is justine and i am trying to edit an area in the website i am making by using frames. I have made the #maincontent area editable and i can type in the area but it wont let me edit the CSS rule for #maincontent (text colour,size etc). when i do try it comes up with:
    "Making this change would require changing code that is locked by a template or translator. The change will be discarded"
    I do all my work through the design view and don't know much about html. if you could have a look at the html and give me any ideas on how to solve this would be very much appreciated:
    </div>
      <!-- InstanceBeginEditable name="EditRegion" -->
      <div id="mainContent">
        <h1>Index (Home)</h1>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <p>   </p>
        <!-- end #mainContent -->
      </div>
      <!-- InstanceEndEditable -->
      <!-- This clearing element should immediately follow the #mainContent div in order to force the #container div to contain all child floats --><br class="clearfloat" />
      <!-- end #container -->
    </div>
    in between all of the <p>  <p/> is "&.n.b.s.p.;" (no full stops)  but it wont show up in the forum for some reason
    Thanks

    First off, I suggest that you go back and recreate your pages without using frames, which are collections of html pages tied into one frameset for presentation. Frames are not easy to use, and have many strikes against them, notably that they are not bookmarkable, you can't use the back browser button reliably, etc. I could go on and on but will not.
    Second, if you have not already done so, I encourage you to do some great tutorials on the Adobe site. That will boost your knowledge a great deal, as well as your confidence in what you are doing. http://www.adobe.com/devnet/dreamweaver/css.html
    Many of us would like to work mainly in Design View, but you will find the real power behind the Dreamweaver tools in learning some XHTML and Cascading Style Sheets along the way.
    Your phrase, "I have made the #maincontent area editable" implies to me that you have made a page and created a Template from it. If that is not the case, then it is a byproduct of having been working in Frames. I don't really see how that could be, but error messages may be thrown by particular situations that might occur, both in a 'normal' page and in a 'Frames' page.
    If your site is relatively straightforward, I do encourage you to discard the Frames approach and join us in the div/CSS world!
    Best,
    Beth

Maybe you are looking for

  • Can I see which of my skype number has been dialle...

    Hi, I have 4 skype numbers but would like to see when i receive a call which number was dialled.  Is this possible. I would also like to have different answer messages set up for each number, again is this possible. Many thanks

  • Font size issues..

    for example 8pt doesn't look like 8pt, how do I fix this problem?

  • Transfer Itunes from Hope PC to New Laptop

    Good Morning, I bought a new laptop and would like to get some opinions on the best way to copy my Itunes software/Library from my home PC to my laptop. One of my main questions are, should I down load the Itunes software to my lap top prior to tryin

  • Motorolla RF scanners getting disconnect and connecting back

      Hi i have deployed wlc 5508 with software 6.0.199.4 . AP 1142 . Customer have few motorola RF scanners which i added the mac address in mac filter and its working. Now cust informed that these scanners get sometime diconected in between and connect

  • Clear/Delete alert message in CCMS

    Hi, I have a red alert message in RZ20 (CCMS monitor) in the node called QRFC Queues - Exactly-Once Processing Queues - Int. Server Outbound Messages (XBTO*) - Blocked queues: Client 100 It's a message that failed a week ago, and the message is now c