My editable region appears to be transformed "template".

http://www.laserlines.co.UK/htm/Corp/newsandpress.htm

"Design" view of this page indicates that the 'News' and ' press release: "section is part of the model, however the code apears to indicate it is still editable. What is stop access to this space? Also when I update my model through the site, I receive a report indicating that there is a problem felt with the editable area of 'Quick Link', "InstanceBeginEditable tag inside the editable region" on this page, but the code does not seek to be different than on other pages. Clues?

> Many thanks, you've been a
> great help.

You are welcome! I am pleased that we were able to work through this.

> Is
> there a better system for tracking site traffic?

Success counters are usually the worst way to do this. The best way is to
analyze log files from your site, managed by the server session. Most of the guests
This ability - ask them. This means that you don't need a
counter on your page at all.

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

"Haberdashery" wrote in message
News:e3sh12$66N$1@forums. Macromedia.com...
> There is that Word to describe you - genius! Thank you very much, you have
> summer a
> great help.
>
> A thing, you ask using the Red Toolbox meter but don't say why?
> Is
> there a better system for tracking site traffic?
>

Tags: Dreamweaver

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]

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

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

  • 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 regions, nested on template

    The model has 2 elements of library, each container javascript rollovers and a couple of editable regions. He recorded without error and fine views. But when I try to create a file based on the template, the error reads: ' there is an error on line 152, 190 (absolute position 8582) column of... ". Filename. nested editable regions.

    http://www.aptcoweb.com/templates/aptcopage.dwt

    Now I see it. Open your model, go to line 152 and remove this block of code:

    It is a repetition of thetag and it confuses your model.

    You should also validate your model. I see several incorrect entries for XHTML. For example, images tags should be closed with a "" / > "(space-bar oblique-angled support), not just ' > '."

  • 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

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

  • 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

  • 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

  • Create a template editable region with static link "label"?

    Hello.

    Does anyone know how to create a simple and minimum link on my model (just the word 'LINK' will do)... and put an editable field * behind * the 'LINK'... If I change the destination link for the link on each page of the child?

    So, in the page of the child in particular, the visitor click on 'LINK'... then goes to a specific destination for that child page URL?

    Thank you.

    OK - just show bits of code won't work :-)

    It was initially a Frontpage design?  seems to be going by the code :-)

    You try to do this insert inside an 'editable' already defined.  (the second seizure has not been approved yet), or is it a new editable region?

    I'm afraid you'll have to put to the top of the entire page, so that we can see exactly where you are trying to add this new region.  It is better to see the page and what you tried to do to this day.   Is this possible?  You can upload it to your server?

  • Templates, backgrounds and editable regions.

    A simple question with, hopefully, a simple answer!
    I designed a site that uses a background image (800 x 600) with links mapped offshore. So far so good. I then added an editable region, and in fact a model. My problem is the positioning of parts. My background image is set to the absolute center, but the combo box takes its location between the corner of the screen, not the background, so continues to move in different size screens. Is there a way to anchor the editable region in the background, so when one moves, the other not?

    Thanks in advance,

    Hmm, tried, and everything went to pot. But after combining the first two sets of advice, everything works fine. Thanks for the help.
    P.S. I don't know the size, will sort that and other small pieces now, the site works!

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

  • Difficulty in aligning the editable regions.

    I have a site that has two different regions editable on the page index, unlike the rest which are connected to a model. the problem I have is the two editable regions to automatically be the same height.

    There is a content area of left and right content area. The left content area doesn't have a lot of context in there, however, the right content area only. When I add more content to the content area on the right, it is already programmed automatically adjust the height, as it is the left content area. However, the problem is they essentially link together, so that they are both the same height. rather than having the left side more short and to the right the 'right' length touching the footer. Instead, I find myself with a gap between the left side and the footer. is there a way to "sync" with the right box's left content area content so that they are always the same height?

    Thank you!.. .and sorry if I do not have the correct terminology [I am a little new to this...]

    I'd appreciate any help! I launched the website for a local shop and need to get updated for the big sale of the weekend.

    Thanks again,

    -ali

    If you are using CSS for layouts, it's impossible.  Height of the DIV is determined by the amount of content you put in.  Well as a dysfunctional family, Divs don't talk to everyone, so no column knows that the other is.

    Background image to tones 2 in your wrapper page, and repeat-y (bottom of the page) to simulate the appearance of the columns of the same height.  This is known as Columns of fake.  See the link below for an example.

    http://ALT-Web.com/templates/2-column-fixed-width-template.shtml

    Nancy O.
    ALT-Web Design & Publishing
    Web | Graphics | Print | Media specialists
    http://ALT-Web.com/
    http://Twitter.com/ALTWEB

Maybe you are looking for