Adding keywords to child pages

I'm trying to add keywpords and descriptions to individual
pages, yet the template code keeps locking me out. Murray had
suggested inserting them in the 'editable' region, yet that gets
blocked too. Can you show me exactly where in the code to insert
this? Here's a link, thanks!
http://www.robinbachnia.com/index1.htm

Right under this -
<!-- InstanceBeginEditable name="head" -->
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
==================
"Bushido" <[email protected]> wrote in
message
news:fo7gic$rgi$[email protected]..
> I'm trying to add keywpords and descriptions to
individual pages, yet the
> template code keeps locking me out. Murray had suggested
inserting them in
> the
> 'editable' region, yet that gets blocked too. Can you
show me exactly
> where in
> the code to insert this? Here's a link, thanks!
>
http://www.robinbachnia.com/index1.htm
>

Similar Messages

  • Child pages

    Hello,
    I posted a discussion yesterday, but i'm still slightly confused on something. Apologies if this is a silly question, i'm a complete novice at using Muse so i'm kind of learning as i go along!
    The site i'm making on Muse is a site which holds a catalogue of products. I have a page will all the brand names on, then master pages for the seperate brands with icons/links for the products, then underneath i add all the single product pages with the info/price/image on etc.
    As each brand has about 20 products each, my Muse screen is looking slightly chaotic, and rather long horizontally in plan mode.
    My question is - Can i add a Child page under a product (for another product) so that my screen isn't going to be really long? When i go to link the page which i've added under the child page the link looks like this > Ortofon (*brand page) > MC1 Turbo (*child page) > OM5E (*child page underneath mc1 turbo)
    When customers click on the OM5E logo, will it take them straight to that product page? I'm confused with the MC1 Turbo?
    I've inserted a screenshot below of what i mean -
    Any help would be great                      

    Just wait until next month. There Muse 5 will be published. It has the option to "collapse" those constructions virtually.
    If you sign in to the Muse Beta Programm, (Help-Menu), you can use this feature at once.

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

  • Link to spry css broken in template or child pages

    Hi,
    on the following pages the spry menu is not displaying properly.  I did notice that in the template pages the link ref was missing ../ at the beginning.  Having added this and updated the templates and child pages (these were also uploaded to the server) I thought that would solve the problem.  But it doesn't look as though the change in the link ref has updated correctly.
    http://davidcoshdesign.com/nea/lighting_decorative.html
    http://davidcoshdesign.com/nea/lighting_functional.html
    http://davidcoshdesign.com/nea/news.html
    http://davidcoshdesign.com/nea/links.html
    http://davidcoshdesign.com/nea/blog.php
    Any pointers, would be great.
    Second url: 
    http://davidcoshdesign.com/nea/lighting_functional_wall.html
    This one appears not to be linking properly to the template?  At leats, I think that's the problem.  The template is in the correct folder and uploaded to the server.
    I have noticed on this site that when I make a new page based on any of the site templates, when I look at the coding in DW, there are references to the local site 'root' folder.
    Have I messed up the links to templates etc on site-wide basis?  Do I need to go into 'Manage Sites' to sort this out?

    No, just a reoccurring problem, for someone who constantly struggles witht the vagaries of html.
    RP

  • Template do not update child pages

    I really do not understand why this happens to me all the time.
    I had this problem when I was using windows/pc with previous version of dreamweaver many years ago.
    I had the same one, now that I am using mac and dreamweaver cs4.
    In the past, I created a template, with one editable region. Based on this template, I created many pages.
    For some time, everything worked ok, every change in editable region of template forced all child pages to reflect to this change too.
    Now, this do not happen anymore(once again as I said).
    I cannot understand why this happens. 118 files examined, 0 files updated. Why? What am I doing wrong? Is this a bug in dreamweaver that lasts for years?
    I 've done nothing to detach the pages from template, ever. Why it stoped the updating of child file?
    Can anybody please help me?

    giugiugiugiugiugiugi wrote:
    I really do not understand why this happens to me all the time.
    I had this problem when I was using windows/pc with previous version of dreamweaver many years ago.
    I had the same one, now that I am using mac and dreamweaver cs4.
    In the past, I created a template, with one editable region. Based on this template, I created many pages.
    For some time, everything worked ok, every change in editable region of template forced all child pages to reflect to this change too.
    Now, this do not happen anymore(once again as I said).
    I cannot understand why this happens. 118 files examined, 0 files updated. Why? What am I doing wrong? Is this a bug in dreamweaver that lasts for years?
    I 've done nothing to detach the pages from template, ever. Why it stoped the updating of child file?
    Can anybody please help me?
    You say "every change in editable region of template forced all child pages".  This is NEVER how DW has operated.  It's only changes to NON-EDITABLE regions that are propagated to child pages.  I suspect that this misunderstand is what is causing you trouble, but if not, read this -
    Here are seven common mistakes that will result in changes not propagating from Template to child -
    1.  Rename the Templates folder
    2.  Move the Templates folder to some other folder level in the site other than root level
    3.  Move a template out of the Templates folder.
    4.  Make changes to an editable region of the Template (which will not propagate)
    5.  Assume that Template changes will be effected by just uploading the changed Template file to the server without also uploading the changed local files
    6.  Corrupt the site cache so that the link between Template and child page is broken
    7.  Improperly create your child pages by simply opening the Template, adding page specific content, and resaving the Template with an *.html extension rather that its *.dwt extension. (you can tell if this is the case by looking at the code on a child page - if you see anything like <!-- TemplateBeginEditable... then this is what you have done).  If you *have done this*, then recreate the child pages (in DWCS3) using FILE | New > Page from Template, select the Template and click CREATE.
    The 6th problem can be repaired by using SITE | Advanced > Recreate Site Cache, and the six others can be fixed by just not doing them.  Have you done any of those?
    Or, read this -
    http://www.adobe.com/go/dd83ba8b

  • Problem applying Spry tool tips to child pages because the head tag is in a locked region

    I’m new to DW and migrating a site from GoLive CS2 to DW CS5. The site uses templates created in GL CS2. I have stripped out as much GL stuff as possible.
    I want to use the SPRY tooltips as a way to show captions for graphics that are on some of the pages (I used to use an Open New Browser window for that but I don’t have as much control in DW as I did in GL). But when I try to apply SPRY tooltips (or any SPRY widget for that matter) I get the following message:
    “Required links could not be added to this file because the <head> tag is in a locked region. To insert this content, open the template file ‘xyz.dwt’ and either unlock the <head> tag or add this content to the template.”
    I am not sure how to go about solving this problem. In the template there is an editable region for adding graphics but in the template itself there are no graphics or anything else to apply a tooltip too. Also in the child pages there may be more than one place to use a tooltip. So that suggests to me that I should not add a tooltip to the template. That brings me to the other option.
    How would I go about unlocking the  <head> tag in the template, without messing everything up?
    Or, should I detach any page from the template when I want to add tooltips then reapply the template? I am planning to ditch the GL template anyway and apply a DW template to all the pages anyway.
    Any suggestions as to what I should do?
    Yours faithfully
    Branko
    PS I’m using Mac with Snow Leopard.

    I found a solution.
    I just made a transparent PNG. Put it in an inconspicuous part of the template. On the child page I could make as many copies as I needed making sure I provided id tags for each use etc.

  • Template not updating child pages

    Hi,  here's a link to the conundrum:
    http://theexperience-exchange.co.uk/stop.html
    This page (as are a few others) is based on a template document (stored in a Templates folder in the site root).
    I added an editable region in the form of a new div with some text etc.  When I do a 'save' I get the update files dialogue box, but it doesn't update the child pages.
    I did look on the forum for an answer, althought there are similar examples of this issue, they don't seem to have had any dircet help.
    As ever, any ideas would be greatly appreciated. 
    I'm signing off for the night, catch up with you all in the morning.
    Thanks in anticipation
    RP

    Let's start with the obvious things.
    1. Are you sure you're editing the correct template.dwt file? 
    Your Stop.html page is referencing this one.   internal_pages.dwt
    2. After saving your template and updating the child pages, did you upload the child pages to your server?
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

  • Template and child pages do not match

    Hi, there are several issues here and I'm pretty sure they're linked so I'll tell you them all. I was recently editing my website and I was changing the title of a page a created. I noticed that after I changed the name, when I clicked off it it just went back to the default title in the template. I then looked up how to sort and I think I changed a few bit of coding (I can't remember what though, sorry. It seemed to work. Then I decided to add another page which I listed in the navbar... when I got round to pressing save on the template, this happened....
    (http://ScrnSht.com/vttvzm)
    I'm sorry to sound so vague but I can't really remember what I did. Anyway, it says this for nearly every page when you save the template. I've noticed some of the coding on the template and the child pages do not match. This is the code on the template.
    <!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" xmlns:ice="http://ns.adobe.com/incontextediting">
    <head><link href="../Img/favicon.ico" rel="shortcut icon" />
    <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
    <link href="../style.css" rel="stylesheet"  type="text/css" ice:classes="*" />
    <link href="../Img/favicon.ico" />
    <meta property="fb:page_id" content="182170851815699" />
    <script src="../includes/ice/ice.js" type="text/javascript"></script>
    <meta name="description" content="The Mowhay Radio is a new radio station. Tune in every Friday night from 7:30pm (GMT) to hear your favourite tracks played and maybe even some you haven't heard before!" />
    <meta name="Keywords" content="The Mowhay Radio, Mowhay, Radio, Cornwall, Gabriel Lucas-Green, Music, Listen, Online, Station, Request, Fun, Games, Take Part, Songs, Tracks, Secret Sound, Celebrity Voice, Random Stuff, mowhayradio.co.uk, mowhayradio, mohay" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>The Mowhay Radio | </title>
    <!-- TemplateEndEditable --></head>
    <body>
    <div id="wrapper">
    <div id="header"><a href="../index.html"> <img src="../Img/logo.png" alt="" width="143" height="125" class="logo" title="The Mowhay Radio" /></a>
    <div id="nav">
    <ul>
    <li><a href="../index.html" class="">Home</a></li>
    <li><a href="../live/" target="_blank">Listen LIVE</a></li>
    <li><a href="../song_requests.html">Song Requests</a></li>
    <li><a href="../takepart/">Take Part</a></li>
    <li><a href="../about.html">About &amp; Links</a></li>
    <li><a href="http://www.facebook.com/MowhayRadio" target="_blank">News</a></li>
    <li><a href="../contact.html">Contact</a></li>
    </ul>
    </div> <!-- END NAV-->
    </div><!-- END HEADER-->
    <div id="content">
    <div id="col1">
    </div> <!-- END COL1-->
    <!-- TemplateBeginEditable name="main text" -->
    <div id="col2">
      <h1>Lorem Ipsum</h1>
      <p>
        <iframe src="http://www.facebook.com/plugins/like.php?href=www.facebook.com%2FMowhayRadio&amp;layout=standard&amp;show_faces=false&amp;width=350&amp;action=like&amp;font=verdana&amp;colorscheme=dark&amp;height=35" scrolling="No" frameborder="0" style="border:none; overflow:hidden; width:350px; height:35px;" allowtransparency="true"></iframe>
      </p>
      <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod   tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim   veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea   commodo consequat. Duis aute irure dolor in reprehenderit in voluptate   velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint   occaecat cupidatat non proident, sunt in culpa qui officia deserunt   mollit anim id est laborum.</p>
    </div>
    <!-- TemplateEndEditable -->
    <!-- END COL2-->
    <!-- TemplateBeginEditable name="Right sidebar" -->
    <div id="col3">
      <p> </p>
      <p>I love listening to this radio show. <br />
        &#9733;&#9733;&#9733;&#9733;&#9733; - Mitchell Wilson</p>
    </div>
    <!-- TemplateEndEditable -->
    <!-- END COL3-->
    </div>
    <!-- END CONTENT-->
    <div id="footer">
      <blockquote>
        <blockquote>
          <p>&copy; 2011 The Mowhay Radio  |  <a href="../contact.html">Contact</a> | <a href="../about.html">About &amp; Links</a> | <a href="../live/" target="_blank">Listen LIVE</a> | <a href="../song_requests.html">Song Requests</a> | <a href="../takepart/">Take Part</a><a href="../takepart/secret_sound.html"></a> | <a href="../disclaimer.html">Disclaimer</a> | Design by <a href="mailto:[email protected]">Igor Jovic</a></p>
        </blockquote>
      </blockquote>
    </div> 
    <!-- END FOOTER -->
    </div> <!-- END WRAPPER-->
    <!-- Start of StatCounter Code -->
    <script type="text/javascript">
    var sc_project=6645564;
    var sc_invisible=1;
    var sc_security="da714bb8";
    </script>
    <script type="text/javascript"
    src="http://www.statcounter.com/counter/counter.js"></script><noscript><div
    class="statcounter"><a title="click tracking"
    href="http://statcounter.com/" target="_blank"><img
    class="statcounter"
    src="http://c.statcounter.com/6645564/0/da714bb8/1/"
    alt="click tracking" ></a></div></noscript>
    <!-- End of StatCounter Code -->
    </body>
    </html>
    and this is the coding for another page. The index for example.
    <!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/template.dwt" codeOutsideHTMLIsLocked="false" --><!-- InstanceBegin template="/Templates/template.dwt" codeOutsideHTMLIsLocked="false" --><head>
    <title>The Mowhay Radio</title>
    <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ice="http://ns.adobe.com/incontextediting">
    <head><link href="Img/favicon.ico" rel="shortcut icon" />
    <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
    <link href="style.css" rel="stylesheet"  type="text/css" ice:classes="*" />
    <link href="Img/favicon.ico" />
    <meta property="fb:page_id" content="182170851815699" />
    <script src="includes/ice/ice.js" type="text/javascript"></script>
    <meta name="description" content="The Mowhay Radio is a new radio station. Tune in every Friday night from 7:30pm (GMT) to hear your favourite tracks played and maybe even some you haven't heard before!" />
    <meta name="Keywords" content="The Mowhay Radio, Mowhay, Radio, Cornwall, Gabriel Lucas-Green, Music, Listen, Online, Station, Request, Fun, Games, Take Part, Songs, Tracks, Secret Sound, Celebrity Voice, Random Stuff, mowhayradio.co.uk, mowhayradio, mohay" />
    <!-- InstanceBeginEditable name="doctitle" -->
    <title>The Mowhay Radio | </title>
    <!-- InstanceEndEditable --></head>
    <body>
    <div id="wrapper">
    <div id="header"><a href="index.html"> <img src="Img/logo.png" alt="" width="143" height="125" class="logo" title="The Mowhay Radio" /></a>
    <div id="nav">
    <ul>
    <li><a href="index.html" class="">Home</a></li>
    <li><a href="live/" target="_blank">Listen LIVE</a></li>
    <li><a href="song_requests.html">Song Requests</a></li>
    <li><a href="takepart/">Take Part</a></li>
    <li><a href="about.html">About &amp; Links</a></li>
    <li><a href="contact.html">Contact</a></li>
    </ul>
    </div> <!-- END NAV-->
    </div><!-- END HEADER-->
    <div id="content">
    <div id="col1">
    </div> <!-- END COL1-->
    <!-- InstanceBeginEditable name="main text" -->
    <div>
      <div id="col2">
        <h1> Welcome</h1>
        <p>
          <iframe src="http://www.facebook.com/plugins/like.php?href=www.facebook.com%2FMowhayRadio&amp;layout=standard&amp;show_faces=false&amp;width=350&amp;action=like&amp;font=verdana&amp;colorscheme=dark&amp;height=35" scrolling="No" frameborder="0" style="border:none; overflow:hidden; width:350px; height:35px;" allowtransparency="true"></iframe>
          </p>
        <p>Welcome to the Mowhay Radio website!</p>
        <p>
          <iframe src="http://www.countdownr.com/external.html?logo=http%3A%2F%2Fmowhayradio.co.uk%2FImg%2Fmr%2520countdown%2520badge.png&amp;alert=http%3A%2F%2Fk002.kiwi6.com%2Fhotlink%2Fy34m6855oc%2FCountdown_clock_noise.mp3&amp;time=2011_05_06_19_30&amp;title=The%20Mowhay%20Radio&amp;repeat=4&amp;url=http%3A%2F%2Fmowhayradio.co.uk&amp;background=transparent" frameborder="0" width="320" height="130" scrolling="No"><a href="http://www.countdownr.com">Countdownr</a></iframe>
        </p>
        <p>The Mowhay Radio is a new amateur radio station hosted by Gabriel Lucas-Green and based in Cornwall which   broadcasts a variety of musical genres. Tune in <strong>every Friday night from    7:30pm (GMT)</strong> to hear your favourite tracks played and maybe even some you haven't heard before!</p>
        <p>
          <object classid='clsid:D27CDB6E-AE6D-11cf-96B8-444553540000' width='350' height='197' id='single1' name='single1'>
            <param name='movie' value='http://mowhayradio.co.uk/jwplayer/player.swf' />
            <param name='allowfullscreen' value='true' />
            <param name='allowscriptaccess' value='always' />
            <param name='wmode' value='transparent' />
            <param name='flashvars' value='file=http://www.youtube.com/watch?v=KYwtW1Z7rZc&image=http://mowhayradio.co.uk/Img/mowhay__site_vid_thumbnail.jpg&backcolor=000000&frontcolor=999999&screencolor=000000&volume=35&controlbar=over&autostart=true' />
            <embed
    type='application/x-shockwave-flash'
    id='single2'
    name='single2'
    src='http://mowhayradio.co.uk/jwplayer/player.swf'
    width='350'
    height='197'
    bgcolor='undefined'
    allowscriptaccess='always'
    allowfullscreen='true'
    wmode='transparent'
    flashvars='file=http://www.youtube.com/watch?v=KYwtW1Z7rZc&image=http://mowhayradio.co.uk/Img/mowhay__site_vid_thumbnail.jpg&backcolor=000000&frontcolor=999999&screencolor=000000&volume=35&controlbar=over&autostart=true'
    /></embed></embed>     
    </object>
        </p>
        <p>You can listen live on Friday nights by going to the <a href="http://mowhayradio.co.uk/live" target="_blank">Listen LIVE</a> page.</p>
        <p>Please  </p>
        <p>If you want to keep up to date with exactly what's going on with The Mowhay Radio, you can follow our <a href="http://www.facebook.com/MowhayRadio" target="_blank">Facebook page</a>.</p>
      </div>
    </div>
    <!-- InstanceEndEditable -->
    <!-- END COL2-->
    <!-- InstanceBeginEditable name="Right sidebar" -->
    <div id="col3">
      <p> </p>
      <p>I love listening to this radio show. <br />
        &#9733;&#9733;&#9733;&#9733;&#9733; - Mitchell Wilson</p>
    </div>
    <!-- InstanceEndEditable -->
    <!-- END COL3-->
    </div>
    <!-- END CONTENT-->
    <div id="footer">
      <blockquote>
        <blockquote>
          <p>&copy; 2011 The Mowhay Radio  |  <a href="contact.html">Contact</a> | <a href="about.html">About &amp; Links</a> | <a href="live/" target="_blank">Listen LIVE</a> | <a href="song_requests.html">Song Requests</a> | <a href="takepart/">Take Part</a><a href="takepart/secret_sound.html"></a> | <a href="disclaimer.html">Disclaimer</a> | Design by <a href="mailto:[email protected]">Igor Jovic</a></p>
        </blockquote>
      </blockquote>
    </div> 
    <!-- END FOOTER -->
    </div> <!-- END WRAPPER-->
    <!-- Start of StatCounter Code -->
    <script type="text/javascript">
    var sc_project=6645564;
    var sc_invisible=1;
    var sc_security="da714bb8";
    </script>
    <script type="text/javascript"
    src="http://www.statcounter.com/counter/counter.js"></script><noscript><div
    class="statcounter"><a title="click tracking"
    href="http://statcounter.com/" target="_blank"><img
    class="statcounter"
    src="http://c.statcounter.com/6645564/0/da714bb8/1/"
    alt="click tracking" ></a></div></noscript>
    <!-- End of StatCounter Code -->
    </body>
    <!-- InstanceEnd --></html>
    Is there any way I can just create a new template to match the pages already created?
    Sorry if I sound silly but this is my first post on these forums and I'm not really sure what you need to know.
    Gabriel

    You can do everything, (and I mean absolutely EVERYTHING) in a regular HTML page that you can do in a DWT, and you don't have any of the parent/child/editable/non-editable/nested/nesting region problems that you will get with DWT's until you are very highly proficient at coding HTML and know exactly how to lay one out from the start so these things don't happen.
    DWT's are good for putting together a "mockup" to show a client, and have a good idea of the layout you will eventually use. They are also good for a teaching tool (the only time I ever created one was part of a class). If you have a group of people working on a site together, they are helpful too, but if none of the above apply, just make a plain HTML page and "Save As" when you need to make additional pages from it.

  • Trouble with updating child pages in dreamweaver cs4

    Hello,
    I have added some advertising links to my template page in Dreamweaver CS4 and it doesn't update my child pages for some reason.  I have saved the template and synchronized the sitewide as normal but it isn't updating them.  Any suggestions would be greatly appreciated.
    thx
    kim

    Yes it has worked in the past.
    Not if you made those changes to an editable region in the template it didn't.  Changes made to a template page ONLY propagate to child pages if they have been made to non-editable regions.  Changes to editable regions of a template page will ONLY appear in child pages created from the template after the changes have been made, and will not propagate to existing child pages.
    so does that mean if I add content to editable region I will have to manually put it on each page
    Yes it means exactly that.
    Can I change the editable region to a non editable region
    You can do that by removing the editable region from the template.  Of course when you do that, all unique content appearing in those regions on your child pages will also be removed.
    The moral to the story is to make sure that your template is designed properly (vis-a-vis editable regions) so that all of your needs are accommodated.

  • My master button made with a Blank Composition box displays under the content on the child pages

    I made my main menu buttons with a blank composition box. I have the button on the B-Master page so it displays the same at the top of every page. When I preview it and click open the buttons they seem to open a layer underneath the content on the child page. Is anyone familiar with this problem and have a solution?

    Hello,
    After much trial in error, I found that you must put your composition in the top layer, the header layer.  Perhaps Muse is doing to you what it was doing to me.  I created another master page within one of my files and when I was adding the composition box, it was going into the my "home" layer.  Grab your composition "meatball" and put it into your "header" layer and voila!  Problem solved.  Your composition contents will show on top of your page contents. Thanks for the question.  I've learnt with it as well!  And I hope this helps.

  • When menu bar is on a Master page, it is always on bottom layer on its child pages.

    How do you put items under it on its child pages? I don't want it getting covered over with added graphics. The workaround of pasting the menu bar on every page sucks.

    Wondering if anyone ever worked this out - I am having the identical problem and more, on the individual pages, my "controlled by master" is completely greyed out. My layout works well when I am working on the master.
    I am totally new to liquid layout, any tips welcome.

  • Child pages won't update

    I have a template "main.dwt.php" that has a spry menu, I updated a link on the spry menu to another page in the site, but the child page does not update.
    I'm having weird results with templates in DWCS3, don't know if it's worth it for a 20 page site. Sometimes it updates other pages and sometimes not.
    Now on the other hand, I updated some text on the main template on a side bar and after I saved the template DW did ask me if I wanted to update the other pages. 
    Any recomendations for this problem??
    Have a good holiday weekend!
    Kevin

    Is the Spry menu in an editable region?  A 20-page site is ideal for Templates.....
    Here are seven common mistakes that will result in changes not propagating from Template to child -
    1.  Rename the Templates folder
    2.  Move the Templates folder to some other folder level in the site other than root level
    3.  Move a template out of the Templates folder.
    4.  Make changes to an editable region of the template (which will not propagate)
    5.  Assume that template changes can be uploaded to the server without also uploading the changed local files
    6.  Corrupt the site cache so that the link between template and child page is broken
    7,  Improperly create your child pages by simply opening the template, adding page specific content, and resaving the template with an *.html extension rather that its *.dwt extension. (you can tell if this is the case by looking at the code on a child page - if you see anything like <!-- TemplateBeginEditable... then this is what you have done)
    The 6th problem can be repaired by using SITE | Advanced > Recreate Site Cache, and the six others can be fixed by just not doing them.  Have you done any of those?
    Or, read this -
    http://www.adobe.com/go/dd83ba8b

  • Updating child pages from a template in CS4

    I built a site that uses one template.  Everything was going along fine I'd make a change to the template and I was able to update all the child pages.  I made changes to the template yesterday and nothing updates.  I try using the update the site... I choose the files that use  and the one template I have and none of the pages update.  I've tries re-saving the template file as a template and still nothing updates.
    It has never immediately done an automatic update to the pages.  It always seems to be a while before the update these pages pallette comes up.  And again sometimes it will update all the pages, but most of the time not.
    I've done a search of the discussions to see if I could find a solution, before I posted this.  The ones I found do not have a solution that works for me.
    So does anyone know what to do?
    On a related issue... I usually create a page save the page to the site folder and then apply the template.  I have tried to create the page from the template, but the graphic in the background of the container div doesn't show up.  I usually have to then apply the template to the newly created page to get that to show up.  So what's up with this?
    Thank you!
    Nina

    On a related issue... I usually create a page save the page to the site folder and then apply the template.  I have tried to create the page from the template, but the graphic in the background of the container div doesn't show up.  I usually have to then apply the template to the newly created page to get that to show up.  So what's up with this?
    Try saving the page to the site after creating it, even though the graphic doesn't show up.  It should appear when you save it.
    Just for drill, here is my "Seven Common Mistakes" post - do any of these cover your situation?
    Here are seven common mistakes that will result in changes not propagating from Template to child -
    1.  Rename the Templates folder
    2.  Move the Templates folder to some other folder level in the site other than root level
    3.  Move a template out of the Templates folder.
    4.  Make changes to an editable region of the Template (which will not propagate)
    5.  Assume that Template changes will be effected by just uploading the changed Template file to the server without also uploading the changed local files
    6.  Corrupt the site cache so that the link between Template and child page is broken
    7.  Improperly create your child pages by simply opening the Template, adding page specific content, and resaving the Template with an *.html extension rather thanits *.dwt extension. (you can tell if this is the case by looking at the code on a child page - if you see anything like <!-- TemplateBeginEditable... then this is what you have done).  If you *have done this*, then recreate the child pages (in DW) using FILE | New > Page from Template, select the Template and click CREATE.
    The 6th problem can be repaired by using SITE | Advanced > Recreate Site Cache, and the six others can be fixed by just not doing them.  Have you done any of those?
    Or, read this -
    http://www.adobe.com/go/dd83ba8b

  • Instancebegin template populating twice in child pages

    I just made a change to my template for my site in Dreamweaver. I simply added the Google Analytics snippet to my head section, but now when it goes to update my child pages I get an error in line 1 stating "Unbalanced InstanceBegin tag" and the pages don't update. I looked at the code in one of my child pages and somehow instancebegin is now in twice. Here is a snippet of those first lines from a child page:
    <!-- InstanceBegin template="/Templates/Template.dwt" codeOutsideHTMLIsLocked="false" --><!DOCTYPE html>
    <!--[if IE 8]>                                          <html class="no-js lt-ie9" lang="en" > <![endif]-->
    <!--[if gt IE 8]><!--> <html class="no-js" lang="en" ><!-- InstanceBegin template="/Templates/Template.dwt" codeOutsideHTMLIsLocked="false" --> <!--<![endif]-->
    How can I eliminate one of those "<!-- InstanceBegin template="/Templates/Template.dwt" codeOutsideHTMLIsLocked="false" -->"? How did it get in there in the first place? Any help is appreciated!
    Update: On a side note, I tried opening a child page in textedit and deleting one of those snippets and it came back the next time I saved the template and pushed the change to the pages, so I am still looking for a way to fix this issue...

    Extra - I can see what's happening here, I think. The code is being expanded when it's copied to the child, so it's repeating the internal call to itself (randomImages is called from inside itself).  I got this code from a Dreamweaver tutorial, and it works perfectly well in a page that's not the child of a template.
    Can I prevent the code being expanded somehow? If not, can I edit the code that's copied from the template somewhere?
    Frances

  • Hyperlink and child page problems

    I have had no success in solving my muse problems.  I will restate the problem with more detail in the hope that some knows what I am doing wrong and can recommend solutions.
    The Hyperlink panel element is missing so that I cannot establish a hyperlink. This situation exists with two website I am working on, so I assume that it is a Muse setting which has to be set or re-set, in order to have the hyperlink option available.  I can turn the panel off/on by going to windows>control, but tuning the control back on, it still appears without the hyperlink.
    2. 
    In the plan mode, I created a page with two child pages attached.  The plan view shows the site layout the way it was planned.
    However when I choose Preview or Preview in Browser the children do not appear.  One recommendation I received from this forum was to turn on “show all Pages”, but I cannot find that switch.
    The inability to use these two features has brought me to a screeching halt. 
    The odd part is that the hyperlink worked fine until a couple of days ago, but when I went back  to continue work on the site, hyperlink was not there.
    The Child problem has never worked.

    Hi
    For the last question, the show all pages is located on the top right of the menu bar; (check on top left of the screen that you have indeed selected the menu bar) once menu bar is clicked, the blue circle with white arrow will appear, it is in there you will find MENU TYPE option, select ALL PAGES.
    NOTE when you selct menu bar, top left of the page has to confirm that you have selcted the menu!
    Hope this helps?
    Jilo

Maybe you are looking for

  • Window resizing and how to keep the window at that size.

    Having trouble with the applications window not staying the same size after I resize it. I know that dragging the corner will resize as well as the green button, but after I close it, it reverts back the small window and not to the resized window aft

  • External Sample Clock timeout

    Hi, I'm attempting to program up a Met One 010c cup anemometer which sends out 11V pulses whose frequency correlates to wind speed. I've written the following program Met One 010c-3b.vi which works when there's no sample clock and outputs data to the

  • Why does (disco.)iphone not sync bookmarks, mp3s, etc.. BUT it syncs mails?

    simple question i cant find in the user guide from apple; i must place my iphone in my dock which is connected via usb to my imac then i can sync it with mp3s and movies and so on... why does it receive mails (disconnected from dock) when i am online

  • Upgrade Solution Manager 7.1 add-on ST-ICO

    Hi everybody I'm upgrading from Solman 7.01 to 7.1. In the prepartion I'm stucked at the phase ADD-ON selection. The following stack is the target: SAP_BASIS 702 0009 SAPKB70209 SAP Basis Component SAP_ABA 702 0009 SAPKA70209 Cross-Application Compon

  • Arabic Character while loading in to Oracle.

    Hi All, OWB config is as follows: OWB : 9.2 Oracle 9i database. I am able to load Arabic characters from a source table to a target table using OWB mappings but when i try to load a flat file the characters get jumbled. My environment variables :-- I