Nested Templates / div

Similar Questions

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

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

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

  For example:

  __________________

  Model Master:

  <!-TemplateBeginEditable name = "ChildTemplateCSSLinks"->

  Model child CSS links here.

  <! - TemplateEndEditable - >

  _____

  Child model:

  <!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->

  Model child CSS links here.

  <!-TemplateBeginEditable name = "ChildPageCSSLinks"->

  Child CSS PAGE links here.

  <! - TemplateEndEditable - >

  <! - InstanceEndEditable - >

  _____

  The child page:

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

  <!-InstanceBeginEditable name = "ChildPageCSSLinks"->

  Child CSS PAGE links here. (Accurately appearing editable)

  <! - InstanceEndEditable - >

  __________________

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

  Now for an example of what does not work:

  __________________

  Model Master:

  <!-TemplateBeginEditable name = "ChildTemplateCSSLinks"->

  Model child CSS links here.

  <! - TemplateEndEditable - >

  _____

  Child model:

  <!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->

  Model child CSS links here.

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

  <! - InstanceEndEditable - >

  _____

  The child page:

  <!-InstanceBeginEditable name = "ChildTemplateCSSLinks"->

  Model child CSS links here.

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

  <! - InstanceEndEditable - >

  __________________

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

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

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

  Thank you. Sincerely,

  ~ Miss Cat

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

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

  Sincerely,

  Miss Cat

  [info promo signature removed by Moderator]

• Problem to the &lt; title &gt; tag editable inside a nested template

  Thank you very much in advance for the help with my problem below.

  -I'm going to build a website using Dreamweaver CS4.

  -J' have a model of main site including some code html pages are correctly built out of.

  -J' also have a nested blog model built on the main model for the blog site section and built 5 HTML pages out of this blog template nested start with.

  -With the site ready to launch, I try to go into each HTML page and update my tages < title > and then my < metatags description >. I put the < title > tags in the HTML pages out of my main template.

  -My problem is with the < title > tags in the HTML pages, built on the model of the blog nested. I can only change the < title > tag in the template real blog nested itself, and not the nested HTML built out of this blog template pages.

  -To try to solve the problem, I tried to move the tags surrounding area editable "doctitle" to different positions within the < head > tag on the main model and nested model of the blog. This includes surrounding the editable attribute code and also put an editable region around the entire < head > tag. But all produce errors when Dreamweaver tries to update the pages based on the given model.

  -The head of <>tag code to the main model of nested blog and an HTML page out of the nested model blog is below. I hope someone can help?

  # TEMPLATE < HEAD > HAND TAG #.

  < head >
  < meta http-equiv = "Content-Type" content = text/html"; charset = utf-8 "/ >"
  <!-TemplateBeginEditable name = "doctitle"-->
  mainTemplate < title > < /title >
  <! - TemplateEndEditable - >
  "" < link href = "... / css/main.css ' rel ="stylesheet"type =" text/css"/ >
  "" < link href = "... / pictures/faviconIcon.ico" rel = "shortcut icon" / >
  <!-TemplateParam name = "indexClass" type = "text" value = "holder"->
  <!-TemplateParam name = "domesticClass" type = "text" value = "holder"->
  <!-TemplateParam name = "commercialClass" type = "text" value = "holder"->
  <!-TemplateParam name = "blogClass" type = "text" value = "holder"->
  <!-TemplateParam name = "contactClass" type = "text" value = "holder"->
  <!-TemplateParam name = "bodyClass" type = "text" value = "main"->
  < / head >

  # TEMPLATE BLOG < HEAD > TAG #.

  < head >
  < meta http-equiv = "Content-Type" content = text/html"; charset = utf-8 "/ >"
  <!-InstanceBeginEditable name = "doctitle"-->
  < title > < /title > 1111
  <!-TemplateParam name = "blogClass4" type = "text" value = "holder"->
  <!-TemplateParam name = "blogClass3" type = "text" value = "holder"->
  <!-TemplateParam name = "blogClass2" type = "text" value = "holder"->
  <!-TemplateParam name = "blogClass1" type = "text" value = "holder"->
  <!-TemplateParam name = "blogClass5" type = "text" value = "holder"->
  <! - InstanceEndEditable - >
  "" < link href = "... / css/main.css ' rel ="stylesheet"type =" text/css"/ >
  "" < link href = "... / pictures/faviconIcon.ico" rel = "shortcut icon" / >
  <!-InstanceParam name = "indexClass" type = "text" value = "holder"->
  <!-InstanceParam name = "domesticClass" type = "text" value = "holder"->
  <!-InstanceParam name = "commercialClass" type = "text" value = "holder"->
  <!-InstanceParam name = "blogClass" type = "text" value = "current"->
  <!-InstanceParam name = "contactClass" type = "text" value = "holder"->
  <!-InstanceParam name = "bodyClass" type = "text" value = "blog"->
  < / head >

  # HTML < HEAD > TAG PAGE BLOG #.

  < head >
  < meta http-equiv = "Content-Type" content = text/html"; charset = utf-8 "/ >"
  < title > < /title > 1111
  <!-InstanceParam name = "blogClass4" type = "text" value = "holder"->
  <!-InstanceParam name = "blogClass3" type = "text" value = "holder"->
  <!-InstanceParam name = "blogClass2" type = "text" value = "current"->
  <!-InstanceParam name = "blogClass1" type = "text" value = "holder"->
  <!-InstanceParam name = "blogClass5" type = "text" value = "holder"->
  "" < link href = "... / css/main.css ' rel ="stylesheet"type =" text/css"/ >
  "" < link href = "... / pictures/faviconIcon.ico" rel = "shortcut icon" / >
  < / head >

  First of all, there are ways to achieve what you want without using nested templates.  A bit of CSS and server-side includes will do the job admirably.

  Next - you will be surely able to insert an editable region in the
  

  on this subject.

  
  
  
  
  

  If you want to use nested templates, you will need to learn how to think like one.  It is not easy.  And it will take you to put your hand in the code sometimes.  This is only one of the reasons why I think that using them is a mistake.

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

  I have a basic model for the website (creation of main menus) and a secondary model using this basic model, which establishes a common table, on the one hand of the site layout. After you create the PHP to drive page, I need to lock this secondary nested region - otherwise any edit I make on my secondary & quot; -definition of table & quot; model is not passed to the last pages using the secondary model. I created a secondary edit box successfully in every part of the & lt; body & gt; region, and of course, it locks text outside the secondary editable help DW says it should. So far so good.
  
  Now the problem - I can not create a region inside the & lt; head & gt; combo box to lock this region too. Normally we'd like keywords and so on to be variable from one page to another, but as I am filling variable keywords from a database, it makes sense to lock the & lt; head & gt; Too much. Does anyone know why that generates an error & quot; failed to create an optional region here & quot;? Is there anything we can do about it?

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

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

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

  Prevent an editable region to a nested model

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

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

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

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

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

  Best regards
  Richard

• clientListener 'click' guy went in nested templates

  I have the following situation (JDev 11.1.1.3):
  
  -an ADF library with template has javascript and some pages based on A template
  -a project using the library with its own model based on the model A B and more javascript, and some pages based on model B
  
  Model has an outputText with a clientlistener, the code is as follows:
  

                      <af:outputText id="medbtn1" value="X" styleClass="mededelingenbutton"
                       visible="#{portalBean.showMededelingen}" >
                         <af:clientListener method="hideMededelingen" type="click"/>
                         <af:serverListener type="jsServerListener"
                                             method="#{portalBean.hideMededelingen}"/>
  </af:outputText>

  the javascript so that it looks like this:
  

  function hideMededelingen(evt) {
      document.getElementById('pt1:pt_pbl1').style.display = 'none'; 
      AdfCustomEvent.queue(evt.getSource(), "jsServerListener",     {    },true);
      evt.cancel();
  }

  This only works in pages based on the model A, but I want also that it works in pages based on the template (B) I noticed that the id of the item that I hide evolves according to the model used, that's fine.
  I can change the code to do this:
  

  function hideMededelingen(evt) {
      document.getElementById('pt1:pt_pbl1').style.display = 'none'; // main_template
      document.getElementById('pt1:mpt1:pt_pbl1').style.display = 'none'; // reinigingsrecht_template
      
      AdfCustomEvent.queue(evt.getSource(), "jsServerListener", { },true);
      evt.cancel();
  }

  but it does not work.
  I know that the javascript is available at/context-root/faces/js /, I tested that. But it seems that in the pages based on the model B, the clientListener is gone competely!

  Wendy,

  We don't recommend JavaScript accessing the DOM in ADF Faces. However, the problem comes from the use of naming containers in JSF. Page templates naming container, and thus influence the client ID of the contained components. The solution is to use search (findComponent (id)) relative or absolute search. ADF Faces has a complete client architecture that allows to search components relative or absolute. Relative, you can access them as

   function hideMededelingen(evt) {
       var outputTextField =  evt.getSource();
       //if the outputText component is in the same naming container with the component to
       //change or hide, use
      var componentToChange = outputTextField.findComponent('pt_pbl1');
      // ... do whatever you want here
  
      evt.cancel();
  }
  

  If the two components are not in the same naming container, then I recommend the use of a customer attribute. The outputText component is supposed to textField1 somewhere on a view in an access model

  1. create a managed bean and bind of JSF (subject links) component to the text field
  2 expose a clientId property on the managed bean (getter/setter) that return of the textField1.getClientId (FacesContext.getCurrentInstance ())
  3. Add an af:clientAttribute to the af: outputText and call it for example "lookupId. Assign the value # {managedBean.cientId}
  4. your JavaScript code should be modified as shown below

   function hideMededelingen(evt) {
       var outputTextField =  evt.getSource();
       var clientIdToLookup = outputTextField.getProperty("lookupId");
      var componentToChange = AdfPage.PAGE.findComponentByAbsoluteId(clientIdToLookup );
      // ... do whatever you want here
  
      evt.cancel();
  }
  

  In this way, independent of where a component is, you get its id on the displayed HTML code dynamically. If the JS code is in a JS library, then you want to go with a different approach and use a JS reminder, so you do not add the requirement of a clientAttribute. Using a JS reminder, you can change the call to clientListener to

  function hideMededelingen(lookupClientId) {
     return function(evt){
         var outputTextField =  evt.getSource();
         var clientIdToLookup = outputTextField.getProperty("lookupId");
        var componentToChange = AdfPage.PAGE.findComponentByAbsoluteId(lookupClientId);
        // ... do whatever you want here
      evt.cancel();
      }
  }
  

  Frank

• Change &amp; lt; body &amp; gt; nested template tag

  Good morning people,
  
  I work on a customer site and have been using for the main navigation Tree Menu Magic of PVII, I use models and nested models. As I have pages that are not in the tree itself, but are under the general section in the tree, I went on the site Web of PVII for a how-to on the opening of the section of a page that is not listed in the tree. They have a solution! However, this solution requires that I have change the < body > tag.
  
  Is there a workaround for this in a nested model? I saw cases where insertion FW8 HTML in a document based on a nested model will change the < body > tag for me, but how / can do it myself? Thanks a lot for any input. the customer site the customer site

  Murray,

  Thank you. I had to go the nested model, out of which rested my page and edit > model properties > allow nested models control this. Now it works! I submitted an email to PVII, however, because using the onload = "P7_TMopenUrl(1,'index.php')" actually triggers the index.php all pages of the site instead of just the one in the folder where the page updated resides the. " I tried to dig (.. /.. / folder/index.php) but who produces nothing at all.

  Thanks again for the help!

• Padding, borders, and Nested divs in fluid layouts grid Cs6

  In working with the fgl cs6, you can nest the divs effectively? He says clearly that you can't, but I tried anyway and managed somehow. Handles appear, and you can resize. How is that? However, Im confused about adding padding or borders without throwing off the grid. DW Adds padding rather recalculation. I know that you can style of the content, but how you style the div? Thanks in advance.

  Well, to summarize everything if this place, so that the design view certainly has its styles of rendering issues, there's a way for anyone who needs it.

  If you try and fill or border to any fluid grid div, design view does not well she, but she adds your styles to an empty div, inside the fluid div, it allows to achieve the result expected in design mode. I saw it in another post.

  . Padding {padding: 5px; border: 5px solid #000 ;}}

  / * Mobile layout: 480px and below. */

  .gridContainer {margin left: auto; margin-right: auto; width: 100% ;}}

  #LayoutDiv1 {clear: sentences; float: left; margin-left: 0; width: 22.4719%; display: block; background-color: #9F0 ;}}

  #LayoutDiv2 {clear: none; float: left; margin-left: 3.3707%; width: 22.4719%; display: block; background-color: #F00 ;}}

  #LayoutDiv3 {clear: none; float: left; margin-left: 3.3707%; width: 22.4719%; display: block; background-color: #006 ;}}

  #LayoutDiv4 {clear: none; float: left; margin-left: 3.3707%; width: 22.4719%; display: block; background-color: #600 ;}}

  This is the content of the div layout "LayoutDiv1."

  This is the content of the div layout "LayoutDiv1."

  This is the content of the div layout "LayoutDiv1."

  This is the content of the div layout "LayoutDiv1."

  Close enough. Four div tags with a reasonable Design view rendering and the fill and border. Otherwise, you can also style the content to get the same result.

  Design view

  

  
  

  Live View mode

  

• Optional editable areas in templates Documents nested

  Hello - I am running Mac DW MX 2004 (Version 7.0.1) and having a problem with the help of editable optional regions. Have not worked much with the models before, so am probably not see something simple that causes this problem.
  
  I searched Dreamweaver documentation and help, online support and this forum and have not found anything that is directly related to the question and I was wondering if anyone has any ideas.
  
  We build a new customer's Web site and have created a quite General (mainly to block in the design of box header and footer) main template for the site as a whole.
  
  From there, I created a template nested for all inside pages, that defines the design elements more or less common inside pages (home page will be different from the inside of pages, with the exception of the areas defined in the master site).
  
  Inside that I define, among other things, several editable optional regions in order to allow the lower level models and the pages out to control these elements (for example to allow an optional photo in a given region).
  Example code:
  
  <!-TemplateParam name = "IncludePhoto" type = "text" value = "Yes"->
  <!-TemplateBeginIf cond = "IncludePhoto == 'Yes'"--> <!-TemplateBeginEditable name = "Photo optional" - > < img class = "mmhide_LftColPic" src ="'... / imgs/lftcolpics_PHOTONAME.jpg" alt = "Photo" width = "138" height = "187" hspace = "0" hspace = "0" border = "0" align = "right" > "
  <! - TemplateEndEditable - > <! - TemplateEndIf - >
  
  
  This insidepages_master.dwt, I created another level of models nested to allow me to define specific sections of the site page design items and to allow more control in individual pages, while maintaining control over the elements common to all internal pages design. The about_master.dwt, for example, is for the site, section 'a way'.
  
  In such a nested model, because I want to let individual pages within a section to control if or not they display things like the photo option in the above example, I check the 'allow nested templates to control this' for these regions. For the example above, the IncludePhoto parameter, I check the box in the model properties dialog box command.
  
  But when I create an individual page of a model as the about_master.dwt and try to disable an optional region as for the pictures, above, (by setting IncludePhoto to 'No' with the command properties of the model), DW shows a dialog 'Inconsistent region names' box for this editable optional region, complaining that it is «< unresolved >» Box invites me to 'Move the content to a new region', with a drop of places I can stick, but, since everything I'm trying to do is tell the thing to not include this optional editable region on a page says in a section of the site, I don't understand why I even would see this box in the first place.
  
  This result keeps me from being able to control these optional editable regions in individual pages generated by these models nested, that is unacceptable. I know where I would tell him to stick, but it doesn't give me that option. :-)
  
  All the ideas I (probably) doing wrong?
  
  Please feel free to email me with questions about my ad, because I realize it can also be difficult to follow.
  
  Thanks in advance-
  
  Sheldon J. Potter
  Owner, the critical link
  http://www.essential-connect.com

  >

  Quote:

  > As much as "people who have not much used template.
  >
  > Those are your words, not mine.

  >
  > Really? Maybe you should re-read your previous post, where the foregoing
  > was
  > a direct quote.

  Your first post said-

  "Have not worked much with the models before.

  I have paraphrased that, and I think I captured the meaning of it.

  Look - it's not a p * ssing contest. Let's get solve your
  problem, OK?

  Or are you interested in trying to find a solution?

  --
  Murray - ICQ 71997575
  Adobe Community Expert
  (If you * MUST * write me, don't don't LAUGH when you do!)
  ==================
  http://www.dreamweavermx-templates.com - template Triage!
  http://www.projectseven.com/go - DW FAQs, tutorials & resources
  http://www.dwfaq.com - DW FAQs, tutorials & resources
  http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
  ==================

  "Sheldon Potter" wrote in message
  News:eho25f$NM4$1@forums. Macromedia.com...
  >

  Quote:

  > As much as "people who have not much used template.
  >
  > Those are your words, not mine.

  >
  > Really? Maybe you should re-read your previous post, where the foregoing
  > was
  > a direct quote.
  >
  > Well maybe if. If you or someone else have a better idea, I'm all ears.
  >
  >

  Quote:
  So tell me why you feel you need to use, and I'll tell you a
  > alternative approach which I think is a better way.

  >
  > Had you read the words associated with my position as first and second, which would have
  > summer
  > clear. I'm not the habit of repeating myself.
  >
  >

  Quote:
  > If you do not speak to some fans of rank here. Sonny Boy.
  >
  > In the order of things, boy, you're a whippersnapper! (8) but, clear
  > to top
  > a bit and we'll have all supported you.

  >
  > Let's see, first you have insinuated that people who are only learning a
  > technology
  > should not use it, and rather condescending way, I might add, and
  > now
  > you have direct reference to me as a 'whippersnapper '...
  >
  > Yeh, I'll lose my time, leaving a condescending, snot nose
  > arrogant
  > little * as you insult me further. Where is it written all
  > expertise you
  > maybe in some obscure technology, minor gives you register for
  > communicate
  > with people who are just asking for help in a disrespectful way?
  > Sonny boy, I shit bigger than you. Maybe you (think you) wrote the book
  > on
  > this particular technique, but, to use your words, in the grand scheme of
  > things, with this kind of pissy attitude, it is you who are the siphon
  > snapper.
  >
  > God save us from the arrogant self-appointed experts.
  >
  > I'm outa here.
  >

• Several Dreamweaver templates &amp; CSS files

  I have a site that I'm putting in dreamweaver and I have an article I want to use a different template for and have a different presentation, but I'm afraid if I change the way the divs to see my new model that it will transport you to all my other files anyway because I'd go to my css file to change them. Then do I have a css file for another model or will I be paranoid? lol also if anyone knows a good tutorials for the use of several models that would be great. I did research as above that I am at my wits end. Laughing out loud

  Well I think the answer is probably to nested models, it seems.

  Oh, no, don't do it!  Nested templates are pure hell to work with.  Even our resident model expert, Murray, said there is no legitimate reason to nest templates when you can use CSS rules specific page.

  For more ideas, post a link to one of your pages engine model and tell us what you want to change in your custom layout.

  Nancy O.

  ALT-Web Design & Publishing

  Web | Graphics | Print | Media specialists

  http://ALT-Web.com/

  http://Twitter.com/ALTWEB

• Trying in vain the nested model CS4

  I created a page with a header and footer with 1 available pass header and footer fixed and most later recorded as a model after I had designed page like I wanted. I had put a Spry menu bar in the header area and the editable main content div after implementation of the model. Creating child pages from this model is is very well conducted. Then, I decided to add a secondary navigation bar on the side for a second series of pages on the site after reading DW CS4 Missing Manual (p. 755 McFarland). He gave this example as a good time to use nested templates. I created a new template (nested model) on the original model, then add a div tag in the div of the main content (the editable area only) placed a new bar from Spry menus in the div tag I added the div as compound selector, named .oneColFixCtrHdr #sidebar.

  Everything went smoothly, except one (planned, I guess) coupling. Being in an editable area, the side menu is editable as well, and wanted further changes to the sidebar of the nested model to reflect down to child pages. So, I followed McFarland and insert an editable region empty in the sidebar div to overcome this obstacle. That did not work as he claimed he would. Although changes in the sidebar now appear on the pages of the child, the main content div was more editbable in the pages of the child. I tried a creative work around trying to temporarily insert an editable region empty in the div sidebar to change the sidebar that would lead down to the pages of the child; then after making these changes, remove the editable empty that I inserted, so that the main content div would resume its editibility in the pages of the child. It worked, except a serious hitch - when changes have been made to the menu in the sidebar model nested (with the inserted editable empty), content for the main content div of the nested model is transferred to the child pages as well - lose any content already existed in the pages of the child. That won't work!

  I wonder if originally the sidebar should be put in place in the main model as a separate region of the div. of main content but, I didn't have a sidebar in the original model, which seems to complicate things.

  I also wonder if what I'm doing could not achieved by the implementation of the sidebar as an optional region in the main model instead of trying to achieve with a nested model (have not already tried optional regions, so I don't know). I'm not too deeply in the design, so I'm ready to go direction to get the best possible results, even if I have to go back a bit. I spent many hours trying to understand this point, and it baffled me. It's all part of the learning process, I guess...

  Oh, you're right. You put some of the menus in optional regions. Well, why not put javascript code at the bottom of the page also in optional areas? Then you can turn off the power when you don't need them both on when you need it.

  In this way, the javascript code to show nor cause warnings warning because it won't be there!

  About how the var at the bottom of the page code work with menu bars, don't forget that there are also linked javascript file which is the real engine behind the functioning of the menu bar. And you may also notice, especially on the pages where you have two menu bars, each variable set at the bottom of the page is unique. If I have read and understood a little better Javascript, I could be more specific, but suffice it to say that these assignments to variables at the bottom of the page file as much as say in javascript, "see this MenuBar1 up there? Do the work for me... And see MenuBar2 up there? This work, also. »

  For the brothers of the Atonement, my link is the Director of Internet Communications at Graymoor. He praised the work of an artist in New York. Then he hired me to do the job of the Spry menu bar (in all kinds of weather... so to speak). We got along well, and he decided that he would rather call all the coding to me. But we have worked very closely together... He knew what he wanted in the end, and I knew how to get there. When one of us has tried something new, we have conferred and came with the best result.

  Now, I'm writing a description of how the functions of the site (for its use and this possibility "in the case of one of getting us hit by a bus"... hopefully it never comes to that!) The interesting part of the employment relationship, is that I never met the gentleman face to face until after the site was launched, and we worked on it for 9 months.

  Ah, modern life!

  Beth

• Why my page will not save as a template?

  I am trying to save a page as a nested model (the look will be different from the original model).  I created a page from the original model, added my divs and saved as a template.  but when I created another page of him locked areas are not locked, only from the original model.  Any suggestion would be appreciated

  Patrick

  I want to just make sure that you deploy these files correctly.  Here's how a child of a nested template page:

  1. Create an HTML page and use FILE | Save as a template.
  2. Add editable regions to this template file you just saved and save again with FILE | Record.
  3. A child from this model mate with FILE | New model...
  4. Save this page to the child as a model nested with FILE | Save as template
  5. Add regions editable to the left of the boxes since the 1st generation model and re-record with FILE | Record.
  6. A child of this 2nd generation model mate with FILE | New from template

  You have now the child of the last model and the granddaughter of the first model.  In this file, you will be able to change the editable regions you inserted in step 5 or who have been inserted for you to step 5 and all the editable regions UNMODIFIED left from the model of grandparent.  As I said, models nested are not for the faint hearted...

  Here is an example of a 1st and 2nd generation model block and block matching in a child page 3rd generation (that is, the child of a generation model 2).

  1st model generation

  
  EditRegion3
  
  

  2nd generation model * (editable area inserted inside the EditRegion3)

  
  Change R egion3
  
  

  3rd child generation

  
  Change R egion3
  
  

  Notice that in the 3rd child of the generation, the ONLY thing you can change the 'R' in the word "EditRegion3".

  Now to your example. If you do not want the left and right columns editable in the 3rd child of generation, then in the 2nd generation model, you would insert an editable around "wealthMidCol" region, which would then be the only editable thing in the begotten child page.

• Is it necessary to use containers of div in addition to structure insert parts?

  Many experienced web developers use div containers for some of the main structures such as body, header, footer etc to style sections. With the insert function in DW which is necessary or is it advisable to nest a div container inside the tags structure or vice versa?

  for example:

  <>footer

  < div id = "footercontainer" >

  content

  < / div >

  < / footer >

  or

  <>footer

  content

  < / footer >

  It is advisable to nest a div container inside the structure tags

  I don't think anyone has directly addressed the question of the OPs. So here it is:

  Elements semantic as

• changes to the template do not carry out

  Hello.  I have a site that has several sections.  I intend to use a main template that has a menu bar widget horizontal in a locked region.  Then, I create a model nested for each section.  However, when I make changes in the horizontal menu in the main model, the changes are not nested model, then the pages.  I get a message asking if I want to update pages based on this template, and all pages are listed.  I also have an end message saying update succeeded.  I really can't figure out how to get any change to the main menu horizontal model cascade through and you would appreciate the help.  Here's the page created after changing the main menu template: http://bis.illinois.edu/Test/AboutBIS/test.html here is a page created by using a nested template (and he was also supposed to be updated when I changed the main menu template: http://bis.illinois.edu/Test/AboutBIS/aboutbis.html.)  Thanks for any help you can give. I'm using CS5

  You can use something like a library item, if you are careful with the code.  This is the best way to make your widget:

  1. create a blank page "dummy", save it and insert the widget on it.

  2. Select the navigation feature in its entirety and add this object to the library (MODIFY |) Library > add object to library).  You may need to perform this selection in CODE view to be sure to get all the code of the widget - it will be easier because it's the only real content on the model page.

  3. in looking at the code, find all references to external files, or code embedded in the header of the document, copy them and paste them into the region uneditable head of the model file.  This will put this code on all pages of the child, if it is necessary or not.

  4. Insert the library item in the editable area of the child page.

  It should work.

• How can I create a template based on another model

  I have a template that I used for my article pages, but there are several changes that I do when an article page is created according to the model. I would like to create a new tamplate specifically for the pages of my article, but still have the pages of the article was updated to the evolution of the original model which has all the features that are common to all pages.

  Do not even think to go.  Nested models drive you crazy and only create problems for you, not to solve them.  I've never found an application for nested models that could not be resolved more simply and with fewer complications in other ways.

  Please show me your page and tell me what changes you want to make to the layout - and why you feel you need to use nested templates.

• Nested editable region error - but I have no nested model

  Hello:

  Decipher an error message: I need help.

  I have a global model for my site. It was working fine, then it has been disconnected from the site when my computer crashed, so I plugged back it it using site manager and import the .ste file. Now when I try to save the template or use the model, I get an error message which makes it seem like I have a nested template, but I'm not using nested templates.

  Here is what the error message says:

  There is an error on line 117, column 7, position absolute 2195

  Nested editable region

  Here's what the beginner code @ 111 line looks like:

  H6 {}
  font size: 1.1em;
  color: #960;
  }
  ->
  < / style >
  < body >
  < table width = "794" border = "0" align = "center" cellpadding = "0" cellspacing = "0" bgcolor = "#FFFFFF" >
  < b >
  < td colspan = "2" >
  "" < img src = "... / logo/brown_new_orange.jpg ' width = '807' height = '112' alt = 'Brown Golden Colorado chiropractic' > < table >
  < /tr >

  The < body > tag is at line 111. I checked for the end tag, and it seems fine. I also ran the command to check html and it found no errors.

  Any ideas what I did to generate this error message frustrating or how I can fix this problem.

  I'm not super tech savvy. I know enough to be dangerous.

  Thanks for any help you might be able to offer.

  Cindy

  Invalid HTML table height is - there never is part of the HTML language.  The content determines the height.  His presence on the page, however, is of no consequence to almost everything and this particular question.  You should be working fine with this page now...