Duplicate Editable Regions (DW,CS5)

Hi, every time i try and save my file as a template an error message pops up saying: There is an error at line 165, column 8 (absolute position 6235): Duplicate editable regions of name "Document Head"
Please help
Thanks:)

The error message you are getting should be translated to read "Oops - your code is a mess".
You have two <head> tags and three </head> tags, and you have an embedded CSS styles sheet between </body> and </html>!
You also have this code in place - it should be deleted -


Fix that, validate your page at http://validator.w3.org, and when it validates, then you can save it without error.

Similar Messages

Nesting uneditable regions inside editable regions? [CS5]

Hello, I am running into a situation where I have a template structure looking like:
<ul id="outer">
     <li class="nohighlight"><a href="something.html">A page</a>
                 <ul id="inner">
                        <li><a href="other.html">A subpage</a></li>
                 </ul>
     </li>
     <li class="highlight"><a href="something2.html">Another page</a>
                  <ul id="inner2">
                         <li><a href="other2.html">Another subpage</a></li>
                  </ul>
      </li>
</ul>
Now what I would like to do be apply to create new html documents from the template that uses the above structure, and be able to edit the CSS class in the new document. This is easily done by making the (outer) li tags into editable regions. But I would also like to be able to modify/update the "inner" lists in the template file and apply these updates to all files using the template.
Something like:
<li class="nohighlight"><a href="something.html" >A page </a>
            <ul>
              <li><a href="#">The Hydrological Cycle</a></li>
            </ul>
        </li>
Does not work as Dreamweaver ends up auto-completing the <li> tag when templates are applied, leaving the document with two </li>.
Is there a way to make a child tag uneditable and hence to make it update in files when the template is updated, when its parent tag's CSS class remains editable?
Thanks,
Ron

Build your menu with a persistent page indicator and you won't need to change anything on your pages except the body class name.
I keep my menus in server-side include files and this method works great.
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/

Duplicating an Editable Region

Is it possible to duplicate an editable region without
getting the error "Duplicate editable regions found". I need to
duplicate the content in one editable region multiple times. I have
Windows XP SP2, version 7.0.1. Thanks!

Are you interested in duplicating the region or the region's
contents? If
the latter just copy and paste it as many times as you
need...
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Acta non verba" <[email protected]> wrote
in message
news:e6skvq$cla$[email protected]..
> Is it possible to duplicate an editable region without
getting the error
> "Duplicate editable regions found". I need to duplicate
the content in one
> editable region multiple times. I have Windows XP SP2,
version 7.0.1.
> Thanks!
>

Can't click inside editable region in template based HTML document in CS5

Hi Everyone,
I m having a strange problem in Dreamweaver Cs5. After making the html page based on template, when i am opening the HTML page to edit content in editable region, I couldnot click inside the editable region. I can make changes in code view but not in design view in Dreamweaver Cs5.
Please help if anyone knows the solution. It is really creating a mess for me.
Thanks,
Komal

One of the sites is www.ShelbyVideo.com.
The code for one of the pages is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<meta name="description" content="SHELBY VIDEO SERVICES: Shelby, NC Video services that are inexpensive, professional, and thorough! Offering corporate and wedding video production services in and around Shelby North Carolina and South Carolina." />
<meta name="keywords" content="shelby video, shelby videographer, shelby videography, shelby nc video, north carolina shelby video, shelby video camera, shelby videos, north carolina videos, nc video, shelbyvideo, shelbyvideo.com, shelby video production, shelby video services, cleveland county video, cleveland county wedding video" />
<title>Shelby Video Production Services: SheblyVideo.com offering videography services in the Carolinas.</title>
<link href="css/main.css" rel="stylesheet" type="text/css" media="projection,screen" />


</head>
<body class="body">
<div id="wrapper">
<div id="header">
    <p><a href="http://www.shelbyvideo.com"><img src="images/shelby-video-logo.jpg" alt="Shelby Video Services" name="weddingVideo" width="216" height="77" border="0" id="weddingVideo" /></a></p>
    <p><a href="index.html">HOME</a>   <a href="shelby-nc-video-services.html">SHELBY VIDEOS</a>   <a href="shelby-video-demos.html">DEMOS</a>   <a href="shelby-video-prices.html">PRICES</a>   <a href="shelby-video-faqs.html">FAQ'S</a>   <a href="shelby-video-north-carolina-reviews-testimonials.html">TESTIMONIES</a>   <a href="shelby-video.html">BOOK US</a></p>
</div>
<div id="mainContent"><br />
    <h1>ShelbyVideo.com</h1>
    <div id="carolinaWeddingVideoDiv">
      <object width="300" height="182">
          <param name="movie" value="http://www.youtube.com/v/QUSnPSLdnG0&hl=en&fs=1&" />
          </param>
          <param name="allowFullScreen" value="true" />
          </param>
          <param name="allowscriptaccess" value="always" />
          </param>
          <embed src="http://www.youtube.com/v/QUSnPSLdnG0&hl=en&fs=1&" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="300" height="182"></embed>
      </object>
    Shelby Video Demo</div>    <p> </p>
    <p>Welcome to Shelby Video Services. We have been producing videos in Shelby North Carolina and South Carolina since 2004. </p>
    <p> </p>
    <p>Your video will be professional and comprehensive. We will beautifully cover your video production in a way that will propell your business into your market and/or enable you to relive your special event over and over and enjoy sharing with others.</p>
    <p> </p>
    <p> </p>
    <p> </p>
</div>
<div id="footer">© <a href="index.html">Shelby Video Services</a><br />
<a href="shelby-nc-video-services.html">shelby nc video services</a> | <a href="shelby-video.html">start here</a> | <a href="shelby-video-demos.html">demos</a> | <a href="links.html">links</a> | <a href="sitemap.html">site map</a> | <a href="shelby-video.html">contact</a> | <a href="shelby-video-north-carolina-reviews-testimonials.html">testimonials</a></div>
</div>
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-9484651-2");
pageTracker._trackPageview();
} catch(err) {}</script>
</body>
</html>
Because I didn't create the code, rather it was dreamweaver, i believed that DW is obviously broken. Because I have a bunch of sites I made in earlier versions and when I start using a newer versions, CS5, I now can't access the editable region in any of them it seems DW is broken. So, I didn't think the code was necessary. I thought it was something that others have already experienced and resolved. However, that doesn't seem to be the case. Thanks though for helping with what appears to be broken. Hopefully it's an easy fix because there's other sites I have that this annoyance is plaguing me...

Not able to edit editable regions in contribute CS5

Hi there,
i got a question i need to ask according to the helpdesk i just spoke to. I've downloaded the Contribute CS5 trial yesterday and i wanted to show my costumer how to edit pages and create new ones. I've made the connection to the website and tried every possible thing but the only thing i can edit is the first editable region wich i always leave blank (the designer build in some hidden text there). The rest of the editable regions, named header and content can't be edited. How is this possible? This is only on the most existing pages. Creating new ones do not appear to have the same problems.
i work with contribute CS4 and everything works fine. I can edit pages fully and publish everything like it should be. To be sure i also downloaded the trial CS5 to my laptop and i got exactly the same problem as described above.
How can help me out?
cheers
Jarno

Hello Pravin,
I have the complete access, but all of sudden three icons started missing .
Thanks,
Srini

ERROR: cannot edit or duplicate page. Reason: no editable regions

Hi,
Going round in circles with this one. Feeling like Friday afternoon.
URL: http://www.business-risc.com/fleet/bss/1/index.html
CtrlE works fine.
Click on "POLICIES" spry tab
Click on EDIT PAGE
Highlights the correct editable region... hover confirms its an editable region.
Allows me to edit, no problem.
Then, on SAVE DRAFT or DONE returns ERROR: cannot edit or duplicate page. Reason: page does not contain any editable regions.
I just cant see why. Can anyone help please?
Thanks
Carol

There should be a space before the ice:editable attributes (all of them):
class="TabbedPanelsContent"ice:editable="*"
Regards,
Dan Popa

Duplicate TIFF files when using "Edit in PS CS5"

Hello there,
I'm using LR 4.3 and CS5, with ACR 6.7 installed. Whenever I'm using "Edit in PS CS5" comand inside LR, automatically I'm getting a duplicate TIFF file added to my LR catalog. How can I avoid this? Thank you for your time!

bcondoral wrote:
So this happens because 4.1 is compatible with ACR6.7 and 4.3 is not?
There are two basic behaviors regarding Lightroom and Camera Raw versioning:
If the Lightroom version and the Camera Raw version are equal (meaning LR 4.3 and ACR 7.3) Lightroom passes the image from LR to Photoshop using ACR to render the file. In this case, LR doesn't need to render the file and to the -Edit save when opening into Photoshop. Photoshop does the render and when saved, will pass that file creation back to Lightroom for adding in the catalog.
However, whenever the LR version and ACR version do NOT match, Lightroom does the rendering (to be sure of proper rendering) and save the file on disk before passing the image to Photoshop. So, if you are using mismatched LR/ACR versions, this second behavior comes into play.
As ssprengel correctly notes, there was a slight modification to these behaviors when LR 4 first shipped because it shipped before Photoshop CS6 and ACR 7 shipped. LR 4.0 and 4.1 (the quick dot release for camera compatibility reasons) were made to work with ACR 6.7 in Photoshop CS5 with the first behaviors working...
LR 4.2 and above do not have the ACR 6.7 compatibilities so the behavior of the LR render and file saving requirement kicks in.
For optimal compatibility both LR and ACR should be kept in lock-step. Since the release of CS6, ACR 6.7 is the last version of ACR for CS5, so you lose some intigration and functionality by not upgrading to Photoshop CS6 and ACR 7.x.

Templates in DW CS5.5 and editable regions

I have a template 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>
    
</div>
      
<article class="content">
    <h1>BCEF Clubs</h1>
    <section>
other code goes here
</section>

Note the </div> tag after the start of the editable region. This is a proper tag, as it is needed to close the sidebar1 div.
When it is not in an editable region, the </div> does not show up in yellow in design veiw and it works in every repect.
When the editable region is introduced, the </div> shows yellow in design view, and it works in every respect.
It validates using the W3C validation page.
Pages built with it also show the tag as yellow but they do not display it when live or in a browser.
If I delete the </div> as dreamweaver suggests, the css breaks and the page will not work.
It seems that DW thinks that this is an illegal tag. If I click my mouse on the  tag, and collapse the tag, all the code in the editable region + that in the sidebare 1 div, ( even that before the editable region begins) collapses. The editable region does not allow edits in the sidebar1 code outside the region.
I need to put the editable region within part of the sidebar 1 div so that I can add aditional floated items in the sidebar 1 div if needed later.
Is this a bug or am I missing something?

This would make more sense.
</nav>

<p>Some unique sidebar1 content goes here</p>

</div>
<article class="content">

<h1>Unique heading here</h1>
<section>
other code
</section>

</div> 
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
Message was edited by: Nancy O. Forgot to close the .content div.

How to insert a widget in a editable region from a template

Hi there,
ok so basically I am trying to create a HTML page from a template i have already designed.
when I try to insert a widget (Lightbox Gallery) in the editable region I get the following error.
"the widget requires code that must be inserted into the head of the document. insertion cannot happen because this document is read only"
I saw a previous thread (http://forums.adobe.com/thread/901299) that had the same problem with a solution but cant seem to make sense of it.
Not exactly sure where and what to paste in the header of the HTML page.
Any help will be much appreciated.
Thanks

Hi Murray,
ha funny you would say that is the exact answer you would give me seeing you posted it
I understand the logic behind it though not sure what i need to copy and where.
Basically i craeted a "dummy page" and inserted the widget-no problem there.
next step- what code do i copy from the dummy page and where do i paste it? in the template or HTML page.
Dummy HTML with widget code
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Untitled Document</title>
<script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/jquery.js" type="text/javascript"></script>
<script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/lightbox.js" type="text/javascript"></script>
<link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/lightbox.css" rel="stylesheet" type="text/css" />
<link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/sample_lightbox_layout.css" rel="stylesheet" type="text/css" />
<style type="text/css">
/* BeginOAWidget_Instance_2127022: #gallery */
                    .lbGallery {
                              /*gallery container settings*/
                              background-color: #CCC;
                              padding-left: 20px;
                              padding-top: 20px;
                              padding-right: 20px;
                              padding-bottom: 20px;
                              width: 540px;
                              height: auto;
                              text-align:left;
                    .lbGallery ul { list-style: none; margin:0;padding:0; }
                    .lbGallery ul li { display: inline;margin:0;padding:0; }
                    .lbGallery ul li a{text-decoration:none;}
                    .lbGallery ul li a img {
                              /*border color, width and margin for the images*/
                              border-color: #3e3e3e;
                              border-left-width: 10px;
                              border-top-width: 10px;
                              border-right-width: 10px;
                              border-bottom-width: 20px;
                              margin-left:5px;
                              margin-right:5px;
                              margin-top:5px;
                              margin-bottom:5px:
                    .lbGallery ul li a:hover img {
                              /*background color on hover*/
                              border-color: #ffffff;
                              border-left-width: 10px;
                              border-top-width: 10px;
                              border-right-width: 10px;
                              border-bottom-width: 20px;
                    #lightbox-container-image-box {
                              border-top: 0px none #ffffff;
                              border-right: 0px none #ffffff;
                              border-bottom: 0px none #ffffff;
                              border-left: 0px none #ffffff;
                    #lightbox-container-image-data-box {
                              border-top: 0px;
                              border-right: 0px none #ffffff;
                              border-bottom: 0px none #ffffff;
                              border-left: 0px none #ffffff;
/* EndOAWidget_Instance_2127022 */
</style>
<script type="text/xml">

</script>
</head>
<body>
<div id="gallery" class="lbGallery">
<ul>
    <li> <a href="/images/lightboxdemo1.jpg" title=""><img src="/images/lightboxdemo_thumb1.jpg" width="72" height="72" alt="Flower" /></a> </li>
    <li> <a href="/images/lightboxdemo2.jpg" title=""><img src="/images/lightboxdemo_thumb2.jpg" width="72" height="72" alt="Tree" /></a> </li>
    <li> <a href="/images/lightboxdemo3.jpg" title=""><img src="/images/lightboxdemo_thumb3.jpg" width="72" height="72" alt="" /></a> </li>
    <li> <a href="/images/lightboxdemo4.jpg" title=""><img src="/images/lightboxdemo_thumb4.jpg" width="72" height="72" alt="" /></a> </li>
    <li> <a href="/images/lightboxdemo5.jpg" title=""><img src="/images/lightboxdemo_thumb5.jpg" width="72" height="72" alt="" /></a> </li>
</ul>
</div>
<script type="text/javascript">
// BeginOAWidget_Instance_2127022: #gallery
                    $(function(){
                              $('#gallery a').lightBox({
                                        imageLoading:                              '/images/lightbox/lightbox-ico-loading.gif',                    // (string) Path and the name of the loading icon
                                        imageBtnPrev:                              '/images/lightbox/lightbox-btn-prev.gif',                              // (string) Path and the name of the prev button image
                                        imageBtnNext:                              '/images/lightbox/lightbox-btn-next.gif',                              // (string) Path and the name of the next button image
                                        imageBtnClose:                              '/images/lightbox/lightbox-btn-close.gif',                    // (string) Path and the name of the close btn
                                        imageBlank:                                        '/images/lightbox/lightbox-blank.gif',                              // (string) Path and the name of a blank image (one pixel)
                                        fixedNavigation:                    false,                    // (boolean) Boolean that informs if the navigation (next and prev button) will be fixed or not in the interface.
                                        containerResizeSpeed:          400,                               // Specify the resize duration of container image. These number are miliseconds. 400 is default.
                                        overlayBgColor:                     "#999999",                    // (string) Background color to overlay; inform a hexadecimal value like: #RRGGBB. Where RR, GG, and BB are the hexadecimal values for the red, green, and blue values of the color.
                                        overlayOpacity:                              .6,                    // (integer) Opacity value to overlay; inform: 0.X. Where X are number from 0 to 9
                                        txtImage:                                        'Image',                                        //Default text of image
                                        txtOf:                                                  'of'
// EndOAWidget_Instance_2127022
</script>
</body>
</html>
thanks again

Nesting Templates: Child-Template Pages not Fully Responding to Editable vs. Un-Editable Regions

M'kay, so first and foremost, all of this is being done within Dreamweaver CS5. How I might explain this is that I have a series of Master-Templates for my website, accompanied then by Child-Templates linked off of / nested from my Master-Templates. So far this is going wonderfully, that is, until I try to make a page from one of my Child-Templates.
The page from my Child-Template accurately comments-out an un-editable region (Region in which was editable within the Master-Template, but left as ONLY editable within the Child-Template) so long as I add an EDITABLE region WITHIN it. Under the circumstance that I DO NOT add an editable region within the Master-Template's editable region, the region within the Page is still appearing editable.
For example:
Master Template:

     Child Template CSS Links Here.

Child Template:

     Child Template CSS Links Here.
     
          Child PAGE CSS Links Here.
     

Child Page:
Child Template CSS Links Here. (Accurately appearing Un-Editable - {Master-Template's editable region tags accurately appearing invisible})

     Child PAGE CSS Links Here. (Accurately appearing Editable)

This is an example of an editable regions that WORKS. In the Child-Page the "Child Template CSS Links Here." IS appearing commented out and therefore un-editable within the Child-Page, like it's supposed to be. This then allows the "Child PAGE CSS Links Here" to be ACCURATELY editable within the Child-Page.
Now for an example of what DOESN'T work:
Master Template:

     Child Template CSS Links Here.

Child Template:

     Child Template CSS Links Here.
     (As you see, I have NOT added an additional editable region within this Master-Template's editable region. This is an area that is ONLY supposed to be editable within the Child-Template and NOT the Child-Page, which SO FAR appears to be accurate.)

Child Page:

     Child Template CSS Links Here.
     (For some reason, ONLY so long as I DO NOT add an additional Child-Template-editable-region within this Master-Template's editable region, this area is STILL appearing visible as well as editable within the Child-Page.)

So, under this circumstance, it seems that the only way I can leave a Master-Template's editable region ONLY editable within the Child-Template and NOT editable within the Child-Page is by leaving an ADDITIONAL editable region produced via the Child-Template somewhere within EVERY SINGLE editable region produced via the Master-Template. Unless I am doing something seriously wrong, this so far appears to be a potential defect/bug within Dreamweaver CS5. I can't imagine how this would be accurate, otherwise Child/Nested-Templates would not be possible to make. What might I be doing wrong? Is there any way that I can specify in the Master-Template that an Editable Region is ONLY Editable within the Child-Template and NOT within further Child-Pages (A Page based off of the Child-Template)? Or perhaps is there a way that I can specify in the Child-Template that an editable region WILL NOT be editable within the Child-Page? Furthermore, no, I DO NOT want to make them "Optional Regions," so please do not suggest that.
I know that this is all probably a bit confusing, but hopefully the examples above will help more than the descriptions aside. As you can probably assume, this is definitely a HUGE complication within my website if there doesn't end up being a solution, especially with all the time I have put into making the Child-Templates that I hope to rely on. It really would be a bit ridiculous if I had to script-in an additional editable region within every single Master-Template-editable-region available within my Child-Template just so that I may update my Child-Template, furthermore allowing my edits to drop down to my Child-Pages, especially since it would maintain content that I never wanted to be editable within the Child-Page in the FIRST place.
Some help would be sincerely appreciated, and as soon as possible, if I might ask politely.
Thank you. Sincerely,
~ Miss Cat

=____= I cannot believe that I am saying this, after writing ALL of that up, but thanks to "Dreamweaver CS5 for Dummies," I just learned that if you place: @@(" ")@@ within the Child/Nested Template's editable region that you DO NOT want passed down to your Child-Pages, it won't appear editable. Goodness knows why such an inconspicuous formula was the answer, but I guess whatever works. ...WHY WAS THIS INFORMATION SO DIFFICULT TO FIND?!?!?!?! @____@ Information on Nested Templates in general seems rather difficult to find, however, so I'm glad I figured this out /not ever a full hour/ after writing all this up and posting it. #__# ...At least my Child-Templates can work thoroughly now, though. So... Scenario FIXED. ^^
I only hope now that such information will appear helpful to anyone else hunting for this information via Google or other Search Engine in the future. And if there is anything at all that I am still officially missing, then do feel free to add it to the feed and let me know, because the last thing I need right now are more surprise difficulties to equally slow down the productivity of this massive project I've been working on... @___@ ..But so far things seem to be going good. ^^ So I can settle myself unbelievably grateful that there ended up being a solution to this ridiculousness after all.
Sincerely,
Miss Cat
[signature promo info removed by moderator]

Spry Tabbed Panel Content editable region not functioning

I have a web page I created in dreamweaver CS5 with a tabbed panel. When my client opens the page to edit in contibute, the content and tabs do not function properly. Basically, the tabs do not function and the content for all of the tabbed regions is listed down the page on the first tab window. The page works fine when I open in Contibute on my computer, but only if it is through the Contibute Program. If I try to edit through firefox, I get the same issue as my client.
http://menwieldingfire.com.previewdns.com/bbq/bbq-menu.html
also, I get a space between the header image and the horizontal menu that goes white. I end up having to re-upload the page from dreamweaver. Why would the follow code get added to the page when a draft is created in Contribute, when this page is based on a template with editable regions?
< p style="margin-top: 0; margin-bottom: 0;"> </p >
Any ideas?

Check http://blogs.adobe.com/contribute/2010/06/paragraph_spacing_options_in_a.html and also http://blogs.adobe.com/contribute/2010/06/spry_widget_rendering.html it should be helpful to resolve the issue.

Dreamweaver template giving up "instancebegineditable tag inside editable region" error

I have been searching the internet and any forum I can find relating to Dreamweaver and find it has been a comman problem for a lot of people but the solutions they got have not helped me. I created a template by following steps via a helpvid.net tutorial and the site looked very good for being basic enough but since last night when I try save the template it gives up the error "there is an error at line 8, column 47 (absolute position 789) of "file address": InstanceBeginEditable tag inside editable region." Now from what I have read on the forums it usually means there is a mispelling or something placed inside the region when it shouldn't be but there is only 50 odd lines on it and can't see any problem. When I view the files it gives the error about, there are duplications of the "begin editable region" a number of times but they shouldn't be there because they aren't on the template. Im also finding that before this error came up the pages looked fine when uploaded but now the footer height which was set to 20px is 200px when uploaded and I have checked all coding for it and checked the Divs but still see no error. I have uploaded my tempalete and some of the pages that its giving errors about to see if that helps, not sure if its best to just paste wall of coding so ill post links to the files and if code needs to be pasted here ill do so. http://dublinmoulding.com/ <- site im working on, it can be seen the footer is very big. Should be 20px height but inspect element shows its 200px - #wrapper #footer { color: #FFF; height: 200px; On the template it is #wrapper #footer { color: #FFF; text-align: center; margin: 0px; font-size: 18px; font-style: normal; font-weight: lighter; font-family: Arial, Helvetica, sans-serif; padding-top: 5px; padding-right: 0px; padding-bottom: 5px; padding-left: 0px; height: 20px; http://dublinmoulding.com/dreamweaver/temp1.dwt <- my tempalate The error is given up on every page created using the template
**Update** I edited the file names of some of the pages that I used the template on so now it shows the coding.
http://dublinmoulding.com/dreamweaver/index.html6 <- my index page
http://dublinmoulding.com/dreamweaver/about.html6 <-about page

No need for tricks. We can view source code directly from our browsers or with Inspect Element.
Like I said, I don't see any code errors in your Template or child pages.
If DW continues to display errors, the first thing to try is Deleting Corrupted Cache in DW
http://forums.adobe.com/thread/494811
If that doesn't help, try Restore Preferences
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
Nancy O.

CS6 Inserting table breaks editable region

In DW CS6 I am building out a site based on one template with three editable regions. I generally work in split view building PHP-MySQL sites such as the current one, and I have been building template-driven sites in Dreamweaver since 1998; but this problem has me stumped. Everything works fine until I insert a table into one of the editable regions. That region immediately becomes non-editable in design view (but I can edit in code view). It doesn't matter how I insert the table -- whether I paste code from another page where the table is being delivered, whether I use the DW Insert Table function, or hand-code from scratch. The result is the same -- I can no longer place a cursor in that editable region, in any design window.
I seem to remember from CS5 a similar situation with a workaround that included triple clicking somewhere, but I have not been able to find that in this forum or in my notes. Any suggestions?

The issue exists both at home and at the office. There may be minor differences. I am now at the office .
Mac OSX ver. 10.9.4
DW v. 12.0 Build 5861
xxxxxxxxxxxxxx
TEMPLATE CODE
xxxxxxxxxxxxxxx
<!doctype html>
<html>
<head>
<meta id="p7PM3" name="viewport" content="width=device-width">
<meta charset="utf-8">

<title>Advanced Reporting</title>

<link href="../3D/p7affinity/p7affinity-5.css" rel="stylesheet" type="text/css" media="all">
<link href="../3D/p7affinity/p7mobius-animate.css" rel="stylesheet" type="text/css" media="all">
<script type="text/javascript" src="../3D/p7ehc/p7EHCscripts.js"></script>
<link href='http://fonts.googleapis.com/css?family=Federo' rel='stylesheet' type='text/css'>
<link href='http://fonts.googleapis.com/css?family=Life+Savers' rel='stylesheet' type='text/css'>
<link href="../3D/p7dmm/p7pm3/p7PM3-01.css" rel="stylesheet" type="text/css" media="all">
<script type="text/javascript" src="../3D/p7dmm/p7pm3/p7PM3scripts.js"></script>


</head>
<body>
<div id="layout">
<div id="logo">
    <?php include('../3D/includes/logo_content.php'); ?>
</div>
<div id="top-navigation">
    <?php include('../3D/includes/primarynav.php'); ?>
</div>
<div id="content">
<div class="column-content border-bottom colored-black"> Lorem ipsum dolor sit amet, ne sea vocent scripta abhorreant. </div>

<div class="affinity-row">
    <div class="affinity-column percent70 reverse-float">
      <div class="column-content border-left p7ehc-1">
      <h1>Main section heading</h1>
      <p>Lorem ipsum dolor sit amet, </p>
      <h3>Coming up soon...</h3>
      <p>Lorem ipsum dolor sit amet, ne sea vocent </p>
      </div>
    </div>
    <div class="affinity-column percent30 reverse-float">
      <div class="column-content p7ehc-1">
      <p><img class="p7-animate zoom-out" src="../3D/art/mobius-art-04.jpg" width="520" height="713" alt=""></p>
      <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Quisque congue tristique eros. Nulla facilisi. Quisque sem mauris, ullamcorper ac, gravida id, mattis id, sapien. Nullam adipiscing enim dapibus felis.</p>
      </div>
    </div>
</div>
</div>
    <?php include('../3D/includes/footertext.php'); ?>
</div>
</body>
</html>
Will send child separately

(un)editable regions extension

Hello !
I'm currently trying to do an extension which would parse a
(JSF) DreamWeaver file, find a certain kind of tag and then make
all content nested into them uneditable.
Could anyone give me an hint ? Ideally, I would not use
templates, but I'm afraid I will have to. No problem.
The problem is that I would like to be as little intrusive as
possible regarding the page code : is there another way to proceed
than   ?
Another question : is there some kind of code like @@("")@@
which I could use ? Because this code is nice but I can't afford to
use nested templates : if I use it into a page, I want it to be
effective into that page, not into the one to which my page is a
template to.
I'm using DreamWeaver 8 & JavaScript.
Cheers,
TheGridOne

=____= I cannot believe that I am saying this, after writing ALL of that up, but thanks to "Dreamweaver CS5 for Dummies," I just learned that if you place: @@(" ")@@ within the Child/Nested Template's editable region that you DO NOT want passed down to your Child-Pages, it won't appear editable. Goodness knows why such an inconspicuous formula was the answer, but I guess whatever works. ...WHY WAS THIS INFORMATION SO DIFFICULT TO FIND?!?!?!?! @____@ Information on Nested Templates in general seems rather difficult to find, however, so I'm glad I figured this out /not ever a full hour/ after writing all this up and posting it. #__# ...At least my Child-Templates can work thoroughly now, though. So... Scenario FIXED. ^^
I only hope now that such information will appear helpful to anyone else hunting for this information via Google or other Search Engine in the future. And if there is anything at all that I am still officially missing, then do feel free to add it to the feed and let me know, because the last thing I need right now are more surprise difficulties to equally slow down the productivity of this massive project I've been working on... @___@ ..But so far things seem to be going good. ^^ So I can settle myself unbelievably grateful that there ended up being a solution to this ridiculousness after all.
Sincerely,
Miss Cat
[signature promo info removed by moderator]

Editable region in template not editable??

I'm trying to add a Spry Image Slideshow (basic) to several files in Dreamweaver CS5. I have set up templates, and in the child pages, when I try to insert the widget it just says: "Making this change would require changing code that is locked by a template or translator. The change will be discarded." I have a Spry menu already on the page (although it doesn't show up on my laptop but does on my desktops). What should I do? A sample page is already uploaded here: http://www.tomandlauriereese.com/bands/muzette/muzette.html. I'm trying to add the photos to Col1 (an editable region). Col2 allows me to add content, but Col1 won't. Actually, I can't add anything to Col3 either (it's set up as an iframe right now).
Please help! Let me know what other information you need; I'm new to this!
Thanks,
Laurie Reese, cellist

I'm not really piling on here, but I'm confident your extensive use of absolute positioning is going to sadly return to bite you on this very nice looking layout. Add some real-world content to one of those text regions, preview in the browser and start increasing the size of the text in the browser. You'll get an overflowing mess in a hurry.
I chose the doctype of xhtml 1.0 Transitional. I'm not sure which type is best for this type of page. I also tried html 4.0 Transitional, but still no luck.
A doctype only does two things: a) it informs a validator of how to validate the code on the page, and b) it informs the browsers whether to render the page in quirks more or standards mode. Because it's useful to be able to use validation as your first line of defense when encountering layout issues, you should therefore choose a doctype that is consistent with your skill and knowledge as a coder (as a first-order approximation). In your case, I'm pretty sure that would be HTML 4.01 Transitional. You can have DW do this for you by opening the template page and using FILE | Convert > HTML 4.01 Transitional. Be aware that this will only affect the content in NON-editable regions of your child pages as is expected with any template changes.
I did notice that the Head editable region is way underneath all the other code; it's at line 506; but there's nothing in there. Should I move the " to the top somewhere?
As long as that region is actually in a legal location between <head> and </head> it doesn't matter where it is. Since it is, then you can just leave it.
What should be in that region?
This is the region that allows you to add javascript behaviors to child pages, like image swaps, or show/hide divs, or even page-specific stylesheet/javascript links. Without it, you could not do that.
Where is it you are trying to add this widget? Which editable region?

Duplicate Editable Regions (DW,CS5)

Similar Messages

Maybe you are looking for