Current link status within sidebar editable region library item

Hello,
I have looked all around and am still at a loss on how to address this issue. I would like the current page to be highlighted white when it is clicked on, although I am having no success. The user should see the "Into" link in white on this link: http://www2.biochem.wisc.edu/projectcrystal/la-Introduction-to-basic-chemistry.html
Thanks from a Dw beginner,
Dan
And, here is the code for this page:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Project CRYSTAL: Crystallographers Researching with Young Scientists: Teaching and Learning</title>
<script src="/projectcrystal/Scripts/swfobject_modified.js" type="text/javascript"></script>

<link href="/projectcrystal/style.css" rel="stylesheet" type="text/css">







<link href="print.css" rel="stylesheet" type="text/css" media="print" />
<link href="/projectcrystal/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<script src="/projectcrystal/Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="/projectcrystal/Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="/projectcrystal/Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="/projectcrystal/Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="/projectcrystal/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin .js" type="text/javascript"></script>
<script src="/projectcrystal/Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin .js" type="text/javascript"></script>
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
    these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
     These assume the following widget classes for menu layout (set in a preset)
    .MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
    .MenuBarVertical - vertical main bar; all submenus are pull-right.
    You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
    They only apply to horizontal menu bars:
        MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
        MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
        MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
        MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                        and centered in its parent container.
        MenuBarFullwidth - Grows to fill its parent container width.
    In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
    with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
    there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
    background-color:#cccccc;
    font-family: Arial, Helvetica, sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                MenuItem, and MenuItemLabel
                                                at a given level all use same definition for ems.
                                                Note that this means the size is also inherited to child submenus,
                                                so use caution in using relative sizes other than
                                                100% on submenu fonts. */
    font-weight: normal;
    font-size: 16px;
    font-style: normal;
    padding:0;
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
    width: 100%;
    float: left;
    color: #000;
    text-align: left;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
    display:none;
.MenuBarLeftShrink {
    float: left; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarRightShrink {
    float: right; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarFixedLeft {
    float: left;
    width: 80em;
.MenuBarFixedCentered {
    float: none;
    width: 80em;
    margin-left:auto;
    margin-right:auto;
.MenuBarFixedCentered br {
    clear:both;
    display:block;
.MenuBarFixedCentered .SubMenu br {
    display:none;
.MenuBarFullwidth {
    float: left;
    width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
    padding: 0px 0px 0px 0px;
    margin: 0;     /* Zero out margin on the item containers. The MenuItem is the active hover area.
                For most items, we have to do top or bottom padding or borders only on the MenuItem
                or a child so we keep the entire submenu tiled with items.
                Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
    background-color:#cccccc;
    padding-top: 0px;
    padding-right: 22px;
    padding-bottom: 0px;
    padding-left: 0px;
    border-top-width: 0px;
    border-right-width: 0px;
    border-bottom-width: 0px;
    border-left-width: 0px;
    border-top-style: none;
    border-right-style: none;
    border-bottom-style: none;
    border-left-style: none;
    color: #000;
#MenuBar .MenuItemFirst {
    border-style: none none none none;
#MenuBar .MenuItemLast {
    border-style: none solid none none;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:center;
    line-height:1.4em;
    color:#000;
    background-color:#cccccc;
    width: 10em;
    width:auto;
    padding-top: 6px;
    padding-right: 15px;
    padding-bottom: 6px;
    padding-left: 30px;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
    width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
    font-family: Arial, Helvetica, sans-serif;
    font-weight: normal;
    font-size: 14px;
    font-style: normal;
    background-color:#ffffff;
    padding:0px 2px 0px 0px;
    border-width:1px;
    border-color: #cccccc #cccccc #cccccc #cccccc;
    /* Border styles are overriden by first and last items */
    border-style: solid solid none solid;
    color: #000;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1em;
    background-color:#ffffff;
    color:#000;
    padding: 6px 12px 6px 5px;
    width: 7em;
    width:auto;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: #999;
    border-top-color: #999;
    border-right-color: #999;
    border-bottom-color: #999;
    border-left-color: #999;
    color: #FFF;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: #999999; /* consider exposing this prop separately*/
    color: #FFF;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: #999999;
    color: #FFF;
#MenuBar .SubMenu .MenuItemHover {
    background-color: #999;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: #999;
    color: #FFF;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: #ffffff;
    min-width:100%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
    top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
    left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                    and your personal taste.
                    0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
                    on MenuItemContainer and MenuItem on the parent
                    menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                    the dropdown with the left of the menu item label.*/
    z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
    top: 0px;
    left:100%;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
    background-color: #ffffff;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
    top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                vertically 'centered' on its invoking item */
    left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                to use px or ems to get the offset you want. */
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: #999999; /* consider exposing this prop separately*/
    color: #000000;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: #cccccc; /* consider exposing this prop separately*/
    color: #333333;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
    margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
a:active {
    color: #FFF;
    text-decoration: underline;
a:hover {
    color: #FFF;
    text-decoration: underline;
h4 {
    color: #3E8012;
    font-size: 35px;
    background-image: url(/projectcrystal/check-icon-for-h4-heading.png);
    background-repeat: no-repeat;
    background-position: left top;
    padding-left: 70px;
a:visited {
    color: #23998C;
    text-decoration: underline;
a:link {
    text-decoration: underline;
</style>
<script type="text/xml">

</script>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head>
<body>
<div id="wrapper">
<div id="header"><a href="/projectcrystal/index.html"><img src="/projectcrystal/Local Site Folder/Images/header_logo_nsf_final.jpg" width="83" height="95" alt="project CRYSTAL logo">
<h1>Project CRYSTAL</h1>
<h2>Crystallographers Researching with Young Scientists: Teaching And Learning</h2></a>
</div>

<ul id="MenuBar">
<li> <span class="MenuBar"><a href="/projectcrystal/index.html" class="MenuBar">HOME</a></span></li>
<li><a href="/projectcrystal/learn-along-with-young-scientists.html" class="MenuBar">LEARN ALONG WITH YOUNG SCIENTISTS</a>
    <ul>
      <li><a href="/projectcrystal/la-Introduction-to-basic-chemistry.html">Introduction into Basic Chemistry</a></li>
      <li><a href="/projectcrystal/la-the-structures-of-atoms.html">The Structures of Atoms</a></li>
      <li><a href="/projectcrystal/la-dna-part-one-properties-and-structures.html">DNA Part One: Properties and Structure</a></li>
      <li><a href="/projectcrystal/la-dna-part-two-replication.html">DNA Part Two: Replication</a></li>
      <li><a href="/projectcrystal/la-dna-part-three-transcription-translation-and-protein-structure.h tml">DNA Part Three: Transcription, Translation and Protein Structure</a></li>
    </ul>
</li>
<li><a href="/projectcrystal/modules.html" class="MenuBar">MODULES</a>
    <ul>
      <li><a href="/projectcrystal/m-cos-home.html">The Chemistry of Sugars</a>
        <ul>
          <li><a href="/projectcrystal/m-cos-atomsandmatter.html" class="MenuBar">Atoms and Matter</a></li>
          <li><a href="/projectcrystal/m-cos-theperiodictable.html" class="MenuBar">The Periodic Table</a></li>
          <li><a href="/projectcrystal/m-cos-bonding.html" class="MenuBar">Bonding</a></li>
          <li><a href="/projectcrystal/m-cos-importanceofsugars.html" class="MenuBar">Importance of Sugars</a></li>
          <li><a href="/projectcrystal/m-cos-foodandnutrition.html" class="MenuBar">Food and Nutrition</a></li>
          <li><a href="/projectcrystal/m-cos-unusualsugars.html" class="MenuBar">Unusual Sugars</a></li>
          <li><a href="/projectcrystal/m-cos-modeling.html" class="MenuBar">Modeling</a></li>
          </ul>
        </li>
      <li><a href="/projectcrystal/m-cof-home.html">The Chemistry of Fats</a>
        <ul>
          <li><a href="/projectcrystal/m-cof-atomsandmatter.html" class="MenuBar">Atoms and Matter</a></li>
          <li><a href="/projectcrystal/m-cof-theperiodictable.html"class="MenuBar">The Periodic Table</a></li>
          <li><a href="/projectcrystal/m-cof-bonding.html" class="MenuBar">Bonding</a></li>
          <li><a href="/projectcrystal/m-cof-typesof_fats.html" class="MenuBar">Types of Fats</a></li>
          <li><a href="/projectcrystal/m-cof-steroids.html" class="MenuBar">Steroids</a></li>
          <li><a href="/projectcrystal/m-cof-cholesterol.html" class="MenuBar">Cholesterol</a></li>
          <li><a href="/projectcrystal/m-cof-importanceof_fats.html" class="MenuBar">Importance of Fats</a></li>
          <li><a href="/projectcrystal/m-cof-thecellmembrane.html" class="MenuBar">The Cell Membrane</a></li>
          </ul>
        </li>
      <li><a href="/projectcrystal/m-cop-home.html">The Chemistry of Proteins</a>
        <ul>
          <li><a href="/projectcrystal/m-cop-atomsandmatter.html"class="MenuBar">Atoms and Matter</a></li>
          <li><a href="/projectcrystal/m-cop-theperiodictable.html" class="MenuBar">The Periodic Table</a></li>
          <li><a href="/projectcrystal/m-cop-bonding.html"class="MenuBar">Bonding</a></li>
          </ul>
        </li>
      </ul>
</li>
<li><a href="/projectcrystal/holdenlab-home.html" class="MenuBar">HOLDEN LAB</a>
    <ul>
      <li><a href="/projectcrystal/hl-newsworthy.html">Newsworthy</a></li>
      <li><a href="/projectcrystal/hl-xraycrystallography.html">X-ray Crystallography</a></li>
      <li><a href="/projectcrystal/hl-sugarchemistry.html">Sugar Chemistry</a></li>
      <li><a href="/projectcrystal/hl-labmembers.html">Lab Members</a>
        <ul>
          <li><a href="/projectcrystal/hl-lm-graduatestudents.html">Graduate Students</a></li>
          <li><a href="/projectcrystal/hl-lm-highschoolinterns.html">High School Interns</a></li>
          <li><a href="/projectcrystal/hl-lm-projectcrystal.html">Project CRYSTAL</a></li>
        </ul>
      </li>
    </ul>
</li>
<li><a href="/projectcrystal/contactus.html" class="MenuBar">CONTACT</a></li>
</ul>
<ul>
<ul>
    <ul>
      <ul>
        </ul>
      </ul>
    </ul>
</ul>
<script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
      widgetClass: "MenuBar MenuBarLeftShrink",
      insertMenuBarBreak: true,
      mainMenuShowDelay: 100,
      mainMenuHideDelay: 200,
      subMenuShowDelay: 200,
      subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
</script>
<div id="sidebar">
    <div class="top"></div>
    <div class="content"> 
<style type="text/css">
a:link {
    color: #23998C;
a:visited {
    color: #23998C;
a:hover {
    color: #FFF;
</style>
<h1>Learn Along Lessons</h1>
    <p><a href="/projectcrystal/la-Introduction-to-basic-chemistry.html">Introduction to Basic Chemistry</a></p>
    <p><a href="/projectcrystal/la-the-structures-of-atoms.html">The Structures of Atoms</a></p>
    <p><a href="/projectcrystal/la-dna-part-one-properties-and-structures.html">DNA Part One: Properties and Structures</a></p>
<p><a href="/projectcrystal/la-dna-part-two-replication.html">DNA Part Two: Replication</a></p>
<p><a href="/projectcrystal/la-dna-part-three-transcription-translation-and-protein-structure.h tml">DNA Part Three: Transcription, Translation and Protein Structure</a></p>
</div>
    <div class="bottom"></div>
</div>
<div id="main">
    <div class="top"></div>
    <div class="content">
    
    <h1>Learn Along</h1>
    <h2>Introduction to Basic Chemistry</h2>
    <p>
      <object id="FlashID" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="700" height="500">
        <param name="movie" value="/projectcrystal/LA_Introduction_to_Basic_Chemistry.swf" />
        <param name="quality" value="high" />
        <param name="wmode" value="opaque" />
        <param name="swfversion" value="6.0.65.0" />
        
        <param name="expressinstall" value="/projectcrystal/Scripts/expressInstall.swf" />
        
        
        <object type="application/x-shockwave-flash" data="/projectcrystal/LA_Introduction_to_Basic_Chemistry.swf" width="700" height="500">
          
          <param name="quality" value="high" />
          <param name="wmode" value="opaque" />
          <param name="swfversion" value="6.0.65.0" />
          <param name="expressinstall" value="/projectcrystal/Scripts/expressInstall.swf" />
          
          <div>
            <h4>Content on this page requires a newer version of Adobe Flash Player.</h4>
            <p><a href="http://www.adobe.com/go/getflashplayer"><img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif" alt="Get Adobe Flash player" width="112" height="33" /></a></p>
          </div>
          
        </object>
        
      </object>
    </p>
    </div>
    <div class="bottom"></div>
</div><div id="pulldown"></div>
</div>
<div id="footer">
<p>Copyright © 2011 The Board of Regents of the University of Wisconsin System<br>
    Last updated:
    July 26, 2011
    <script type="text/javascript">
swfobject.registerObject("FlashID");
    </script>
    <br>
    Feedback, questions, or accessibility issues: [email protected]<br>
</p>
</div>

</body>

I would like the current page to be highlighted white when it is clicked on,
Here's one method
http://alt-web.com/Articles/Persistent-Page-Indicator.shtml

Similar Messages

HOW TO LINK PAGE IN TEMPLATE EDITABLE REGION

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

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

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

I cannot select or edit content within template editable region in DW CS5

The only way I can edit the content is in code view. A real pain. Anyone else have this happening? I have re-checked and re-applied template to page in question and doesn't help. I cannot directly select an image or text in design view. I get the "no can do" icon that appears over template items that are locked. I have strolled through the preferences and don't see anything regarding this. Since upgrading from CS3 to Dreamweaver CS5 mac, I have had nothing but problems. This app is half baked at best.

Wasn't a problem in prior versions of DW.
Would have been in CS4, but not in earlier ones. In those versions, the use of overflow:hidden as a way of setting a new block formatting context to clear internal floats was not supported even though it was a perfectly valid method. You may find that you need to return the overflow:hidden to your styles to properly manage floats within that container. In that case, a double click is all that's needed to temporarily display the entire content of the element.

Dreamweaver Teamplate with Library Item for Navigation/Sidebar not updating editable classes

I have a Dreamweaver Template that contains two Library items. One Library item is my navigation bar, the other is a sidebar that shows different content depending on what page you are on. I'm assigning an editable class "active" to the navigation bar to show you are on a particular page, and also assigning the editable class "active" to the sidebar to reveal a portion of the sidebar with links pertaining to that specific page. The default value for the class is "hidden". So what is happening is when I open a page I have created and "edit" the Library Items in it to edit these classes, it resets resets all the other pages on the site to the default class values. How am I able to use editable classes and Library Items to achieve this kind of functionality? The idea is to only have ONE navigaton bar to update on the site and to only have ONE sidebar item to update. Here is an example of the sidebar and navigation in action so you can see what I'm going for. Notice the green button in the navigation bar (that is a list item with the class "active" which is an editable class in the Library Item, also notice the tan links in the sidebar, that is an unordered list that has an editable class of "active" in the Library Items --- these editable classes reset to their defaults when updating the Library Item on the website).
http://www.brumleve.org/joe/temp/CAP/mission.html

In my understanding, whenever you edit the contents of a library item, it will update all other occurances of this library item on the rest of the site. That's "working as designed" as far as I know, unless you break the link by telling it to not update - which kinda defeats the purpose I think.
But theres another way to do this using template properties, i#ve been using this approach myself a couple of times:
Write your navigation bar in the template (.dwt) file itself, then select the class= of your first menu item and choose .. (names might be off, I am using a non-English copy of DW): "modify > template > make attribute editable" from the main menu. Do so for all your menu items and name these new template properties something like "item_x_class"
You'll end up with something like this in your template source:
<div class="@@(item_1_class)@@">
and a matching
 in the header
Now, on each page, you can set the class within the template properties dialog ("modify > template properties"). If your main menu changes, it won't overwrite your template properties, but still update all pages when you do make a change to the menu.
If you're using multiple templates for your site, consider nesting templates, so the master template already includes your navbar and all subsequent templates will "inherit" changes to the navbar code (sans the editable class property).
Hope this helps.. or at least gives you an idea for further experiments..
Stephan

Spry Validation within Editable Region of Template

Hello all,
Spry Validation Field is not working on this page where the
code is within an editable region of a template based page:
http://www.nprducati.com/newsite/service.html
The same exact code works on a "normal" HTML page.
Anyone else encounter this or has any ideas why it's failing?
Rich

Spry validation would not be affected by being located within
a template
editable region, since editable regions are only indicated by
the use of
HTML comment tags, i.e., meaningless to a browser.
Most likely the problem is the link here -
<script src="SpryAssets/SpryValidationTextField.js"
type="text/javascript"></script>
It appears that you have not made the link properly in the
Template file,
since the corresponding link for the menu is this -
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1",
{imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
You might also want to take care of these errors -
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.nprducati.com%2Fnewsite%2Fser vice.html
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
==================
"Multistrada1100" <[email protected]> wrote
in message
news:flegqo$h60$[email protected]..
> Hello all,
>
> Spry Validation Field is not working on this page where
the code is within
> an
> editable region of a template based page:
>
>
http://www.nprducati.com/newsite/service.html
>
> The same exact code works on a "normal" HTML page.
>
> Anyone else encounter this or has any ideas why it's
failing?
>
> Rich
>

Editable Regions Problem in CS3

I am working a set of pages based on the two column fixed with template.
4 Editable Regions.
Two Created by Dreamweaver
Two Created by me
Doc Title
Head
MainContent
Ad Area
Almost ALL of my additions are going into the Content Region. 80% of the time I have NO ISSUES
between Code View and Design View.
What is happing to me too many times now that it has become annoying......
I will make a simple code change in Code View, usually WELL WITHIN the editable region tags
and when I go to view what I did in Design View, I get an error box that says something like this.
You have made a code change in an area that is designated as uneditable.
If you wish to keep this change it will be lost the next time you update the template.
This could be a siple change like adding a bold to a piece of text.
A lot of times it happens whe I try to put a Container Div around some text.
It almost ALWAYS happens when I am trying to float something.
Is this a BUG. Is there a fix? I know I can't ignore it because I have seen what happens when I do that....
Please don't tell me to update to a more recent version unless that absolutely has the fix in it.
It cost me an arm to buy this product in the first place and if I had known how little I was gaining
I would have NEVER purchased it.I certainly don't want to spend any more unless it solves the issue.
The design view in CS3 STINKS! Design View was one of the reasons
I wanted the product in the first place. WYSIWYG. I was trying to upgrade away from years of using HotDog.
Two years of this now and I still find myself doing most of my design in Code View.
I don't TRUST Design View.
I do eventually publish to a copy without template marup but I need to code in the version that is still templated.
I do change the master template from time to time.
HELP!

Better than your helpless nagging would be that you share a link to your page.
... and your: Please don't tell me to update to a more recent version unless that absolutely has the fix in it. It's actually also not a very good attitude and (for me!) not a great motivation to help you. Ok, I have this program on the computer, even, but the reasons are to work here in the forum.
... and I quote from a thread here in the forum:
"It's not a word processor or WYSIWYG, never has been, but I think you're using those terms more broadly than the regulars in this forum use them. But if you're happy to use only Design View and let DW code then you'll get similar results to using DW8."

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

<title>Untitled Document</title>

<style type="text/css">

</style>
<script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />


</head>
<body>
     <div id="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 "header" div (the dark grey one), which is positioned "relative."</p>
      </div>
     </div>
     <div id="content">
       
       
       <h1>This text (really an h1) is appearing within the div with id of "content"</h1>
       </div>
     
<script type="text/javascript">

    </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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Untitled Document</title>

<style type="text/css">

</style>
<script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />


</head>
<body>
     <div id="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 "header" div (the dark grey one), which is positioned "relative."</p>
      </div>
     </div>
     <div id="content">
       
       
       <h1>This text (really an h1) is appearing within the div with id of "content"</h1>
       </div>
     
<script type="text/javascript">

    </script>
</body>
</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

After Edit Library Item- "Premature end of JPEG file"

Hello, I'm using Windows 7 Home Premium 64-bit. In DW CS5 after editing a Library item and saving, DW asks if it should update pages containing the item. I tell it to go ahead, and after some processing I get an error box titled "JPEG Library Error." The message is "Premature end of JPEG file." Nothing else except "OK"! I can't imagine what this is referring to or if the error is causing the pages to not be updated with the edited lbi. I don't have any JPEG images i nthe Library item. Here's a link to the Libraty item:
http://www.techno-archive.com/Library/bottom_menu.lbi
After I dismiss the error in DW the Update Pages dialog sits there with the Done button grayed out. The bottom few lines of the log look like this:
updated gallery_rec\trees\firetree\firetree-sky2.html
    item Library\bottom_menu.lbi
updated gallery_rec\trees\firetree\firetree-tree1.html
    item Library\bottom_menu.lbi
updated gallery_rec\trees\firetree\firetree-tree2.html
    item Library\bottom_menu.lbi
updated gallery_rec\trees\firetree\firetree-tree3.html
    item Library\bottom_menu.lbi
updated gallery_rec\trees\firetree\firetree.html
    item Library\bottom_menu.lbi
Done.
files examined: 641
files updated: 641
files which could not be updated: 0
total time: (0:00:19)
Updating F:\techno-archive\
Done.
files examined: 15697
files updated: 0
files which could not be updated: 0
total time: (0:00:57)
It doesn't tell which pages got updated and which didn't or why those that didn't did not get updated.
Any ideas anybody?
Thanks, - Dave

Update- Solved!
An answer to this thread dated April 30, 2009 of the same subject by David_Powers, community Professional, did the trick. I wound up renaming the DW Configuration folder in C:\Users\dmckeen\AppData\Roaming\Adobe\Dreamweaver CS5\en_US\Configuration (where dmckeen is my username) and letting DW rebuild it.
Thanx

Can users edit Library items?

Hi everyone. I'm almost done with my first Contribute site
and I had a question. My client has a small piece of text that is
shown in the header of every page and this text is something that
they want to change regularly. I added a Library item for this
chunk in Dreamweaver thinking that this would be the proper way to
allow them to edit it in one place in Contribute.
I found where I can grant permissions for editing the various
types of shared assets, but I don't see that they can edit the
Library item. Is there a way to do this or do I need to set this up
differently (server-side include, etc.)?
Thanks in advance,
Jason

I think you should use a SSI in your Template and provide
your user with a link to that include-file, so they can edit it in
Contribute.
gtrz.
Hayo

How do I edit Library Items in Contribute?

I've been attempting to edit a Library Item in Contribute CS5 with no real luck. First in said it could not open the file so I designated "simpleText" and also MSWord as alternate programs to edit the Library with. (I need something that my client has access to on a PC in their office). Contribute allowed me to open, edit and even publish...giving me a notice of "success" but when accessing the actual page online, the changes were not updated.
Adobe Tech support was useless on this issues.
Here is the code for the Library Item:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">
.newsHeader {
    font-family: Arial, Helvetica, sans-serif;
    font-size: 18px;
    line-height: 18px;
    font-weight: bold;
    color: #6693b3;
    margin: 0px;
    padding: 20px 0px 0px;
.newsbodycopy {    font-family: Arial, Helvetica, sans-serif;
    font-size: 12px;
    line-height: 18px;
    color: #666;
    margin-top: 4px;
    margin-bottom: 5px;
</style>
<p class="newsHeader">News header</p>
<p class="newsbodycopy">Update Content on this page.</p>
Any help or suggestions to try would be appreciated. I created the item in Dreamweaver. Code is directly from Dreamweaver. I'm not a coder.
Thanks!

1. In the main menu go to >File>Actions>Edit page source in external application (Dreamweaver)
2. In the Dreamweaver make the necessary modifications.
3. Save the file
4. Return to Contribute and publish the page

DW removes spaces surrounding updated library items

I've filed a bug with Adobe on this issue, but I'm wondering
if anyone else has received a fix for what I consider a
showstopping bug. In a nutshell, whenever I update a library item,
DW removes all spaces surrounding the updated library item, and
will even remove spaces surrounding unrelated library items during
the same operation.
For example, let's say I have a simple library item that
contains only the character "^". I insert that into a page to
render like this: "| ^ |", using normal spaces in the page code to
separate the three characters. If I then edit the library item to
use the character "-" instead, all updated pages will lose the
surrounding spaces: "|-|".
I've developed hundreds of library items over the years, and
can reproduce this over the last three versions of DW (8, MX 2004,
MX), on multiple computers using new code or existing sites. If I
edit a single library item, it corrupts hundreds of pages in a
large site, and I have to use special searches to find and fix the
error. I can't believe that noone else is affected by this problem,
or isn't using library items to the extent that I do.
I'd really like to see library item functionality repaired,
and this is my last appeal before finding a replacement for DW, Are
any DW developers monitoring this list?

> bug is just as capable of affecting SSI
I don't think so. At least, I have never seen it happen. Have
you?
> Library items are particularly aimed at professionals
managing large
> sites.
I don't think so here, either. Why would one EVER choose a
Library item
over SSI? On a large site, you would upload hundreds if not
thousands of
files for each change with the former.
> It is an opportunity to
> create reusable code that can be managed and edited in
one central
> location, so
> that changes to a single file can be replicated
throughout the entire code
> base.
Precisely what SSI does, only better.
> Yes, it may be more desirable to use a server side
technology to control
> these bits through the use of variables and includes,
but I also build and
> manage high performance web servers, and no dynamic
language can even come
> close to the speed of delivering static files,
especially if you want to
> withstand a slashdotting or other unusual burst of
activity.
This is true - since Library items are design-time tools, you
take the
bandwidth hit on the upload side of things rather than on the
fetch side of
things.
> I'm hoping that someone at Adobe is monitoring this list
They do not. If you need to communicate with them, you must
contact them
directly. But you have been told that Adobe is aware of the
problem at
least twice - is that not enough?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"jorey" <[email protected]> wrote in message
news:[email protected]...
> The examples I used are overly simplified to more
clearly demonstrate the
> problem. Using a server-side technology is not relevant
to this issue.
> This
> bug is just as capable of affecting SSI, PHP, ASP, or
any other code
> edited and
> managed with Dreamweaver.
>
> Library items are particularly aimed at professionals
managing large
> sites.
> Who else would even be interested in such a feature? It
is an opportunity
> to
> create reusable code that can be managed and edited in
one central
> location, so
> that changes to a single file can be replicated
throughout the entire code
> base. To suggest that it is necessary to create slightly
different
> versions of
> code snippets to suit the individual needs of each
generated page utterly
> defeats the purpose of library items.
>
> As for the uses of library items, sure, I'll use it to
maintain large
> blocks
> of code, but it's also useful for little things that
change on a regular
> basis,
> such as names of people in specific roles, addresses,
phone numbers, email
> addresses, URLs, dates and other things that might
appear hundreds of
> times
> throughout a site in a variety of contexts. This bug has
serious
> repercussions,
> because it is not limited to the item being updated. You
could update a
> large
> block of code and have unpredictable changes occur
elsewhere. This is
> unacceptable, and may not be limited to library items,
but may also affect
> templates or any other site management function that
relies on the same
> routines.
>
> Yes, it may be more desirable to use a server side
technology to control
> these bits through the use of variables and includes,
but I also build and
> manage high performance web servers, and no dynamic
language can even come
> close to the speed of delivering static files,
especially if you want to
> withstand a slashdotting or other unusual burst of
activity.
>
> But as I mentioned, the type of code or use of the
library item is
> irrelevant.
> Dreamweaver as a programming editor has a serious bug.
It's broken, and
> needs
> to be fixed. I'm hoping that someone at Adobe is
monitoring this list and
> will
> understand that this is a problem that affects advanced
users and whole
> teams
> who have made extensive and productive use of this
feature before it was
> broken.
>

Change Linked to Document with Edit Menu Column in Forms Library

Hi!
I am using a Forms Library, which I have associated with a Infopath Form, and there is that column "Name" which is linked Edit Menu... I do not want to use this column "Name" which is basically a FileName, so if I hide this "Name" column, how can I use an other column like ID (for eg) to link to document with edit menu...
I'll appreciate any advice on this... Thanks in Advance

Steve - Open the page in SP designer and in design mode hover over an item in the column a little '>' should show, click it and you can choose the options, however in SP2013 the design mode is gone so here is how it looks in the code of the page for adding
a menu to the 'ActiveSite' column, note you need to do this in every location the column is used, which may make this not workable?
<ViewFields>
<FieldRef
Name="Attachments"/>
<FieldRef
Name="LinkTitle"/>
<FieldRef
Name="SiteURL"
/>
<FieldRef
Name="ActiveSite"LinkToItem="TRUE"
ListItemMenu="TRUE"/>
</ViewFields>
http://sharepointsurfer.wordpress.com/.

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

</style>
<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>
    
</div>

       <br class="clearfloat" />
</p>
<div id="footer">
    <hr width="100%" size="8" noshade="noshade" color="#006666" id="color="069"" colour="#069"/>
    <p><strong>Maintainted by: ASQM </strong></p>
    <p><strong>Date Modified: 2013-03-25</strong></p>
    
</div>
<script type="text/javascript">

</script>
</h3>
    
</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.

How to remove Editable region from nested template?

I'm trying to remove an editable region from a nested
template while retaining it in the parent template. DW doesn't want
to let me do this.
Example:
- I've created an overall template call ALLPAGES.DWT
- In it, there's an editable region called "related links".
- The "related links" will stay the same for all my main
pages (welcome, news, info, etc), so I'd like to create a nested
template called MAINPAGES.DWT where the field is locked.
So here's what I did; I started a new page from ALLPAGES.DWT
and then I created a template MAINPAGES.DWT from it. Now I want to
remove the editable region "related links". According to the DW
manual, I should be able to highlight the region and go to
Modify > Templates > Remove Template Markup, but that
option is greyed out!
Apparenlty the only way of removing the editable region is to
create a smaller editable region within it. But that's unnecessary
and sloppy. How can I remove the region entirely?

> This use of nested templates is very useful and very
simple and
> straightforward.
> It involves no additional overheads, and introduces no
reliability
> problems.
I really disagree with this.
> I cannot understand why Murray has such a bad attitude
to nested
> templates.
I spent quite a bit of time using them, tweaking them,
understanding them,
and watching the problems that others have had here on the
forum. My
compelling conclusion is that there is nothing you can do
with nested
templates that you cannot do more simply and with far less
trouble by using
other methods, some involving other kinds of template
regions, and some
involving simple use of Library items, or better, server-side
includes.
> I can only assume either that he had a bad experience on
the road to
> Damascus,
> after writing his definitive book on templates
I assure you, it's based on much more study and experience
than you have put
into it.
> "Templates are wicked and sinful! Don't play with them,
or you will go
> blind!"
This is not only unkind, it's completely erroneous. Far and
away, I am the
single most enthusiastic proponent for the use of templates
on these boards.
Perhaps a read of my book would help you rid yourself of your
attitude, too.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Clancy" <[email protected]> wrote in message
news:[email protected]...
> "Dodgeit" <[email protected]> wrote:
>
>>I'm trying to remove an editable region from a nested
template while
>>retaining
>>it in the parent template. DW doesn't want to let me
do this.
>>
>> Example:
>> - I've created an overall template call ALLPAGES.DWT
>> - In it, there's an editable region called "related
links".
>> - The "related links" will stay the same for all my
main pages (welcome,
>> news,
>>info, etc), so I'd like to create a nested template
called MAINPAGES.DWT
>>where
>>the field is locked.
>
> Very simple:
>
> Open allpages.dwt.
> Save as template, with name mainpages.dwt (I always do
this immediately so
> that
> if I do something stupid I don't corrupt the original
template).
> Insert the desired content into "related links".
> At the beginning of the content area of "related links"
insert the magic
> code
> @@("")@@
> This turns off the editable region, and there will be no
reference to it
> in
> pages derived from this template.
> Save the changes to mainpages.dwt
> Done!
>
> Have a look at
>
>
http://www.corybas.com/Technical/Nested.htm
> This is derived from my template techpage.dwt, which in
turn is ultimately
> derived from my template basicpage.dwt.
>
> Basicpage.dwt defines two editable regions 'title' and
'subtitle' at the
> top of
> the page. Techpage.dwt sets a fixed title for all my
technical pages, as
> follows:
>
> <p class="hdgtn" >@@("")@@Roger
> Riordan: Technical notes</p>
> <p class="hdgstn">Notes</p>
>
> In the page Nested.htm the references to 'title'
disappear, and the two
> lines
> appear as
>
> <p class="hdgtn" >Roger Riordan: Technical
notes</p>
> <p class="hdgstn">Nested
> Templates</p>
>
> This use of nested templates is very useful and very
simple and
> straightforward.
> It involves no additional overheads, and introduces no
reliability
> problems.
>
> I cannot understand why Murray has such a bad attitude
to nested
> templates. I
> can only assume either that he had a bad experience on
the road to
> Damascus,
> after writing his definitive book on templates, or that
it says simply:
>
> "Templates are wicked and sinful! Don't play with them,
or you will go
> blind!"
>
>
> Clancy

Current link status within sidebar editable region library item

Similar Messages

Maybe you are looking for