Editable Region - Head

I have been working with templates for quite some time now
but have really dove in or created ones that are too complex. I
have a situation now where I need to ad some layers to a specific
page created from a template. DW is not letting me giving me the
error:
quote:
"Making this change would require changing the code that is
locke d by a template or translator. The change will be discarded."
If I go back to the template itself I see code for the head
like this:
quote:
<head>


<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />

<title>Untitled Document</title>

<link href="../style/main.css" rel="stylesheet"
type="text/css" />
<link rel="stylesheet" href="../p7tm/p7tmbasic.css"
type="text/css" />
<script type="text/JavaScript">

</script>
<script type="text/javascript"
src="../p7tm/p7tmscripts_mod.js"></script>
</head>
What do I need to do so that the page generated from a
template will let me put in a layer on that page?
Thanks you,
Houston

Here's the problem with layers in template child pages, and a
simple
solution.
When you DRAG a layer onto the page in DW (this means you
click on the layer
icon in the Insert Toolbar and drag the layer on the page),
DW wants to put
the code for that layer immediately under the body tag, e.g.,
BEFORE DRAG -
<body...>
<table>
AFTER DRAG -
<body ...>
<div id="foo" style="position:absolute; ...>LAYER
STUFF</div>
<table>
In a template child page, this region is usually not part of
your editable
region, and so the layer's code is rejected by the template
engine. This is
a bad thing.
If instead of dragging the layer onto the page, you use
INSERT | Layer, that
should work provided your cursor is in an editable region,
but since
editable regions are usually within tables or other layers,
you have just
broken one of the rules listed above. This is also a bad
thing.
THE SOLUTION -
Open your template page in DW, and create a special place
where it is SAFE
to put your layers. In code view, find this -
</body>
and click so that your cursor insertion point is just to the
left of
</body>.
Now, use INSERT | Template Objects > Editable Region, and
name this region
"Layer Pad" or something like that.
When you save your template page, all your child pages will
now have the
LayerPad editable region on them.
THE BIG FINISH -
On any child page where you need a layer, just click in this
editable
region, and use INSERT | Layer. Bada bing, bada boom.
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
==================
"htown" <[email protected]> wrote in message
news:[email protected]...
>I have been working with templates for quite some time
now but have really
>dove
> in or created ones that are too complex. I have a
situation now where I
> need to
> ad some layers to a specific page created from a
template. DW is not
> letting me
> giving me the error:
>
"Making this
change would require changing the code that is locke d by
> a
> template or translator. The change will be
discarded."
>
> If I go back to the template itself I see code for the
head like this:
>
>
<head>
> 
>
> 
> <meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
> 
> <title>Untitled Document</title>
> 
>
> <link href="../style/main.css" rel="stylesheet"
type="text/css" />
> <link rel="stylesheet" href="../p7tm/p7tmbasic.css"
type="text/css" />
> <script type="text/JavaScript">
> 
> </script>
> <script type="text/javascript"
src="../p7tm/p7tmscripts_mod.js"></script>
>
> </head>
>
>
> What do I need to do so that the page generated from a
template will let
> me
> put in a layer on that page?
>
> Thanks you,
> Houston
>

Similar Messages

Editable regions in child page

Hi all.
Dreamweaver 8.
I have a template with two editable regions, Header and Body.
I have a new page, and I want to apply the template.
I am prompted to move the content to the new regions. Is my
new child page supposed to have editable regions with the same
name? If I try to do this, I am prompted to create a new template.
If I apply the template and move all of my new content to the
'body' region, it all disappears. If I move all of it to the Header
region, it is all there. I've tried every combination and only the
one works. I've seen a lot of discussion about having the regions
named in the child page, but don't understand that bit yet.
Ty in advance.

> Layers and layer content are
> also treated as separate elements
Not necessarily.

<div id="layer1">Contents</div>

This treats the layer AND its contents as editable.
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
==================
"Virginia Oh My" <[email protected]> wrote
in message
news:[email protected]...
> For others' reference, this is what I've found out
digging around on the
> net
> some more.
>
> "You can make an entire table or an individual table
cell editable, but
> you
> can't make multiple cells editable all at once, unless
you have merged
> them
> first. You have to select each cell one at a time if you
want to make some
> of
> the cells in a table editable, but not others. Layers
and layer content
> are
> also treated as separate elements, but either can be
marked as editable.
> Making
> a layer editable enables you to change the position of
that layer. Making
> layer
> content editable means that you can change the content
of the layer, such
> as
> the text or image in the layer."
>
> Nesting an editable table seems to the be the answer.
I'm off to redo and
> retry.
>
> Thanks, all.
>
> Virginia
>
>
quote:
Originally posted by:
Virginia Oh My
> Thanks, I've tried this method. I have an editable table
cell. I can add
> new
> cells (rows and columns), but I cannot adjust the width
and height .
> They're
> locked, even though they are in the editable region.
>
> Virginia
>
>
quote:
Originally posted by:
Newsgroup User
> It's not a good idea to apply templates to pages with
existing content,
> for
> this very reason. Can you use a method instead where you
spawn a new
> child
> page from the template, copy/paste content into it, and
then save it over
> the existing page? Then you can put the content exactly
where you want.
>
> --
> 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
> ==================
>
>
> "Virginia Oh My" <[email protected]>
wrote in message
> news:[email protected]...
> > Hi all.
> > Dreamweaver 8.
> > I have a template with two editable regions, Header
and Body. I have a
> > new
> > page, and I want to apply the template.
> > I am prompted to move the content to the new
regions. Is my new child
> > page
> > supposed to have editable regions with the same
name? If I try to do
> > this,
> > I am
> > prompted to create a new template.
> >
> > If I apply the template and move all of my new
content to the 'body'
> > region,
> > it all disappears. If I move all of it to the
Header region, it is all
> > there.
> > I've tried every combination and only the one
works. I've seen a lot of
> > discussion about having the regions named in the
child page, but don't
> > understand that bit yet.
> >
> > Ty in advance.
> >
> >
>
>
>
>
>
>
>
>

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.

Optional editable regions in head

I'm trying to create a master template that will enable me to
include or not include cross-fading photographs in pages based on
that template.
I know that with DW8 I can insert an editable region in the
<head> (ie for description, keywords).
I know that with DW8 I can insert an optional region in the
<body> to show/hide content.
But can I insert an optional editable region in the
<head>?
I want to have the option of including a javascript file in a
<script> tag in the <head> of pages created from the
template and if I exercise the option to include it in the
<head>, I also want to be able to edit and change the name of
the javascript file.
All the help I've seen only talks about optional regions in
the <body>.
Do I use optional editable regions for this, or do it some
other way?
Urgent help appreciated - I'm stuck!
DW8 | XHTML | CSS

> But can I insert an optional editable region in the
<head>?
Not by way of the DW user interface, no.
But if you have a parameter called optionJS, with a type of
URL, and a
default value of "" (i.e., null), you could have this in your
template
document's head -
@@(optionJS==""?'':'<script src="'+optionJS+'"
type="text/javascript"></script>')@@
Then in each child page, as long as you leave the parameter
alone, no script
tag is written to the head. But to get the script tag, you
would just use
MODIFY | Template Properties, select the optionJS parameter,
and browse to
and select the desired script file, and it'll be there....
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
==================
"Digihound" <[email protected]> wrote in
message
news:[email protected]...
> I'm trying to create a master template that will enable
me to include or
> not
> include cross-fading photographs in pages based on that
template.
>
> I know that with DW8 I can insert an editable region in
the <head> (ie for
> description, keywords).
>
> I know that with DW8 I can insert an optional region in
the <body> to
> show/hide content.
>
> But can I insert an optional editable region in the
<head>?
>
> I want to have the option of including a javascript file
in a <script> tag
> in
> the <head> of pages created from the template and
if I exercise the option
> to
> include it in the <head>, I also want to be able
to edit and change the
> name of
> the javascript file.
>
> All the help I've seen only talks about optional regions
in the <body>.
>
> Do I use optional editable regions for this, or do it
some other way?
>
> Urgent help appreciated - I'm stuck!
>
> DW8 | XHTML | CSS
>
>

Can't manually add editable regions to head in template

When I created my main template in Dreamweaver CS6 for my website, I had copied most of the page code from another layout I already had, including the head code. I did not realize there were already editable regions built into the head section of the Dreamweaver template and deleted them when I pasted my previous code without adding new ones. I then added an editable region to the body and started created pages using the template.
Everything works well and updates properly when I make changes to the template but now that I am trying to add those editable regions back to the head section so I can change the page title (and possibly add more responsive code), it doesn't work. I copied and pasted the following code into my template file in Dreamweaver and it saves in the template telling me it's updating the related pages, but when I open those individual pages in Dreamweaver, the code isn't there and those regions are not editable; only the original editable region I created in the body exists and works properly. Everything else continues to work perfectly.
Here is the code I pasted into the head around the <title> tag:

<title>Collings Document Database</title>

And here is the code I pasted into the head just before the </head> tag:


</head>
Any help would be appreciated. From everything I've read on these forums after searching, it sounds like pasting that code should work but I continue to get the results mentioned. Thank you.

Thanks for the response. I've run the template code through the validator and the following two errors are the only ones that showed up. I don't see how either of these would cause this issue. Thoughts?
Line 5, Column 53: Bad value X-UA-Compatible for attribute http-equiv on element meta.
<meta http-equiv="X-UA-Compatible" content="IE=Edge">
✉
Line 27, Column 127: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images. …gs_guitars_stroke_clear.png" width="184" height="81" class="scalable"> </div>

Error adding editable region in nested template Header

I have a base template for the website (establishing basic
menus), and a secondary template using that base template, which
establishes a common table layout for one part of the site. Having
created the PHP to drive the page, I need to lock down that
secondary nested region - otherwise any edit I make to my secondary
"table-defining" template is not passed through
to the final pages using the secondary template. I have
successfully created a secondary editable region in each part of
the <body> area, and sure enough, it locks down text
outside the secondary editable region just as DW help says it
should. So far so good.
Now the problem - I cannot create a region inside the
<head> editable region to lock down that region too.
Normally one would want keywords and so on to be variable from page
to page, but as I am filling variable keywords from a database, it
makes sense to lock down the <head> too. Does anyone
know why that generates an error "cannot create an
optional region here"? Is there anything that can be done
about it?

Posts are hard to read when they are all crammed together
like yours. Try
making some paragraphs!
Nevertheless, I think I understand what you are saying., but
honestly, I
just wouldn't do it that way. Anymore, my templates are just
one editable
region in the body, and a bunch of server-side includes. I
find nested
templates much too complex, and troublesome to work with, and
have really
never found a scenario where I could do things with them that
I could not do
more easily with other methods.
> However, I have an Editable
> region with the HTML Head area, and DW does not permit
me to add a
> 'secondary-template Editable Region' within it to lock
it down.
Is it only you working on the site? Who are you trying to
'lock down'? If
it's only you, I'd forget about this. Invariably the things
like this that
you think are a good idea come back later to bite you.
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
==================
"suddensurprise" <[email protected]> wrote
in message
news:[email protected]...
> Murray 'ACE' wanted to understand why I am using nested
templates.
>
Primary
> Template or 'base layout' I have a primary template
which establishes
> the
> top, left and bottom borders for the site. These contain
Spry menus - if
> I
> change the menu on the primary template, all pages will
be updated. The
> primary template has a 'work area box' which is where
the page content
> goes for
> each different page.
Secondary or 'nested' template Next I have a
> secondary template, or nested template. It starts with
the primary
> template
> but this time the 'work area box' is set up with a
product table and
> various
> fixed column headings. The table is filled from
different database
> records
> using PHP and MySQL. Therefore the secondary or 'nested'
template
> establishes
> a common format for the product table. For example, a
change to a heading
> in
> the secondary template is updated into all pages using
it. And to
> reiterate, a
> change to the Spry menu bar on the primary template will
update the
> secondary
> template and all pages created from that template.
Similarly, I have
> several
> other secondary templates, all created from the primary
template, all
> setting
> standard sections of the website so that multiple pages
can be updated at
> once
> via a single template change.
Note: the code in the secondary
> template
> needs to be 'locked' so that edits within it are passed
on to its slave
> pages.
> This is done by creating an empty Editable region at the
beginning of the
> 'work
> area box' I talked about.
Other Approaches? If anyone knows a
> better
> way of enabling site edits to be passed consistently
down into different
> standard-section blocks of the website, I would welcome
your input.
>
The
> Problem Now to reiterate the problem with which I
started this thread.
> In
> a secondary template it works fine creating a second
Editable Region
> within the
> Body of the HTML document - the rest of the code in that
'primary template
> editable region' is now locked out as is required.
However, I have an
> Editable
> region with the HTML Head area, and DW does not permit
me to add a
> 'secondary-template Editable Region' within it to lock
it down. I am
> wondering
> if anyone in the Community knows why or can suggest a
solution. Regards
> Richard
>

Template editable regions in head

Murray - as you always seem to answer questions on Templates:
I'm troubleshooting a site for a friend who does not frequent
this
forum - they have a couple of editable regions in the
<head> of the
file - used for some Javascript and also the page title.
Now I know that a properly formatted template has:
separate editable region named name="doctitle" - er for the
title and
a second editable region named name="head" for other things.
Does having

in the <head> matter - affect the functionality of Dw
??? - I know of
course that in wouldn't matter as far as the server is
concerned.
many thanks
~Malcolm~*...
~*

On Sat, 12 Jul 2008 10:11:24 -0400, Alan
<[email protected]> wrote:
>
>
>> Does having
>> 
>>
>> in the <head> matter
>
>It's fine.
>
>As long as:
>none of the editable regions are nested. Each needs to be
closed before the
>next editable region.
>
>And the head and body tags cannot be inside of an
editable comment tag.
>
>More likely- If the person is using 12+ editable regions
in a template file
>and leaving them with the default naming of EditRegion12
they need to step
>back and think about the whole process
Thanks Alan - I did think that would be the case - even if
not what I
would do.
No - not 12 editable regions - no idea how that happened - -
they only
have three - two in the head and 1 in the body.
I long ago moved to Dw - and details are hazy - but when I
did a
refresh of a site a couple of years ago - I created a brand
new single
template using File | New | Blank Template - so all
superfluous
nonsense I had generated in the migration from Frontpage was
eradicated - and unexplained program crashes became a thing
of the
past.
thanks again
~Malcolm~*...
~*

Templates - editable region in head

I've got code that I would like to make a template, but it's
in the head tag. I cann't make any portion of this an editable
region. Also, any pages generated from the template don't allow me
to edit anything in the head area. So if I want to have only a few
items differ in the head area for several similar pages, does this
mean I cann't use templates? Is there another way to do this?
Maybe I could just use a bunch of server side includes and
abondon templates butr this would inciate to me a serious design
limit in templates.
Here is my code in the head area that I'm trying to use as a
template with an editable region. The margin-right, margin-left
would have unique values for each page. Also the line "a.slidea
{background:url(images/cats/sidney-small.jpg);}" would be unique
for each page.
Thanks
a.gallery, a.gallery:visited {
display:inline;
color:#000;
text-decoration:none;
border:1px solid #000;
width:75px;
height:75px;
float:left;
position:relative;
cursor:default;
margin-top: 21px;
margin-right: 60px;
margin-bottom: 21px;
margin-left: 60px;
a.slidea {background:url(images/cats/sidney-small.jpg);}
a.slideb {background:url(images/cats/sidney-small.jpg);}
a.slidec {background:url(images/cats/sidney-small.jpg);}
a.slided {background:url(images/cats/sidney-small.jpg);}
a.slidee {background:url(images/cats/sidney-small.jpg);}
a.slidef {background:url(images/cats/sidney-small.jpg);}
a.slideg {background:url(images/cats/sidney-small.jpg);}
a.slideh {background:url(images/cats/sidney-small.jpg);}
a.slidei {background:url(images/cats/sidney-small.jpg);}
a.slidej {background:url(images/cats/sidney-small.jpg);}

This is the sign of an improperly made template.
Do this -
Create a new page (Basic HTML).
Use FILE | Save as Template....
Look at the code in the head region of the page, particularly
the editable
region around the <title> tag, and the other editable
region in the head
called "head".
Make your template file look like that.
Always use FILE | Save as Template when you create your
templates and you
won't have this problem again.
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
==================
"brucew6char" <[email protected]> wrote in
message
news:[email protected]...
> I've got code that I would like to make a template, but
it's in the head
> tag. I
> cann't make any portion of this an editable region.
Also, any pages
> generated
> from the template don't allow me to edit anything in the
head area. So if
> I
> want to have only a few items differ in the head area
for several similar
> pages, does this mean I cann't use templates? Is there
another way to do
> this?
>
> Maybe I could just use a bunch of server side includes
and abondon
> templates
> butr this would inciate to me a serious design limit in
templates.
>
> Here is my code in the head area that I'm trying to use
as a template with
> an
> editable region. The margin-right, margin-left would
have unique values
> for
> each page. Also the line "a.slidea
> {background:url(images/cats/sidney-small.jpg);}" would
be unique for each
> page.
>
> Thanks
>
>
>
> a.gallery, a.gallery:visited {
> display:inline;
> color:#000;
> text-decoration:none;
> border:1px solid #000;
> width:75px;
> height:75px;
> float:left;
> position:relative;
> cursor:default;
> margin-top: 21px;
> margin-right: 60px;
> margin-bottom: 21px;
> margin-left: 60px;
> }
>
> a.slidea {background:url(images/cats/sidney-small.jpg);}
> a.slideb {background:url(images/cats/sidney-small.jpg);}
> a.slidec {background:url(images/cats/sidney-small.jpg);}
> a.slided {background:url(images/cats/sidney-small.jpg);}
> a.slidee {background:url(images/cats/sidney-small.jpg);}
> a.slidef {background:url(images/cats/sidney-small.jpg);}
> a.slideg {background:url(images/cats/sidney-small.jpg);}
> a.slideh {background:url(images/cats/sidney-small.jpg);}
> a.slidei {background:url(images/cats/sidney-small.jpg);}
> a.slidej {background:url(images/cats/sidney-small.jpg);}
>
>
>
>

How do I make head section an editable region?

I have a main template with header, spry menu, main content(editable region) and footer.
I create new page from template, but it will not let me edit the head section to add a spry accordian. I need to paste the external link to css for the accordian in the head section, but DW wont let me touch the head section. I tryed to make the "head" an editable region, but that did not work.
Thanks for any insight...
Kevin

If you are using a recent version of Dreamweaver, there should be an editable section in the head of the document just before the closing head tag. It looks like this:


</head>
Insert the keywords, description, links to external files between the Template comments.
If you're using an older version of Dreamweaver that hasn't created an editable region inside the head, copy and paste the template comments into the master template just before the closing head tag, as shown above.

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

Editable region but not in code view

EDIT: While cooking dinner I thought that the computer "fixes" itself when it reboots what about Dreamweaver? I closed DW down. Reopened the app and voila. I CAN edit that section in code view now. It's weird but it appears to be working. I'll repost if something is amiss again regarding this issue. I'll leave the post up in case it's helpful to anyone else. thanks.
I have new pages made from a template. I can only edit in design view NOT in code view. I get the standard error of I'm trying to edit where I'm not allowed. I've made templates many times but never had this problem (I don't think!). Does someone have a tip or help for me? In addition to this issue I was not able to change the title of the page until I added the editable region in the template for title line. That's always been default editable before. Thanks a lot. I'm using DW8.
begining code from template:
<!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>Party Invitation Boutique</title> 
begining code from new pages:
<!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>Baby Blue</title> 
-------------then further down on the page is the editable region-------------

<div id="content_right">test only can type in design view. can't add div boxes
even in this editable region. ugh. can't even type next this this text in the
code view. </div>


Best thing you can do in the future is run your code through the validator if the editable region exists:
http://validator.w3.org/
If there are code errors with other tags on the page then it is possible DW is overlooking its own template code. Unfortunately without seeing the whole page I cannot say this is definitely the case, but a likely possibility.

Dreamweaver does not allow me to edit the editable region

Oh my, I'm so desperate in this, I have a .dwt and have set up the editable region as well. When I want to make a new html file from the said template dreamweaver does not allow me to edit it. I mean, all the code is completely grayed out as if the template itself is locked by default.
What I want to do is to create several new pages such as new albums, charts, genres, contacts (which all based on the home template) The home template itself has slider in its body. For the new html files I'm about to create (which I'm so desperate why I can't do so) I want the header and footer to remain the same.
Here is an image of my index.dwt (my homepage) anything inside the red frame is what I want to edit for new albums, charts, genres, contacts, login page, etc. The top part is the header and the bottom one is the footer (Excuse the right image, I'm working on dual screen)
Any help will be appreciated!
Sorry for my english

Hello SeptianNugraha,
here some hints concerning while handling templates (I quote):
The main principle of DW Templates is:
Non-editable regions = propagate to all child pages. The content of non-edtable regions is identical on all child pages. When you edit a non-editable region, DW propagates all changes to all child pages.
Editable regions = do not propagate because they're unique to every child page. The whole idea of editable regions is that they contain page specific content which does not appear on any other child page.
And:
PART 1
1. Create a prototype page with all the sitewide elements (common header, footer, sidebar, etc..) that you will need for your entire project. This requires some careful pre-planning even for small web sites.
2. Validate your code & test this prototype page in all major browsers. 3. When you're completely satisfied with your layout, SaveAs Template. DW will save this as a .dwt file in a site folder called Templates.
4. DW will ask you to add Editable Regions for stuff that will change from page to page. Do this and SAVE.
5. Close your Template.dwt file.
PART 2
1. File > New Page > from Template. Select the template you wish to use. Hit OK.
2. This is a child page. You can only edit content within editable regions. Everything else is locked.
3. SaveAs index.html (your home page) to the root in your local site folder.
PART 3
Repeat PART 2 for each additional page required.
PART 4
1. Open your main TEMPLATE file and add a navigation menu with links to your site pages.2. SAVE.3. DW will ask if you want to populate changes to child pages. Hit yes.
4. Publish all site pages to your server.
PART 5
If you should ever need to edit your TEMPLATE .dwt file, Repeat PART 4.
Good luck!
Hans-Günter

Why does this happen when I insert editable region?

Hi ppl... I got a small problem here. When I insert editing region into the ORANGEBOX div, for some unknown reason which I can't figure out, my spry menu bar shifts to the left. But in preview, it looks fine. What's the reason for this and how can I avoid it? The shifted spry menu bar in the workspace is disturbing me.. haha.. I have attached screenshots of the 2 states below (Before inserting editable region and after inserting editable region)
Before inserting editable region into the ORANGE BOX
After inserting editable region into the ORANGEBOX
Here's the code BEFORE inserting editable region.. If you are free, do try to insert an editable region into the ORANGEBOX, and kindly tell me why it's happening! =) Thanks!
<!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>

<style type="text/css">

</style>


<script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="wrapper">
<div id="header"></div>
<div id="navigationlinks">
    <ul id="MenuBar1" class="MenuBarHorizontal">
      <li><a href="#">Home</a>      </li>
      <li><a href="#">Audio Lectures</a></li>
      <li><a class="MenuBarItemSubmenu" href="#">Video Lectures</a>
        <ul>
          <li><a href="aqeedah1.htm">Aqeedah</a></li>
          <li><a href="fundamentals1.shtml">Tawheed</a></li>
<li><a href="#">Friday Bayans</a></li>
<li><a href="#">Other Topics</a></li>
        </ul>
      </li>
      <li><a href="#">Books</a></li>
    </ul>
</div>
<div id="mainContent">
    <p> </p>
    <p>mainContent</p>
    <p> </p>
    <div id="orangebox">
      <p>ORANGE BOX    </p>
      <p> </p>
    </div>
<p> </p>
    <p>mainContent</p>
    <p> </p>
    <p> </p>
</div>
<div id="footer">
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p>FOOTER </p>
    <p> </p>
    <p> </p>
    <p> </p>
</div>
<p> </p>
<p> </p>
</div>
<script type="text/javascript">

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

Here's the SpryMenuBarHorizontal.css
@charset "UTF-8";
/* SpryMenuBarHorizontal.css - version 0.6 - Spry Pre-Release 1.6.1 */
/* Copyright (c) 2006. Adobe Systems Incorporated. All rights reserved. */
LAYOUT INFORMATION: describes box model, positioning, z-order
/* The outermost container of the Menu Bar, an auto width box with no margin or padding */
ul.MenuBarHorizontal
    margin: 0;
    padding: 0;
    list-style-type: none;
    font-size: 100%;
    cursor: default;
    width: auto;
/* Set the active Menu Bar with this class, currently setting z-index to accomodate IE rendering bug: http://therealcrisp.xs4all.nl/meuk/IE-zindexbug.html */
ul.MenuBarActive
    z-index: 1000;
/* Menu item containers, position children relative to this container and are a fixed width */
ul.MenuBarHorizontal li
    margin: 0;
    padding: 0;
    list-style-type: none;
    font-size: 100%;
    position: relative;
    text-align: left;
    cursor: pointer;
    width: 9em;
    float: left;
/* Submenus should appear below their parent (top: 0) with a higher z-index, but they are initially off the left side of the screen (-1000em) */
ul.MenuBarHorizontal ul
    margin: 0;
    padding: 0;
    list-style-type: none;
    font-size: 100%;
    z-index: 1020;
    cursor: default;
    width: 9em;
    position: absolute;
    left: -1000em;
/* Submenu that is showing with class designation MenuBarSubmenuVisible, we set left to auto so it comes onto the screen below its parent menu item */
ul.MenuBarHorizontal ul.MenuBarSubmenuVisible
    left: auto;
/* Menu item containers are same fixed width as parent */
ul.MenuBarHorizontal ul li
    width: 9em;
/* Submenus should appear slightly overlapping to the right (95%) and up (-5%) */
ul.MenuBarHorizontal ul ul
    position: absolute;
    margin: -5% 0 0 95%;
/* Submenu that is showing with class designation MenuBarSubmenuVisible, we set left to 0 so it comes onto the screen */
ul.MenuBarHorizontal ul.MenuBarSubmenuVisible ul.MenuBarSubmenuVisible
    left: auto;
    top: 0;
DESIGN INFORMATION: describes color scheme, borders, fonts
/* Submenu containers have borders on all sides */
ul.MenuBarHorizontal ul
    border: 1px solid #CCC;
/* Menu items are a light gray block with padding and no text decoration */
ul.MenuBarHorizontal a
    display: block;
    cursor: pointer;
    color: #333;
    text-decoration: none;
    font-family: Arial, Helvetica, sans-serif;
    font-size: 12px;
    font-weight: bold;
    padding-top: 1.1em;
    padding-right: 0.75em;
    padding-bottom: 1.1em;
    padding-left: 0.75em;
    text-align: center;
/* Menu items that have mouse over or focus have a blue background and white text */
ul.MenuBarHorizontal a:hover, ul.MenuBarHorizontal a:focus
    color: #FFF;
/* Menu items that are open with submenus are set to MenuBarItemHover with a blue background and white text */
ul.MenuBarHorizontal a.MenuBarItemHover, ul.MenuBarHorizontal a.MenuBarItemSubmenuHover, ul.MenuBarHorizontal a.MenuBarSubmenuVisible
    color: #FFF;
SUBMENU INDICATION: styles if there is a submenu under a given menu item
/* Menu items that have a submenu have the class designation MenuBarItemSubmenu and are set to use a background image positioned on the far left (95%) and centered vertically (50%) */
ul.MenuBarHorizontal a.MenuBarItemSubmenu
    background-image: url(SpryMenuBarDown.gif);
    background-repeat: no-repeat;
    background-position: 95% 50%;
/* Menu items that have a submenu have the class designation MenuBarItemSubmenu and are set to use a background image positioned on the far left (95%) and centered vertically (50%) */
ul.MenuBarHorizontal ul a.MenuBarItemSubmenu
    background-image: url(SpryMenuBarRight.gif);
    background-repeat: no-repeat;
    background-position: 95% 50%;
/* Menu items that are open with submenus have the class designation MenuBarItemSubmenuHover and are set to use a "hover" background image positioned on the far left (95%) and centered vertically (50%) */
ul.MenuBarHorizontal a.MenuBarItemSubmenuHover
    background-repeat: no-repeat;
    background-position: 95% 50%;
/* Menu items that are open with submenus have the class designation MenuBarItemSubmenuHover and are set to use a "hover" background image positioned on the far left (95%) and centered vertically (50%) */
ul.MenuBarHorizontal ul a.MenuBarItemSubmenuHover
    background-image: url(SpryMenuBarRightHover.gif);
    background-repeat: no-repeat;
    background-position: 95% 50%;
BROWSER HACKS: the hacks below should not be changed unless you are an expert
/* HACK FOR IE: to make sure the sub menus show above form controls, we underlay each submenu with an iframe */
ul.MenuBarHorizontal iframe
    position: absolute;
    z-index: 1010;
    filter:alpha(opacity:0.1);
/* HACK FOR IE: to stabilize appearance of menu items; the slash in float is to keep IE 5.0 from parsing */
@media screen, projection
    ul.MenuBarHorizontal li.MenuBarItemIE
    display: inline;
    f\loat: left;

Template_Can't edit in editable region

I created a template but an unable to edit in the editable region. Does anyone know why? Here is the code for the parent pasted below and I will paste the code for the child on another post.   Here is what it looks like in Dreamweaver:
Here is the error message that I'm getting for the child:
Can someone please help?
<!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>Inland Empire Waterkeeper</title>

<link href="../_css/styles.css" rel="stylesheet" type="text/css" />
<script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
<style type="text/css">
body,td,th {
    color: #333333;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 12px;
body {
    background-color: #FFFFFF;
    color: #D6D6D6;
    background-image: url(../_images/background_teal.png);
    background-repeat: repeat-x;
    margin: auto;
    margin-left: 0px;
    margin-top: 0px;
    margin-right: 0px;
    margin-bottom: 0px;
h1 {
    font-size: 28px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h2 {
    font-size: 22px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h3 {
    font-size: 20px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h4 {
    font-size: 18px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h5 {
    font-size: 16px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h6 {
    font-size: 14px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
p {
    margin-top: 0;
    margin-bottom: 0;
    text-align: justify;
</style>


</head>
<body>
<div class="container">
<div class="header"><img src="../_images/banner.jpg" width="933" height="300" /></div>
<div class="menubar">
    <ul id="MenuBar1" class="MenuBarHorizontal">
      <li><a href="#" class="MenuBarItemSubmenu">About Us</a>
        <ul>
          <li><a href="../organization.html" class="MenuBarItemSubmenu">Our Org.</a>
            <ul>
              <li><a href="../mission.html">Our Mission</a></li>
              <li><a href="../history.html">Our History</a></li>
              <li><a href="../community.html">Our Community</a></li>
            </ul>
          </li>
          <li><a href="../team.html" class="MenuBarItemSubmenu">Our Team</a>
            <ul>
              <li><a href="../staff.html">Staff</a></li>
              <li><a href="../supporters.html">Supporters</a></li>
              <li><a href="../advisoryboard.html">Advisory Board</a></li>
            </ul>
          </li>
          <li><a href="../coastkeeper.html">Coastkeeper</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">What We Do</a>
        <ul>
          <li><a href="../programs.html" class="MenuBarItemSubmenu">Programs</a>
            <ul>
              <li><a href="../advocacy.html">Advocacy</a></li>
              <li><a href="../education.html">Education</a></li>
              <li><a href="../research.html">Research</a></li>
              <li><a href="../restoration.html">Restoration</a></li>
              <li><a href="../enforcement.html">Enforcement</a></li>
            </ul>
          </li>
          <li><a href="../prokects.html">Projects</a></li>
          <li><a href="../datareports.html">Data & Reports</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">Get Involved</a>
        <ul>
          <li><a href="../volunteer.html">Volunteer</a></li>
          <li><a href="../employment.html">Employment</a></li>
          <li><a href="../events.html">Events & Meetings</a></li>
          <li><a href="../donate.html">Donate</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">News Room</a>
        <ul>
          <li><a href="../pressrelease.html">In the News and Press Releases</a></li>
          <li><a href="../legislation.html">Legislative Updates</a></li>
          <li><a href="../waternews.html">Water in the News</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">Resources</a>
        <ul>
          <li><a href="#" class="MenuBarItemSubmenu">Information</a>
            <ul>
              <li><a href="../watershed.html">Our Watershed</a></li>
              <li><a href="../reportpollution.html">Report Pollution</a></li>
            </ul>
          </li>
          <li><a href="../photos.html">Photo Gallery</a></li>
        </ul>
      </li>
      <li><a href="../contact.html">Contact Us</a></li>
    </ul>
</div>
<div class="body">
    <div class="emptyspacecontent">
    <h4><strong style="text-align: justify;">Content<br />
    </strong></h4>
</div>
      <div class="emptyspace4">space</div>
</div>
<div class="footer"><img src="../_images/footer_transparent.png" width="933" height="100" alt="Inland Empire Waterkeeper" /></div>
</div>
<script type="text/javascript">
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
</script>
</body>
</html>

Here is the code for the child:
<!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>Inland Empire Waterkeeper</title>

<link href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/_css/styles.css" rel="stylesheet" type="text/css" />
<script src="file:///C|/Users/Mondays/Desktop/iewaterkeeper/SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
<link href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/SpryAssets/SpryMenuBarHorizontal.css " rel="stylesheet" type="text/css" />
<style type="text/css">
body,td,th {
    color: #333333;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 12px;
body {
    background-color: #FFFFFF;
    color: #D6D6D6;
    background-image: url(file:///C|/Users/Mondays/Desktop/iewaterkeeper/_images/background_teal.png);
    background-repeat: repeat-x;
    margin: auto;
    margin-left: 0px;
    margin-top: 0px;
    margin-right: 0px;
    margin-bottom: 0px;
h1 {
    font-size: 28px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h2 {
    font-size: 22px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h3 {
    font-size: 20px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h4 {
    font-size: 18px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h5 {
    font-size: 16px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
h6 {
    font-size: 14px;
    color: #666666;
    margin-top: 0;
    margin-bottom: 0;
    text-align: left;
p {
    margin-top: 0;
    margin-bottom: 0;
    text-align: justify;
</style>


</head>
<body>
<div class="container">
<div class="header"><img src="file:///C|/Users/Mondays/Desktop/iewaterkeeper/_images/banner.jpg" width="933" height="300" /></div>
<div class="menubar">
    <ul id="MenuBar1" class="MenuBarHorizontal">
      <li><a href="#" class="MenuBarItemSubmenu">About Us</a>
        <ul>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/organization.html" class="MenuBarItemSubmenu">Our Org.</a>
            <ul>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/mission.html">Our Mission</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/history.html">Our History</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/community.html">Our Community</a></li>
            </ul>
          </li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/team.html" class="MenuBarItemSubmenu">Our Team</a>
            <ul>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/staff.html">Staff</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/supporters.html">Supporters</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/advisoryboard.html">Advisory Board</a></li>
            </ul>
          </li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/coastkeeper.html">Coastkeeper</a></l i>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">What We Do</a>
        <ul>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/programs.html" class="MenuBarItemSubmenu">Programs</a>
            <ul>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/advocacy.html">Advocacy</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/education.html">Education</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/research.html">Research</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/restoration.html">Restoration</a></l i>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/enforcement.html">Enforcement</a></l i>
            </ul>
          </li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/prokects.html">Projects</a></li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/datareports.html">Data & Reports</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">Get Involved</a>
        <ul>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/volunteer.html">Volunteer</a></li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/employment.html">Employment</a></li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/events.html">Events & Meetings</a></li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/donate.html">Donate</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">News Room</a>
        <ul>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/pressrelease.html">In the News and Press Releases</a></li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/legislation.html">Legislative Updates</a></li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/waternews.html">Water in the News</a></li>
        </ul>
      </li>
      <li><a href="#" class="MenuBarItemSubmenu">Resources</a>
        <ul>
          <li><a href="#" class="MenuBarItemSubmenu">Information</a>
            <ul>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/watershed.html">Our Watershed</a></li>
              <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/reportpollution.html">Report Pollution</a></li>
            </ul>
          </li>
          <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/photos.html">Photo Gallery</a></li>
        </ul>
      </li>
      <li><a href="file:///C|/Users/Mondays/Desktop/iewaterkeeper/contact.html">Contact Us</a></li>
    </ul>
</div>
<div class="body">
    <div class="emptyspacecontent">
    <h4><strong style="text-align: justify;">Content<br />
    </strong></h4>
</div>
      <div class="emptyspace4">space</div>
</div>
<div class="footer"><img src="file:///C|/Users/Mondays/Desktop/iewaterkeeper/_images/footer_transparent.png" width="933" height="100" alt="Inland Empire Waterkeeper" /></div>
</div>
<script type="text/javascript">
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
</script>
</body>
</html>

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.

Editable Region - Head

Similar Messages

Maybe you are looking for