DW CS3 Remove editable regions

Hi
How does one go about removing an editable region in DW CS3?

Thanks David...it was rather a simple issue but for whatever reason my mind wasn't working and this had me stumped.
I have another template based question on the forum, once I get past this last issue, I think my troubles will be behind me. If you have time, please have a look.
Cheers!
Bob

Similar Messages

How to remove Editable region from nested template?

I'm trying to remove an editable region from a nested
template while retaining it in the parent template. DW doesn't want
to let me do this.
Example:
- I've created an overall template call ALLPAGES.DWT
- In it, there's an editable region called "related links".
- The "related links" will stay the same for all my main
pages (welcome, news, info, etc), so I'd like to create a nested
template called MAINPAGES.DWT where the field is locked.
So here's what I did; I started a new page from ALLPAGES.DWT
and then I created a template MAINPAGES.DWT from it. Now I want to
remove the editable region "related links". According to the DW
manual, I should be able to highlight the region and go to
Modify > Templates > Remove Template Markup, but that
option is greyed out!
Apparenlty the only way of removing the editable region is to
create a smaller editable region within it. But that's unnecessary
and sloppy. How can I remove the region entirely?

> This use of nested templates is very useful and very
simple and
> straightforward.
> It involves no additional overheads, and introduces no
reliability
> problems.
I really disagree with this.
> I cannot understand why Murray has such a bad attitude
to nested
> templates.
I spent quite a bit of time using them, tweaking them,
understanding them,
and watching the problems that others have had here on the
forum. My
compelling conclusion is that there is nothing you can do
with nested
templates that you cannot do more simply and with far less
trouble by using
other methods, some involving other kinds of template
regions, and some
involving simple use of Library items, or better, server-side
includes.
> I can only assume either that he had a bad experience on
the road to
> Damascus,
> after writing his definitive book on templates
I assure you, it's based on much more study and experience
than you have put
into it.
> "Templates are wicked and sinful! Don't play with them,
or you will go
> blind!"
This is not only unkind, it's completely erroneous. Far and
away, I am the
single most enthusiastic proponent for the use of templates
on these boards.
Perhaps a read of my book would help you rid yourself of your
attitude, too.
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
==================
"Clancy" <[email protected]> wrote in message
news:[email protected]...
> "Dodgeit" <[email protected]> wrote:
>
>>I'm trying to remove an editable region from a nested
template while
>>retaining
>>it in the parent template. DW doesn't want to let me
do this.
>>
>> Example:
>> - I've created an overall template call ALLPAGES.DWT
>> - In it, there's an editable region called "related
links".
>> - The "related links" will stay the same for all my
main pages (welcome,
>> news,
>>info, etc), so I'd like to create a nested template
called MAINPAGES.DWT
>>where
>>the field is locked.
>
> Very simple:
>
> Open allpages.dwt.
> Save as template, with name mainpages.dwt (I always do
this immediately so
> that
> if I do something stupid I don't corrupt the original
template).
> Insert the desired content into "related links".
> At the beginning of the content area of "related links"
insert the magic
> code
> @@("")@@
> This turns off the editable region, and there will be no
reference to it
> in
> pages derived from this template.
> Save the changes to mainpages.dwt
> Done!
>
> Have a look at
>
>
http://www.corybas.com/Technical/Nested.htm
> This is derived from my template techpage.dwt, which in
turn is ultimately
> derived from my template basicpage.dwt.
>
> Basicpage.dwt defines two editable regions 'title' and
'subtitle' at the
> top of
> the page. Techpage.dwt sets a fixed title for all my
technical pages, as
> follows:
>
> <p class="hdgtn" >@@("")@@Roger
> Riordan: Technical notes</p>
> <p class="hdgstn">Notes</p>
>
> In the page Nested.htm the references to 'title'
disappear, and the two
> lines
> appear as
>
> <p class="hdgtn" >Roger Riordan: Technical
notes</p>
> <p class="hdgstn">Nested
> Templates</p>
>
> This use of nested templates is very useful and very
simple and
> straightforward.
> It involves no additional overheads, and introduces no
reliability
> problems.
>
> I cannot understand why Murray has such a bad attitude
to nested
> templates. I
> can only assume either that he had a bad experience on
the road to
> Damascus,
> after writing his definitive book on templates, or that
it says simply:
>
> "Templates are wicked and sinful! Don't play with them,
or you will go
> blind!"
>
>
> Clancy

Remove editable region *and* propagate?

Hi all,
I have an editable region in a template which I would like to
make uneditable. I can remove it in the template, but the change
does not seem to propagate to the child pages. In other words, the
region is still editable on the child pages after I apply the
changed template. Is there a way to do this or am I outta luck
here?
Thanks!

Removing the editable region markup should certainly render
that region
uneditable in the child pages. Something is preventing that
from happening.
Can you show me the child page after removing the markup and
tell me which
region you are deleting?
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
==================
"idRatherBeOutside" <[email protected]>
wrote in message
news:e4e3s6$j23$[email protected]..
> Hi all,
>
> I have an editable region in a template which I would
like to make
> uneditable.
> I can remove it in the template, but the change does not
seem to propagate
> to
> the child pages. In other words, the region is still
editable on the
> child
> pages after I apply the changed template. Is there a way
to do this or am
> I
> outta luck here?
>
> Thanks!
>

Remove editable region

I am trying to remove an editable region on a template but
get a dialog box with inconsistent regions problems. I am afraid I
will mess things up if I don't know what to select from the menu.
Anyone know what to do here/?

Removing an editable region from a TEMPLATE page would not
general such.
Are you sure you have properly described what you are doing?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"sugar_d" <[email protected]> wrote in
message
news:gh9f0j$cps$[email protected]..
>I am trying to remove an editable region on a template
but get a dialog box
> with inconsistent regions problems. I am afraid I will
mess things up if I
> don't know what to select from the menu. Anyone know
what to do here/?
>
>
>

I can't remove Editable Region

I have multiple templates and I cannot remove and editable region...it won't allow me to do so through Modify>Templates>Remove Markup...it will not make that option available to me...Help
Learning

You need to make the change in the main template, not in a child page.

How to delete editable regions and template?

Hi everybody,
I posted this question earlier in the web discussions area, being unaware of a forum specific to Dreamweaver. Sorry for posting in two different places.
For the past week, I have been learning Dreamweaver CS4 from an online tutorial. I got to the place where I generated a template (index.dwt) from the main page (index.html) and created some editable regions on it. At that point, I realized that I had done all the steps by rote and did not actually absorb what I was doing. I wanted to delete the template in order to repeat the steps and gain a better understanding of the process. When I tried to delete the editable regions (modify-templates-remove editable regions), I was unable to do so because "remove editable regions" was greyed out. Nor was I able to delete the html code. I tried to delete the template itself, but when I did that, the index.html page retained those editable regions! Can anyone tell me if there is a way to get back to the place I was in before creating the template?
Thank you for any assistance.

All you need to do is detach the index.html file from the template. Then you can delete the template and start all over.
Go to the Modify menu --> Templates --> Detach from Template

How do I remove an extra editable region in the head of a specific page?

I have a single-template website. My template has the standard two editable regions in the head ("title" and "head"). Somehow, one of my pages ended up with three editable regions in the head - two named "head" as well as title. My template won't update this page because the editable regions don't match. How do I remove this extra editable region from the head of the page? I can't modify it on the page itself, of course, and I can't remove it by modifying the template because it's not part of the template.
Thanks in advance!

Your child page would not contain any editable regions if it wasn't attached to a Template. Perhaps you nested templates which is the wrong thing to do.
Go to Modify > Templates > Detach from Template.
Nancy O.

I have an Editable Region in a template and want to remove it

When I have an Editable Region in a template and want to
remove it, and from all child-pages, what to do[mx 2004] ? The
below code if is in logout.php how is get included in a file ?
I use:

but isset($_SESSION["email"] does not working .... well ?
[code]<?php
if (isset($_SESSION["email"])) {
?>
<link href="/css-styles.css" rel="stylesheet"
type="text/css"><body class="text_normal">
<span class="text_normal">LOGGED IN(<a
class="text_normal"
href="/php_files/logout.php">Customer-LogOut</a>)</span>
<?php
?><br />
<?php
if (isset($_SESSION["email-affiliates"])) {
?>
LOGGED IN(<a class="text_normal"
href="/php_files/affout.php">Affiliate-LogOut</a>)
<?php
?>
[/code]

Click in the editable region in the Template file. Right
click on the
mmeditable tag you see on the tag selection and choose Remove
Tag from the
menu. Save the Template.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"123polis123" <[email protected]> wrote in
message
news:gf7pu8$p69$[email protected]..
> When I have an Editable Region in a template and want to
remove it, and
> from
> all child-pages, what to do[mx 2004] ? The below code if
is in logout.php
> how
> is get included in a file ?
>
> I use:
> 
> but isset($_SESSION["email"] does not working .... well
>
> [code]<?php
> if (isset($_SESSION["email"])) {
> ?>
> <link href="/css-styles.css" rel="stylesheet"
type="text/css"><body
> class="text_normal">
> <span class="text_normal">LOGGED IN(<a
class="text_normal"
>
href="/php_files/logout.php">Customer-LogOut</a>)</span>
> <?php
> }
> ?><br />
> <?php
> if (isset($_SESSION["email-affiliates"])) {
> ?>
> LOGGED IN(<a class="text_normal"
>
href="/php_files/affout.php">Affiliate-LogOut</a>)
> <?php
> }
> ?>
> [/code]
>
>
>

Editable Regions Problem in CS3

I am working a set of pages based on the two column fixed with template.
4 Editable Regions.
Two Created by Dreamweaver
Two Created by me
Doc Title
Head
MainContent
Ad Area
Almost ALL of my additions are going into the Content Region. 80% of the time I have NO ISSUES
between Code View and Design View.
What is happing to me too many times now that it has become annoying......
I will make a simple code change in Code View, usually WELL WITHIN the editable region tags
and when I go to view what I did in Design View, I get an error box that says something like this.
You have made a code change in an area that is designated as uneditable.
If you wish to keep this change it will be lost the next time you update the template.
This could be a siple change like adding a bold to a piece of text.
A lot of times it happens whe I try to put a Container Div around some text.
It almost ALWAYS happens when I am trying to float something.
Is this a BUG. Is there a fix? I know I can't ignore it because I have seen what happens when I do that....
Please don't tell me to update to a more recent version unless that absolutely has the fix in it.
It cost me an arm to buy this product in the first place and if I had known how little I was gaining
I would have NEVER purchased it.I certainly don't want to spend any more unless it solves the issue.
The design view in CS3 STINKS! Design View was one of the reasons
I wanted the product in the first place. WYSIWYG. I was trying to upgrade away from years of using HotDog.
Two years of this now and I still find myself doing most of my design in Code View.
I don't TRUST Design View.
I do eventually publish to a copy without template marup but I need to code in the version that is still templated.
I do change the master template from time to time.
HELP!

Better than your helpless nagging would be that you share a link to your page.
... and your: Please don't tell me to update to a more recent version unless that absolutely has the fix in it. It's actually also not a very good attitude and (for me!) not a great motivation to help you. Ok, I have this program on the computer, even, but the reasons are to work here in the forum.
... and I quote from a thread here in the forum:
"It's not a word processor or WYSIWYG, never has been, but I think you're using those terms more broadly than the regulars in this forum use them. But if you're happy to use only Design View and let DW code then you'll get similar results to using DW8."

After inserting editable regions, DW CS3 tells me none exist...?

I am having muliple problems with templates on this particular project, that I have never seen before. I was going to break them into multiple
questions, per the instructions here at the forum, but all of these relate to the same template code, which I will post below, so I think it would be
more efficient to include the related questions in this thread.
Background
I created this template by first scraping the client's existing site, which is a dynamic CMS site, with HTTrack. Secondly, I opened the HTML file generated by that processs, and saved it as a template in my DW project, which automatically assigned it to the "Templates" folder, and is accessable via the "Assets" panel (usual stuff.)
The reason for starting with a scraped version of existing is that this project involves moving the site off of the CMS platform and into HTML/CMS, yet preserving essentially the same design.
1. The most obvious problem I have is that in the subject line: after adding a couple of editable regions to my template,
when I save/preview, an error message comes up saying "your template has no editable regions, do you want to proceed?"
2. In doing the save as template operation, I am prompted with "Update links?" and I do. When I open the template, all looks good in DW, however as soon as I do a preview, I get a completely raw html page with NO css styling, no images, no fonts, etc. Conversely, if I do the same step, yet choose not to update links when prompted, then I get a template that looks completely bare in DW (no styling, no images, etc.) yet looks fine when previewed...?
Additionally, one other thing I tried was doing the save as template, choosing not to update links, and then moving it out of the templates folder into the main project folder - Here, it both looks fine in DW, and previews, yet I am unable to use it as a template (does not appear in assets, cannot use "create new from" or "apply", etc.)
I have also tried changing from "site root" to "document" in terms of linking, yet nothing has worked. Every time I have created a template on other projects, all has just worked fine from the start, so I am really stumped here.
The project will have too many pages to not use a template for updates, so I am hopeful that I can figure out what is causing this. Following is my template 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 profile="http://gmpg.org/xfn/11">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

<title>Home | Records Management Center</title>
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
<base href="http://records-storage.biz/RMCAugusta/">
<meta name="robots" content="all" />
<meta name="description" content="records management center augusta's choice for data storage, records management, document shredding.">
<meta name="keywords" content="augusta, data, storage, records, management, document, shredding, center">

<link rel="stylesheet" type="text/css" href="../include/scripts/css/screen.css" />


<script language="JavaScript">

</script>
<script type="text/javascript" src="../include/scripts/jquery/jquery1.2.6.js"></script>
<link rel="stylesheet" type="text/css" href="../include/scripts/superfish/superfish.css" media="screen">
<script type="text/javascript" src="../include/scripts/superfish/superfish.js"></script>
<script type="text/javascript" src="../include/scripts/superfish/hoverIntent.js"></script>
<script type="text/javascript" src="../include/scripts/jquery/site.js"></script>
<script language="Javascript" src="../include/scripts/rotate.js"></script>
<link href="/RMCAugusta/common/wsaglobal.css" rel="stylesheet" type="text/css" />
</head>

<body>
<div id="container">
<div id="header">
<h1>
<a class="logo" href="../index.html" title="Home Page">
<img src="../images/RMC-logo.gif" alt="Home Page" /></a>
</h1>
<div id="supernav">
<a href="../index.html" title="Go Home">Home</a> |
<a href="#" title="FAQ">FAQ</a> |
<a href="../common/feedback_footerc73a.html?PAGE=355" title="Contact RMC">Contact Us</a> |
<a href="../common/contentff2a.html?PAGE=353" title="Client Login">Login</a> |
</div>
<div id="searchsite">
<form action="http://www.recordsmanagementcenter.com/common/textsearch-std.asp?PAGE=375" method="post" id="Search" title="Search">
<input type="text" name="i_search" class="searchbox" value="Search Site..."
onfocus="if (this.value == 'Search Site...') {this.value = '';}"
onblur="if (this.value == '') {this.value = 'Search Site...';}" />
<input type="submit" class="submit" alt="Submit" value="Search" />
</form>
<div class="clear"></div>
</div>
<div class="clear"></div>
</div>
<div id="topnav">
<ul id="menu" class="sf-menu">
     <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/contentd618.html?PAGE=350">About RMC</a>
       <ul >
        <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content9a68.html?PAGE=356">Customer Bill of Rights</a></li>
          <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content0864.html?PAGE=369">My Three Point Pledge</a></li>
          <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content1f72.html?PAGE=363">Testimonials</a></li>
          <li><a href="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/common/content3fb4.html?PAGE=364">Our Facility</a></li>
        <li><a href="#">Newsletter</a></li>
        <li><a href="#">Special Offer</a></li>
     </ul>
</li>
     <li><a href="#">Records Managment</a>
      <ul>
      <li><a href="#">Records Storage</a></li>
      <li><a href="#">File Storage</a></li>
      <li><a href="#">File Indexing</a></li>
      <li><a href="#">Storage & Delivery Process</a></li>
      <li><a href="#">Barcode Tracking </a></li>
      <li><a href="#">File Restoration</a></li>
      <li><a href="#">Dedicated Vault Storage</a></li>
      <li><a href="#">Supplies</a></li>
     </ul>
</li>
     <li><a href="#">Document Imaging Solutions</a>
      <ul >
       <li><a href="#">Service Bureau</a></li>
       <li><a href="#">Scan On Demand</a></li>
       <li><a href="#">Data Silo</a></li>
      </ul>
    </li>
    <li><a href="#">Shredding & Destruction</a>
     <ul >
       <li><a href="#">Shredding Process</a></li>
       <li><a href="#">Drop Off Shred</a></li>
       <li><a href="#">One Time Purges</a></li>
       <li><a href="#">Media Destruction</a></li>
       <li><a href="#">Collection Containers</a></li>
      </ul>
   </li>
    <li><a href="#">Data Backup</a>
     <ul >
       <li><a href="#">Tape Vaulting</a></li>
       <li><a href="#">Electronic Vaulting</a></li>
      </ul>
   </li>
   <li><a href="#">Info Management 101</a>
     <ul >
       <li><a href="#">Special Info Kit</a></li>
       <li><a href="#">Storage Options</a></li>
       <li><a href="#">How To Choose</a></li>
       <li><a href="#">Storage Tips</a></li>
       <li><a href="#">Retention Guide</a></li>
      </ul>
   </li>
   </ul>
    <div class="clear"></div>
</div>
<div id="slideshow">
<script language="JavaScript">
//new fadeshow(IMAGES_ARRAY_NAME, slideshow_width, slideshow_height, borderwidth, delay, pause (0=no, 1=yes), optionalRandomOrder)
new fadeshow(fadeimages, 632, 258, 0, 4000, 0)
</script>
</div>
<div id="page">
<div class="tophome">
<div class="bot">
<div id="contenthome">
<table border="0" cellpadding="0" cellspacing="5" width="100%">
     <tr>
          <td valign="top">
               <table border="0" cellpadding="0" cellspacing="0" width="100%">
                    <tr>
                         <td valign="top" width="">

<a name="1"></a>

<h1>Welcome to <b>Records Management Center</b></h1>
<table width="100%" border="0" cellpadding="0" cellspacing="0"><tr><td valign="top" align="Left" class="text">We know you have many options when it comes to storing your organization's records and information. You may choose to store them on-site in your own storeroom, in a mini-storage (self storage) unit, with a moving and storage company or with a full-service records management company like Records Management Center. There are, however, major differences not only in the storage options available, but in the companies that provide them as well. Please take some time to review our website and familiarize yourself with your records management options, so that you can make the choice that's right for your organization.</td>
</tr></table>
<table width="100%" border="0" cellpadding="0" cellspacing="0"><tr><td valign="top" align="Left" class="h2">About Us</td>
</tr></table>
<table width="100%" border="0" cellpadding="0" cellspacing="0"><tr><td valign="top" align="Left" class="text">Records Management Center was established in 1985 as a full-service records management company providing document storage, digital imaging, media storage and shredding services to the Central Savannah River Area.<br />
<br />
We protect businesses and their customers by securing their confidential information and helping them comply with HIPAA, GLB and FACTA, as well as all state and federal information management and destruction laws.</td>
</tr></table>

                         </td>
                    </tr>
               </table>          </td>
     </tr>
</table>
</div>
<div class="clear"></div>
<div id="specials">
<div class="top">
<div class="quote">
<a href="../common/feedback_footerc73a.html?PAGE=355" title="Get A Quote"> </a></div>
<div class="info">
<a href="../common/content371a.html?PAGE=373" title="Free Information Kit"> </a></div>
<div class="days">
<a href="../common/content371a.html?PAGE=373" title="30 Days of Free Shredding"> </a></div>
<div id="newsletter">
<h3>Sign up for our<br /><span class="caps">Free Newsletter</span></h3>
<form action="http://www.recordsmanagementcenter.com/common/feedback_footer.asp?PAGE=374" method="post" id="Search" title="Sign Up">
<input type="text" name="input_2" class="searchbox" value="Email Address"
onfocus="if (this.value == 'Email Address') {this.value = '';}"
onblur="if (this.value == '') {this.value = 'Email Address';}" />
<input name="Sign up" type="submit" class="submit" alt="Sign Up" value="Sign Up" />
</form>
<div class="clear"></div>
</div>
</div>
<div class="bot"> </div>
</div>
<div id="boxes">
<div class="records">
<a href="../common/content5697.html?PAGE=331" title="Records Management"> </a></div>
<div class="imaging">
<a href="../common/content9e28.html?PAGE=61" title="Digital Imaging"> </a></div>
<div class="storage">
<a href="../common/content7f9f.html?PAGE=333" title="Computer Media Storage"> </a></div>
<div class="shredding">
<a href="../common/content1cd1.html?PAGE=296" title="Secure Shredding"> </a></div>
<div class="clear"></div>
</div>
</div>
</div>
<div class="clear"></div>
</div>
<div id="footer">
<div id="links">
<a href="#">Terms and Conditions</a> |
<a href="#">Privacy</a></div>
<div id="copyright">
© 2009 Records Management Center.<br />
A Division of RBW Logistics Corporation<br />
Powered by <a href="http://www.powerserve.net/">PowerServe</a><br />
<a href="http://www.rbwlogistics.com/"><img src="../images/logo-footer.gif" /></a>
</div>
</div>
</div>
<script language="JavaScript" type="text/javascript" src="/NoIEActivate.js"></script><script src="file:///C|/Documents and Settings/sunni/My Documents/1-DelSurSEO/FlourishPress/www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-159577-28";
urchinTracker();
</script>

</body>

</html>

There are (or can be), of course, editable regions in the head of a document. Typically, around the <title></title> you will find 'space' to put links etc, and meta tags:

<title> Your title here </title>
<meta name="description" content="Description here." />
<meta name="keywords" content="keywords here " />
<meta name="robots" content="index,follow" />

Further down in this same document, I find:

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

</style>
<script src="../Scripts/swfobject_modified.js" type="text/javascript"></script>

showing a stylesheet link and an embedded style.
So it's not so much that you can't have editable areas in the head of the document, it's more that you can't overlap or improperly nest ANYTHING.
You can also (am I repeating myself?) make a tag's attributes editable. I use that feature most notably for applying different IDs to <body> tags for different neighborhoods in my sites. By applying different body IDs, I can control more specifically elements on those pages. But that's a conversation for another time!
Best,
Beth

Remove template region

I have established a small hierarchy of templates for a
DreamWeaver CS3 site. At the first level, one template region (1)
contains a table with 9 cells each containing a rollover image.
New template pages (x 6) are generated from this template
page. The images in (1) above are changed on each of these, so that
they remain uneditable in all resulting pages. But when I press the
Template region tab, Modify > Templates > (Remove template
markup) is greyed out.
This is what the help site says I should do. What have I done
wrong, and is there another way to solve the problem?

Do not use nested templates.
Your single template will have editable regions placed so
that on pages that
require section-specific navigation you can add a navigation
element
accordingly.
For example -
1. Make a Library item that contains JUST your navigation for
a specific
section, or
2. Make a server-side include that contains the same
On a child page, you have an editable region available for
the
section-specific navigation because of the way you have built
the template.
So, you can place either item #1 or item #2 as needed (use
DW's F1 help to
read about both - I prefer the latter).
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"bryan o" <[email protected]> wrote in
message
news:foc37b$1ig$[email protected]..
> That sounds good. I suppose it is just the navigation
that changes. At
> level 2
> (category) there is a thumbnail mosaic (navigation)
which has different
> content
> from category to category, but identical within each
category, and must be
> easily updateable as new work is published. Will read up
more about this:
> <...editable regions strategically placed so that you
could drop in
> category-specific navigation 'pieces'?> ... but if
you could give me a
> pointer
> or concrete path to follow it might help ? Dw beginner,
remember! I
> wonder if
> that was similar to what I was doing originally, but
when I dropped in the
> category-specific navigation piece and tried to make it
a new template
> just for
> that category, I could not undo the editable region for
that navigation
> piece.
> Thanks again
>

Modifying a template resulted in all child pages with repeating editable regions - Help !

Good morning,
I have recently been appointed to update a website designed in Dreamweaver by an employee who is no longer here. I have read books on the software and practiced an insane amount which permitted me to update child pages, links, documents etc... however:
I was asked to add a new button to an "non-editable" region of a template. Trying to do so resulted in a massive mess (with massive anxiety).
Even thou the new template had all the same text and editable regions, all my pages look completely different from the template itself. The editable regions appears 2-3 times in different locations ex: Header is showed on the bottom, top etc... and the Editable region titles (EditableRegion1 etc...) repeat themselves as well.
I really need help and not sure what to do, I have tried everything and I am only making it worse and worse. All I want/need is for all my html pages created with this template, match the template.
Please note that this site is local, not online.
Since I noticed on other threads that the code is needed; here it 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" />
<title>QMS: AFM</title>
<style type="text/css">

</style>
<link href="file:///U|/AFM/Dreamweaver/Left sidebar.css" rel="stylesheet" type="text/css" />
</head>
<body link="#006699" class="twoColElsLtHdr">
<div id="container">
<div id="header">
    <h1><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/pwgsc-e.gif" width="364" height="33" align="left" alt="wordmark" /><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/wordmark_canada.gif" width="83" height="21" align="right" alt="wordmark2" /></h1>
    <p> </p>
    <p><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/AFM QMS banner.jpg" width="709" height="80" alt="banner" border="0"/><a href="mailto:[email protected]"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Contactus-e.JPG" width="110" height="21" alt="contactus-e" border="0" /></a><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/French-e.JPG" width="115" height="21" alt="french-e" border="0" /> <a href="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Continual Improvement/QMSTeamMembers-e.html"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Help-e.JPG" width="115" height="21" alt="help-e" border="0" /> <img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Search-e.JPG" width="115" height="21" alt="search-e" border="0" /></a><a href="http://source.tpsgc-pwgsc.gc.ca"><img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/thesource.jpg" width="120" height="21" alt="TheSource" border="0" /> <img src="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/Graphics/menubar/Home-e.jpg" width="104" height="21" alt="home-e" border="0" /></a></p>
    <p> </p>
</div>
<div class="twoColElsLtHdr" id="sidebar1">
    <p><a href="../QMS HOME/QMSHome-e.html"><strong>QMS Home</strong></a></p>
    <hr />
    <p><a href="../ABOUTAFM/AboutAFM-e.html"><strong>About AFM</strong></a></p>
<hr />
<p><a href="../AdminProcedures/AdminProcedure-e.html"><strong>Administrative Procedures</strong></a></p>
<hr />
<p><a href="../BusinessUnits/BusinessUnits-e.html"><strong>Business Units</strong></a></p>
<hr />
<p><a href="../POINTSOFINTEREST/pointsofinterest-e.html"><strong>Points Of Interest</strong></a></p>
<hr />
<p><a href="../Achievements/Achievements-e.html"><strong>Achievements</strong></a></p>
<hr />
<p><strong><a href="../MeasuringPerformance/measuringperformance-e.html">Measuring Performance</a></strong></p>
<hr />
<p><a href="../References/references-e.html"><strong>References</strong></a></p>
<hr />
<p><a href="file:///P|/RPS/AFMS/Quality Management System/QMS Site/HTML/ContinualImprovement-e.html"><strong>Continual Improvement</strong> </a></p>
</div>
<div id="mainContent">
    <h2>Header</h2>
    <p>Paragraph</p>
    <h1>Sub Header </h1>
    <p> </p>
    <h1> </h1>
    <h2> </h2>
    <h1> </h1>
    <p> </p>
    <h2> </h2>
    
</div>

       <br class="clearfloat" />
</p>
<div id="footer">
    <hr width="100%" size="8" noshade="noshade" color="#006666" id="color="069"" colour="#069"/>
    <p><strong>Maintainted by: ASQM </strong></p>
    <p><strong>Date Modified: 2013-03-25</strong></p>
    
</div>
<script type="text/javascript">

</script>
</h3>
    
</h3>
</div>
<script type="text/javascript">

</script>
</body>
</html>

I am not suprised, the previous employee tried to recreate the English version of the site in another folder structure and did not change all links and was still using a template in the wrong location.
I think I created the mess by trying to modify the existing template's non-editable region in order to add a new button. When trying to update all the pages, the fiasco started.
Do you think the best option would be to create a new template in the correct folder structure and apply it? Would it fix the current pages or will I have to fix them all manualy on by one?
I understand it is difficult to deal with a newbie of my magnitude and thanks again.

Can't Delete Non-Editable Region in Template?

Well, I can in existing templates but if I create a new one from an existing page using "Save as Template", when I try to delete a non-editable region in the template, DW won't let me. I don't know why. Aaaargh!
It's my understanding I should be able to edit anything in a template. I've tried existing DW and restarting. I've tried using other pages as a basis for the template. Every template I create won't let me delete non-editable regions. I'm highlighting the non-editable region and pressing the delete key. I can't delete.

burro_mail wrote:
Not sure DW is doing what you describe...
But I am certain you could remove the region in code view.
Even if you are a WYSIWYG-er and not a big code-head, it should be pretty easy to remove the region markers and everything between them...
Trust me, it is. I'm wondering if the problem is associated with the fact that the source page that I saved as a template was based on a template? I just noticed that this new template refers to another template. I'm thinking that means the other template is controlling what I'm trying to do in the current template.
That's it. I just tried saving a template under a different name (still retaining the correct template file extension) but did not do the save as template. Now I can completely edit that template. So you if you save a page that is controled by a template, as a template, that new template is controlled by the previous template.
I've got a headache now.

Can't edit 2nd editable region

Hi,
I have a template which uses CSS and DIVs. It has 2 editable
regions, each within a DIV.
When I open a document based on this template, for some
reason only the first editable region is editable. The only way I
can edit the second is to turn of styles or go into code view.
Any ideas why?

> That's just being picky.
> It makes no difference whether it is absolute or
relative - it doesn't
> work
> either way!
Well, for it to be a layer, it has to be absolutely
positioned, and the
difference in behavior between the two (absolute vs.
relative) is certainly
NOT picky.
Remove the overflow:auto style on the div#main container, and
you'll be able
to edit it in Design view.
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
==================
"mrdebauchery" <[email protected]> wrote in
message
news:[email protected]...
> That's just being picky.
> It makes no difference whether it is absolute or
relative - it doesn't
> work
> either way!
>
> Code attached, with crap cut out.
>
>
> <!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"
lang="en-gb">
> <head>
> <meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
> 
> <title>Title</title>
> 
> <style>
> body,td,th {
> font-family: Times New Roman, Times, serif;
> font-size: 16px;
> color: #000000;
> line-height: 105%;
> }
> body {
> background-color: #FFFFFF;
> margin-left: 0px;
> margin-top: 0px;
> margin-right: 0px;
> margin-bottom: 0px;
> }
> a:link {
> color: #0066CC;
> }
> a:visited {
> color: #0066CC;
> }
> a:hover {
> color: #006699;
> }
> a:active {
> color: #006699;
> }
> h1, h2, h3, h4, p {
> padding: 0px 0px 20px 0px;
> margin: 0px;
> }
> h1 {
> font-size: 24px;
> color: #4376BD;
> }
> h2 {
> font-size: 20px;
> color: #4376BD;
> }
> h3 {
> font-size: 16px;
> color: #4376BD;
> }
> h4 {
> font-size: 14px;
> }
>
> #container {
> width:760px;
> margin: auto;
> overflow:visible;
> }
>
> #topbar {
> position:relative;
> width:760px;
> height:104px;
> background-image: url(images/topbar.jpg);
> background-repeat: no-repeat;
> overflow: hidden;
> }
> #title {
> float: left;
> width: 325px;
> z-index: 2;
> }
> #pics {
> float: right;
> z-index: 2;
> }
> #pics img {
> margin: 4px 10px 4px 0px;
> border: #ffffff 1px solid;
> }
> #middle {
> position:relative;
> width:754px;
> overflow: auto;
> border-right: #006699 3px solid;
> border-left: #006699 3px solid;
> min-height:489px;
> background:url(images/lines.gif) repeat-y;
> }
>
> #menu {
> position:relative;
> width:194px;
> min-height:465px;
> float: left;
> border-right: #006699 3px solid;
> padding: 15px 0px 0px 0px;
> text-align: center;
> overflow: auto;
> }
>
> #links {
> width: 134px;
> height: 320px;
> border: #0276C0 1px solid;
> background-color: #DCF4F8;
> margin: 30px auto 15px auto;
> text-align: center;
> color: #0276C0;
> font-size: 18px;
> padding: 0px 6px 0px 6px;
> }
>
> #links ul {
> list-style: none;
> margin: 0px;
> padding: 0px;
> }
>
> #links ul li {
> padding: 29px 0px;
> margin: 0px;
> }
>
> #links ul li a {
> text-decoration: none;
> }
>
> #main {
> position:relative;
> width:512px;
> min-height:450px;
> float: left;
> overflow: auto;
> padding: 25px 15px 15px 30px;
> text-align: left;
> line-height: 105%;
> }
>
> #botbar {
> position:relative;
> width:760px;
> height:14px;
> background-image: url(images/botbar.jpg);
> background-repeat: no-repeat;
> overflow: hidden;
> }
> .small {
> font-size: 10px;
> padding: 0px 0px 5px 0px;
> line-height: 12px;
> }
>
> </style>
> </head>
> <body>
> <div id="container">
> <div id="topbar">
> <div id="title"><img
> width="325"
> height="104" /></div>
> <div id="pics"><img width="66"
> height="89" /><img width="66" height="89"
/><img width="66" height="89"
> /><img
> width="66" height="89" /></div>
> </div>
> <div id="middle">
> <div id="menu"> <img width="190" height="85"
/>
> <div id="links">
> <ul>
> <li> </li>
> <li> </li>
> <li> </li>
> <li> </li>
> </ul>
> </div>
> <p class="small"> </p>
> </div>
> <div id="main"> 
> <h1>Heading 1</h1>
> <p>Paragraph</p>
> <h2>Heading 2</h2>
> <p>Paragraph</p>
> <h3>Heading 3</h3>
> <p>Paragraph</p>
> <p>Paragraph</p>
>  </div>
> </div>
> <div id="botbar"> </div>
> <p> </p>
> </div>
> </body>
> </html>
>

Spry tool tip does not work in template or child pages within an editable region. Why not?

Ok. so I am getting pretty frustrated. I take the time to learn how to use CSS and to create a template page for a Contractor Site (www.ContractorInsurance.net). The idea is to create a page that I can use for different classes of Contractors...right?
Then I get all happy about being able to insert ToolTip onto pages to help the user. Great!
LIfe to turn to Sorrow after nearly five hours of searching for a "eeking" answer.
So what good does it do to have an Editable region to update if we cannot have the flexibility to insert a tool tip on child pages? Ok so the fast solution is to what... Have a question mark image, insert another apDiv, name it toolTip_Not and provide it with a show=hide behavior?
RRRRRrrr...
This really sucks not being able to find a solution within a reasonable amount of time.

I have tried thank you. However...it is still not working.
www.ContractorInsurance.net/course_of_construction.php
The error message is "Making this change would require code that is locked by a template translator"
Re: Spry tool tip does not work in template or child pages within an editable region. Why not?
created by altruistic gramps in Spry Framework for Ajax - View the full discussion
If you have a look at the following simple document with a tooltipTooltip trigger goes here.
Tooltip content goes here.
you will notice that a couple of lines have been placed in the HEAD section of the document. When using DW templates, the HEAD section is usually not editable, hence the error mesaage. By default, your template should have an editable region in it just before the closing tag. It looks like this:  Dreamweaver should be able to find that editable region and insert the
<script> tag there automatically. Because you don't have an editable region like that in the <head>, open the master template, and paste the code above just before the closing </head>
tag. Gramps
Edited to remove personal data

DW CS3 Remove editable regions

Similar Messages

Maybe you are looking for