Editable regions, nested on template

Similar Questions

• Make editable regions in a template

  I have a model in which I want to make an editable region uneditable.  Is this possible?

  Appreciate any input

  Gilbert

  Yes.

  With the model of open file, select the area you want to make editable and go to insert > template objects > editable region and then give it a meaningful name.

  Alternatively, wrap the code around the area you want to be editable and name, below, both do exactly the same thing: just in different ways.

• Editable region in the template?

  How to "Cancel" a region that has been grayed out as non-editable in a model.

  • There seems to be two different style sheets associated with the model, and I want only correct.
  • For a particular model, I want to be able to comment on the trial in the right column

  I can not change or any of these things because they are not editable now.

  Thanks for your help.

  You can, of course.

• Make BODY tag an editable region in the template

  Hello
  
  I need to have the modified BODY tag in my template, how it works. Because I need to add an onload for some pages.
  
  Found the answer in the Forum :-)
  
  Thanks for help
  Denis

  Hello

  I need to have the modified BODY tag in my template, how it works. Because I need to add an onload for some pages.

  Found the answer in the Forum :-)

  Thanks for help
  Denis

• Messed up the editable regions in the documents based on templates

  Y at - there no way to fix corrupt editable regions in a document?

  We have 2 editable regions in a template: -.

  <!-TemplateBeginEditable name = "MidText"->

  < p > < / p >

  <! - TemplateEndEditable - >

  <!-TemplateBeginEditable name = "LowText"->

  < p > < / p >

  <! - TemplateEndEditable - >

  In several documents based on these models, the name has been deleted by mistake: -.

  <!-TemplateBeginEditable name = ""-> "

  < p > < / p >

  <! - TemplateEndEditable - >

  <!-TemplateBeginEditable name = ""-> "

  < p > < / p >

  <! - TemplateEndEditable - >

  If we try to update the documents in an attempt to fix, we get the following error message:

  There is an error on line..., column... (absolute position...) of "nomDuDocument": name missing for InstanceBeginEditable ""

  If we try to update using the templates, we get the following error message:

  no update, error in the file of template or instance

  Is there a 'fix' for this?

  Thank you.

  Looks like you know what you're doing.

  Assuming your child pages are incorrect, try closing DW and open the problem page in a simple editor like Notepad or Simpletext ascii text, add in the missing name values (remember to use the proper case) and save & close them.

  Then see if DW is happy.

• How to apply a template with a new editable region to a group of existing pages

  Hello

  Here's my question:

  1. I have a group of web pages that were created by using a template with editable regions.

  2. I added a new editable region to a template that should be added to the previous pages.

  What is the procedure to add the new editable region to previous web pages?

  Thanks for your advice

  Juan

  When you have saved the model, you have been invited by Dreamweaver to ask if you want to update pages based on the template. As long as you click Update, the new editable region should be in the pages of the child.

• How to make the model editable editable region

  Hello I have a spry menu bar that is outside the editable regions in a template.  How do I access it to make it editable, or I have to start from scratch?

  All the content on a page template is editable.  Only editable content is editable on model child pages.  If you open a page of model and cannot change some content, is that you open a model nested child, or your template markup is watered.  Do you use nested templates?  You can see the code on the template page?

• Can't change an editable region

  Hello

  I've defined two editable regions in a template. I can change a fine, but not the other. The I can't change is for a submenu and picture on this site: 67.199.64.241/

  Any ideas? Any help would be greatly appreciated.

  This is the code (I can't edit in context):

  < ul id = "navleft" >
  < id li = "nav_hom" > < a href = "/ index.asp" > home < /a > < /li >
  < id li = "nav_do" > < a href = "/ whatwedo.asp" > us < /a > < /li > ""
  < id li = "nav_cabout" > < a href="/consumers/login.asp" > < /a > < /li > current consumer»
  < id li = "nav_pabout" > < a href="/pa/about.asp" > current not < /a > < /li > ".
  " < id li ="nav_cal"> < a href =" http://www.calendarwiz.com/calendars/calendar.php?CRD=cdchoices & "target ="_blank"> calendar < /a > < /li > "
  < id li = "nav_pro" > < a href="/profiles/profiles.asp" > profile < /a > < /li > ".
  < id li = "nav_news" > < a href = "/ news.asp" > CDC in the news < /a > < /li > ""
  < id li = "nav_lnk" > < a href = "" / links.asp "> links < /a > < /li >"
  < id li = "nav_blank" > < a href = "" / message.asp "> Message from the Director general < /a > < /li >"
  <!-TemplateBeginEditable name = "OptionalMenuPicture"--> < an id = "submenu" name = "MainContent2" > < / a >
  < class li = "c2" >
  < div ice: editable = "media, hypertext link, css_styles" >
  OptionalMenuPicture
  < / div >
  <! - TemplateEndEditable - >
  < /ul >

  Use this:

  
  
  • Home
  
  
  • Who we are
  
  
  • Today's consumers
  
  
  • No classes
  
  
  • http://www.calendarwiz.com/calendars/calendar.php?CRD=cdchoices&"target ="_blank"> calendar"
  
  
  • Profiles of school boards
  
  
  • CDC in the news
  
  
  • Links
  
  
  • Message from the Director general
  
  
  
  
  
  
  
  New? To learn more:
   
  • & gt potential consumers
  
   
  • & gt prospective Personal Assistants
  
   
  • & gt search site
  
  
  
  
  
  
  
  • 
    
  
  
   

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

• 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

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

• Templates and editable regions &lt; body &gt;

  I have a model for the site with all the div, as I would like.

  If I area-editable regions, then where it says < body > in the template - it can be changed in a single page to say

  < body onload = "DoThis (); ">

  because as soon as you open the template, it is up to the page back to the < body > and the onload bit is lost.

  I wanted to use templates to maintain consistency, but when you have problems with the editable regions all the time that I wonder if this is a feature implemented there to help or harm us.

  I tried to put the tabs html in an editable area, but then the said model id had not.

  Please how can I do the < body > tag editable in the various documents because I want this function to launch the load on one page only.

  The only way around this would be to have an onload for each page and have only a function empty on the pages that is not required, but it's unprofessional.

  I think that there is another thing like document.ready but don't know where to put it in the document, and if it is as effective.

  THANK you for any comments.

  TERRY

  Try this, you can use it in any region can be changed as thesection of the page.

• Nesting of regions not editable within editable regions? [CS5]

  Hello, I'm running into a situation where I have a template resembling structure:

  < ul id = "outside" >

  < class li = "nohighlight" > < a href = "something.html" > page < /a >
  < ul id = "inner" >
  < li > < a href = "other.html" > a subpage < /a > < /li >
  < /ul >
  < /li >

  < class li = "highlight" > < a href = "something2.html" > another page < /a >
  < ul id = "inner2" >
  < li > < a href = "other2.html" > an other sub page < /a > < /li >
  < /ul >
  < /li >

  < /ul >

  Now what I would like to apply to create new documents html of the model which uses the structure above, and be able to change the CSS class to the new document. This is easily done by li (external) tags in editable regions. But I would also like to change/update power lists "interiors" in the template file and apply these updates to all files using the template.

  Something like:

  <!-TemplateBeginEditable name = 'Navbar1'-> < class li = "nohighlight" > < a href = "something.html" > page < /a > <! - TemplateEndEditable - > "
  < ul >
  < li > < a href = "#" > The Hydrological Cycle < /a > < /li >
  < /ul >
  < /li >

  Does not work as Dreamweaver ends up filling the tag < li > automatically when models are applied, leaving the document with two < /li >.

  Is it possible to make a non editable child tag, and so to do update files when the model is updated, what its parent tag CSS class remains editable?

  Thank you

  Ron

  Build your menu with an indication of the persistence of page, and you will not need to change anything on your page except the name of the body class.

  I keep my menus side Server include files, and this method works very well.

  http://forums.Adobe.com/message/2647186#2647186

  Nancy O.

  ALT-Web Design & Publishing

  Web | Graphics | Print | Media specialists

  http://ALT-Web.com/

  http://Twitter.com/ALTWEB

  http://ALT-Web-design.blogspot.com/

• How can I create CSS for the editable regions in the documents based on templates?

  I created a template in Dreamweaver CS4 by using their set of 3 columns, header and Footer option available. The model works fine in the browser. I inserted an editable region in the empty middle of the model column. I created a new page based on this template and want to be able to format the text that I entered in the editable using CSS. Any time, I try to create a new CSS rule I get the following dialog:

  "This change should change the code which is locked by a model or a translator. The changes will be rejected. »

  Is it possible to create new CSS, which will apply to the information entered in the regions be modified of a document based on a template? Simple step by step instructions would be appreciated.

  Thanks for reading

  Do not know what is the 'id' of the middle column, but you must target the text inside that

  .

  Example:

  {#whatever}

  color: #639;

  do-size: 12px;

  }

  It is better if the text in the middle column is paragraphs and target you them as as follows:

  #whatever p {}

  color: #639;

  do-size: 12px;

  padding: 0 15px 15px 0 / * top, bottom, right, left * /.

  }

  You must make sure that you include the above in the editable page css region and HE MUST come after any link to the style sheet css main.

  If in doubt post the code for the page here and say what you want to be purple and I'll have a look.

  The tip is stop created with the css dialog box in DW, it's a load of bollocks and started writing some simple css directly in the page itself. It is easier and gives you more control than any interface automated half cooked in the oven.

  Start learning some simple css. There is absolutey zillions of resources on the net. A couple of hours well spent and your miles further. If you keep pressing DW to do everything for you, then I'm afraid you'll just be going around in circles.

  Enter the code and don't be afraid of him, take it apart and see how it works. Slowly step by step and little by little you will realize how simple structures are and how simple css really is.

• How to remove the template and editable regions?

  Hello world

  I posted this question earlier in the area of discussion web to ignore a specific Dreamweaver forum. Sorry for posting in two places.

  Since last week, I learned Dreamweaver CS4 to an on-line tutorial. I got to the place where I have generated a model (index.dwt) homepage (index.html) and created boxes on it. At that moment, I realized that I had done all the steps of the Rota and that he didn't really absorb what I was doing. I wanted to delete the model to repeat and acquire a better understanding of the process. When I tried to remove the editable regions (change-models-remove editable regions), I was unable to do so because 'remove the editable regions' is gray. Nor I was able to remove the html code. I tried to delete the template itself, but when I did, the index.html page kept these editable regions! Can someone tell me if there is a way to get back to the place I was forward to create the model?

  Thank you for any assistance.

  All you need to do is detach the template index.html file.  Then you can remove the template and start all over again.

  Go to the menu change--> models--> detach the model