Editable regions

I have a website with Contribute editable regions. These same editable regions are compatible with InContext? InContext will recognize these editable regions to "contribute"?

Hello threebit,

No, you can not use InContext Editing to edit regions contribute, just as you can't use Contribute to edit the InContext Editing editable regions. Please let me know if you have more questions about this.

Best regards
Corey

Tags: InContext Editing

Similar Questions

  • TemplateBeginEditable tag inside the editable region

    I bought a HTML template several years and it works fine until I updated for Dreamweaver on creative cloud. I can still update the pages, but now I can't update a page template. I get the following error whenever I try to update a page template:

    There is an error on line 49, column 47 (absolute position 2839) of (Template:main.dwt) TemplateBeginEditable tag inside the editable region

    My temporary solution was to go back to an older version of Dreamweaver (CS5) on an old Mac to make updates to the model. But I would like to solve this problem, so I can make changes in CC model.

    Here is the code to the top of the site, including the line 49 (I replaced some content meta here with "xyz")
    FYI: line 49 is: <!-TemplateBeginEditable name = "head"->

    <! DOCTYPE html >

    < head >

    < meta http-equiv = "Content-Type" content = text/html"; Charset = UTF-8 "/ >"

    < meta http-equiv = "X-UA-Compatible" content = "IE = edge, chrome = 1" >

    < meta name = "viewport" content = "width = device-width, original scale = 1.0" >

    <!-< META HTTP-EQUIV = "refresh" CONTENT = "15" > - >

    < meta name = "author" content = "xyz" >

    "< link rel ="shortcut icon"href ="... / favicon.ico ">"

    "" < link rel = "image_src" href = "... / img/logos/Lc_ZAR_dot_FE4F00_B8BABC.jpg" / >

    <!-* fonts Google / /-->

    < link href =' http://fonts.googleapis.com/CSS?family=Raleway:400,100,200,300,500,600,700,800 ' rel = "stylesheet" type = "text/css" >

    < link href =' http://fonts.googleapis.com/css?family=Lato:100, 300, 400, 700, 900, 100italic, 300italic, 400ita lic, 700italic, 900italic ' rel = "stylesheet" type = "text/css" >

    < link href =' http://fonts.googleapis.com/css?family=Open+Sans:400, 300, 300italic, 400italic, 600, 600italic, 700italic ' rel = "stylesheet" type = "text/css" >

    < link href =' http://fonts.googleapis.com/CSS?family=open+sans+condensed:300, 300italic, 700 ' rel = "stylesheet" type = "text/css" >

    <! - core bootstrap CSS - >

    "" < link href = "... / css/bootstrap.min.css" rel = "stylesheet" type = "text/css" >

    <!-Custom-> CSS

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

    "" < link href = "... / css/jquery.mCustomScrollbar.css" rel = "stylesheet" type = "text/css" >

    "" < link href = "... / css/font-awesome/css/font-awesome.min.css" rel = "stylesheet" type = "text/css" >

    "" < link rel = "stylesheet" href = "... / css/colorbox-skins/4/colorbox.css" type = "text/css" >

    "" < link href = "... / css/main.css ' rel ="stylesheet"type =" text/css">

    "" < link href = "... / css/header/h1.css" rel = "stylesheet" type = "text/css" >

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

    "" < link href = "... / css/color1.css" rel = "stylesheet" type = "text/css" id = 'site-color' >

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

    <! - LayerSlider styles - >

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

    <!-only for debugging purposes. Do not copy this line really! ->

    "<!-[if lt IE 9] > < script src="js/vendor/ie8-responsive-file-warning.js "> < / script > <! [endif]-->

    <! - HTML5 shim and Respond.js IE8 takes in charge of HTML5 elements and questions from the media - >

    <!-[if lt IE 9] >

    " < script src =" https://OSS.MaxCDN.com/libs/html5shiv/3.7.0/html5shiv.js "> < / script > .

    " < script src =" https://OSS.MaxCDN.com/libs/respond.js/1.4.2/respond.min.js "> < / script > .

    <! [endif]-->

    "< script src ="... / js/vendor/modernizr-2.6.2-respond-1.1.0.min.js "> < / script >"

    "< script src ="... / js/twitterFetcher_v10_min.js "> < / script >"

    < script type = "text/javascript" >

    <!--

    function MM_openBrWindow (theURL, winName, features) {//v2.0

    Window.Open (Theurl, winName, Features);

    }

    ->

    < /script >

    <!-TemplateBeginEditable name = "head"->

    < meta content = "description" name = "xyz" >

    < meta name = "keywords" content = "xyz" >

    XYZ < title > < /title >

    <! - TemplateEndEditable - >

    < script >

    (function(i,s,o,g,r,a,m) {I ['GoogleAnalyticsObject'] = r; i [r] = [r] i: function() {}})

    (.q i [r] = [r] i .q |) ([]) .push (arguments)}, l i [r] = 1 * new Date (); a = s.createElement (o),

    m = s.GetElementsByTagName (o) [0]; a.Async = 1; a.SRC = g; m.parentNode.InsertBefore (a, m)

    ({ }) (window, document, 'script','https://www.google-analytics.com/analytics.js', 'ga');

    GA ('create', ' UA-79018338-1 "," auto");

    GA ('send', 'consultation');

    < /script >

    < / head

    I wonder if this is related to the code Linting.  Maybe if you disable the Linting in preferences DW will leave an error appears when there seems to be none.

    Otherwise, try to restore preferences-

    Unusual behavior in Dreamweaver? Restore preferences.

    Or continue to use the previous version of DW with this model.

    Nancy O.

  • Is it possible to add an editable region where codeOutsideHTMLIsLocked = 'true '.

    Is it possible to add an editable when codeOutsideHTMLIsLocked = 'true' and an editable region is added?

    When I try the following, the first line is grayed out and cannot be changed, but the rest is not grayed out and apparently all editable.

    <!-InstanceBeginEditable name = 'model'->

    I'M EDITABLE

    <! - InstanceEndEditable - >

    I'M NOT EDITABLE

    <! doctype html >

    "< html > <!-InstanceBegin template="/Templates/main.dwt.cfm "codeOutsideHTMLIsLocked ="true"->

    < head >

    < meta charset = "utf-8" >

    <!-InstanceBeginEditable name = "doctitle"-->

    < title > Untitled Document < /title >

    <! - InstanceEndEditable - >

    <!-InstanceBeginEditable name = "head"->

    I'M EDITABLE

    <! - InstanceEndEditable - >

    < / head >

    < body >

    I'M NOT EDITABLE

    <!-Name = 'body'-> InstanceBeginEditable

    I'M EDITABLE

    <! - InstanceEndEditable - >

    < / body >

    <! - InstanceEnd - > < / html >

    I use Dreamweaver CS6 Version 12.0 Build 5861

    Take a look at templates using Dreamweaver to design a page layout, Scripts in the section server models.

  • Can you have editable regions in content holders?

    Hello world

    I had a bit of difficulty getting my work, the editable regions that, through a process of trial and error, I have locked because they do not work if included in a model by the holder of a content.

    This isn't a major problem, but it does not mean I will need the same code in all of three of the four of my models. Initially I store this code in a content holder and pulling the support content in wherever she was needed in a model.

    Of course, I prefer to do the second way for efficiency, maintainability, etc., but I'm not really sure where to start to solve the problem. Does anyone have ideas on this? Is this something that certainly can not be done, or I just do right?

    I'd be interested to hear comments, thanks in advance.

    Hello Ricki,

    You can have editable in your door-content areas, even if the owner of your content is part of the model, it will be always editable through the "Edit" tab on your admin.

    "Don't forget to add some ice: editable = 'content' in your module_contentholder, after the name =" "parameter. This doc will help you, see the.

    The second important thing is to add a coma as he is mentioned in the doc, after the module_contentholder, otherwise that the content will not be rendered, it will just show you the syntax as specified in the model, and you don't want that.

    See you soon,.

    Cristian

  • Create a nonmodifiable (coastal region) within an editable region

    Hello

    So basically, I have my main model that updates the menu and footer on all my pages. On this model, there is an editable region for most of my pages. This model, I have created several models (nested templates?) secondary. On those, I need to have a box of links on the right. Each set of links would be different based on the model and I need the secondary models to update the links on their pages.

    I work with a checkerboard in fluid, and I think that this is part of my problem. If I put the links inside the editable region "content" box then it is changes are not reflected in the updates. But if I put it outside the editable 'content' it lies either above or below the main content of the page. I want the main to wrap around the box content.

    It's my current site is NOT fluid grid. See how the text will wrap around the area outlined in green in? Program of salt marshes

    I use Dreamweaver CS6.

    Any help would be appreciated. Thank you!

    Nested models are never a good option. Never, ever.

    I recommend using 'editable optional regions' instead.

    Using Dreamweaver | Using optional regions in templates

    Or, my favorite way is to use the Server - Side Includes - alone or with models.

    ALT-Web Design & Publishing: Inclusions with PHP server-side

    Nancy O.

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

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

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

  • Model Dreamweaver, renounce the error 'instancebegineditable tag inside the editable region.

    I searched the internet and no matter what forum I can find about Dreamweaver and find the solutions that they don't did not help me, but there was a problem of command for many people. I created a template by following the steps via a tutorial from helpvid.net and the website looked very good to be pretty basic but since last night when I try save the model gives the error message "there is an error in line 8, column 47 (absolute position 789) of 'address of the file': InstanceBeginEditable tag inside the editable region.» Now from what I have read on the forums that means usually there is a spelling error or something placed inside the area when should not be, but there are only 50 odd lines on it and can't see any problem. When I view the files it gives error on, replicas of the editable 'start' there are has a number of times, but they shouldn't be there because they are not on the model. IM also conclusive that until this error came pages went well when downloaded, but now the footer height that has been set to 20px is 200px when downloaded and I check all coding for it so the Divs see but still no error. I downloaded my tempalete and some of the pages that mistakes about donations to see if that help, do not know if its better just stick wall of coding so sick message links to the files and if the code must be pasted here ill do it. http://dublinmoulding.com/ <-work im site, one can see the footer is very large. Should be 20px height but inspect element shows his 200px - #wrapper #footer {color: #FFF;}     height: 200px; The model is #wrapper #footer {color: #FFF;}     text-align: center;     margin: 0px;     do-size: 18px;     make-style: normal;     make-weight: lighter;     do-family: Arial, Helvetica, without serif.     padding-top: 5px;     padding-right: 0px;     padding-bottom: 5px;     padding-left: 0px;     height: 20px; http://dublinmoulding.com/dreamweaver/temp1.dwt <-my error tempalate is abandoned on pages created by using the template


    * Update * I've edited file names of some of the pages I used the template on so now it shows as coding.


    http://dublinmoulding.com/Dreamweaver/index.html6 <-my index page

    http://dublinmoulding.com/Dreamweaver/about.html6 <-on the page

    I've recreated the model and its not waive errors and the layout seems well, hurt that mark as resolved thank you for help

  • Fixed size on editable regions Dreamweaver?

    Dear all,

    I have inexplicable problems with my Web site template.

    Well, I did my site template Web everything is where it should be etc. However, when I try to insert an editable on my Web site region, it extends the editable area.

    It's the process that I take to insert an editable region.

    I select my "content" div tag Then I click on Insert > template objects > editable region. When I click on 'editable' my 'content' div tag extends the size of the page - which is what I don't want.

    Please can you tell me if I'm doing something wrong or if there is further about this.

    Thanks a lot for reading

    After these steps, my code is changed it-

    ...

    on this subject.

    ...

    Is that what you see also?  In this case, the editable region is not wider than the content div (i.e., 660px; such as defined in the CSS).

    What DW and which platform do you use (PC/Mac)?

  • More "label of instancebegineditable inside the editable region"

    I get an error message about instancebegineditable tag inside the editable region on http://www.jurpe.no/index.htm and I can't understand what is wrong. The error is apparently connected to line 12: <!-InstanceBeginEditable name = "description"-> and the template will not update the index file.

    Can anyone help? Thank you!

    Line 14, you have an incomplete tag.

    It should be this:

  • My hover submenu is hidden behind my editable region

    Hello

    Help, please!

    My score of submenu is hidden behind my editable region, as you can see here: http://wbindev.WS .

    Here is the code:

    {body

    Police: 100% / 1.4 Arial, Helvetica, without serif.

    Background: #666;

    margin: 0;

    padding: 0;

    {Color: #000}

    H1, h2, h3, h4, h5, h6 {}

    do-size: 100%;

    Police-weight: normal ;}

    an img {}

    {border: none}

    a: link {}

    color: #E70006;

    {text-decoration: none}

    a: visited {}

    color: #E70006;

    {text-decoration: underline}

    a: hover, a: active, a: {emphasis

    color: #E70006;

    {text-decoration: underline}

    #container {}

    Width: 980px;

    background: #CCC;

    min-height: 540px;

    overflow: hidden;

    margin: auto;

    {float: none}

    #header {}

    {Background: #FFF}

    {#strip}

    background: #E70006;

    height: 20px;

    {padding-left: 16px}

    #left {}

    Width: 210px;

    background: #CCC;

    color: #FFF;

    float: left;

    min-height: 340px;

    overflow: hidden ;}

    {#middle}

    padding-top: 10px;

    Width: 750px;

    Background: #FFF;

    float: left;

    padding-left: 10px;

    padding-right: 10px;

    min-height: 340px;

    overflow: hidden;

    do-size: 14px ;}

    {.numbered}

    {margin-left: 20px}

    #email {}

    padding-top: 10px;

    Width: 160px;

    background: #CCC;

    float: right;

    padding-left: 10px;

    padding-right: 10px;

    height: 120px;

    border-radius: 20px;

    border color: #CCC;

    {do-size: 16px}

    #navigation {}

    do-size: 12px;

    Width: 210px;

    {padding-top: 10px}

    #navigation ul {}

    margin: 0px;

    {padding: 0px}

    #navigation li {}

    list-style: none ;}

    #navigation a {}

    Color: #000;

    cursor: pointer;

    Display: block;

    height: 15px;

    line-height: 25px;

    text-indent: 10px;

    text-decoration: none;

    Width: 100%;

    padding-bottom: 20px;

    {make-weight: bold}

    #navigation li: hover {}

    Background: #F00;

    {position: relative}

    #navigation {of level ul.sub

    {display: none}

    #navigation li: hover. level Sub {}

    background: #CCC;

    display: block;

    position: absolute;

    left: 200px;

    {top: 5px}

    #navigation {of li ul.sub-niveau

    border: none;

    float: left;

    {Width: 300px}

    Can anyone help?

    Thank you

    Hannah

    www.websiteboutique.co.UK

    Try:

    #left

    {

    Width: 210px;

    background: #CCC;

    color: #FFF;

    float: left;

    min-height: 340px;

    position: relative;

    z-index: 1;

    }

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

  • Make editable no editable regions without the original model

    Hi all

    I am designing a new Web site. I created a Web page and it is a model with editable regions so that future pages would be easy to make (the parent Page). However I completely replaced the model with which was suppost to be a new model and record not relising it is the main model for my site. So to sum up, he went and is irretrievably. I have child pages of the template, but these have no editable regions and I want to make editable again so I can save it to the file of the original model so it becomes the model.

    How to make a child page's parent page or remove the editable regions without having to redraw the entire page again?

    Any help will be appreciated.

    Thank you

    I guess that there are several ways to achieve this. So here is my work flow.

    I load the child page in DW and then click on change--> models--> detach the model and I have an editable document.

    GRAMPS

  • New model Page - lack of editable regions

    When you use the new template Page, the resulting HTML code is missing from the editable regions.

    I've created a very simple HTML page, saved as a template, assigned editable regions, saved. Then, I created a new Page of the model.

    Here's the code in this file as well as the resulting HTML file.

    TestTemplate.dwt

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<!-- TemplateBeginEditable name="doctitle" -->
<title>Test Template</title>
<!-- TemplateEndEditable -->
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
</head>

<body>
<table>
 <tr>
  <td><!-- TemplateBeginEditable name="EditRegion3" -->One<!-- TemplateEndEditable --></td>
  <td><!-- TemplateBeginEditable name="EditRegion4" -->Two<!-- TemplateEndEditable --></td>
  <td><!-- TemplateBeginEditable name="EditRegion5" -->Three<!-- TemplateEndEditable --></td>
 </tr>
</table>
</body>
</html>

    TestTemplate.html

    <!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>Test Template</title>
</head>

<body>
<table>
 <tr>
  <td>One</td>
  <td>Two</td>
  <td>Three</td>
 </tr>
</table>
</body>
</html>

    I use Dreamweaver CS5 (Version 11.0 Build 4993) on MAC OS X 10.6.8.

    This is the first time that I am using models in CS5. They worked fine when I used CS4 (on the same computer). Now I have CS5.

    Note that your child page contains model NO markup at all.  This means that when you created it, you should not do check the box called "update page when the template is changed" (on the right side of the new Document dialog box).  Could this be it?

  • Templates in DW CS5.5 and editable regions

    I have a model page that has an editable region defined as follows:

    < div class = "sidebar1″" >

    < nav >

    < ul >

    < li > < a href = "#" > home < /a > < /li >

    < li > < a href = "#" > < /a > < /li >

    < li > < a href = "#" > < /a > < /li >

    < li > < a href = "#" > < /a > < /li >

    < li > < a href = "#" > Members Only < /a > < /li >

    < li > < a href = "#" > Gallery < /a > < /li >

    < li > < a href = "#" > Constitution < /a > < /li >

    < li > < a href = "#" > links < /a > < /li >

    < /ul >

    < / nav >

    <!-InstanceBeginEditable name = 'all'->

    < / div >

    <! - end .sidebar1 - >

    < section class = "content" >

    CBEF clubs < h1 > < / h1 >

    < section >

    other code goes here

    < / section >

    <! - InstanceEndEditable - >

    Note the < / div > tag after the beginning of the editable region. It's a tag that is appropriate, it is necessary to close the div sidebar1″

    When he is not in an editable area, the < / div > shows no upward in yellow in design veiw and it works in every respect.

    When the combo box is introduced, the < / div > shows yellow in design mode, and it works in all respects.

    It validates using the W3C validation page.

    Pages built with it also show the yellow label, but they do not display it when live or in a browser.

    If I delete the < / div > as dreamweaver indicates, breaks css and page do not work.

    It seems that DW thinks that it is an illegal tag. If I click my mouse on the <!-InstanceBeginEditable name = 'all'-> tag and collapse of the tag, all the code in the edit box + than in the sidebare 1 div (even starting before the editable) collapses. The editable area does not allow changes in the sidebar1″ outside the region code.

    I need to put the editable region in the part of the sidebar div 1 so that I can add aditional items floated in box 1 div if necessary later.

    Is this a bug or am I missing something?

    It would be more logical.

    Some unique sidebar1″ content goes here

    The unique position here

    another code

    Nancy O.

    ALT-Web Design & Publishing

    Web | Graphics | Print | Media specialists

    http://ALT-Web.com/

    Post edited by: Nancy O.  I forgot to close the div. I'm glad

Maybe you are looking for