Nested Editable Region

I am trying to save a template and update all the attached
files but when I do, I get the following message:
There is an error at line 8, column 7 (absolute position 507)
of “E:fredbabb.com\index.html”: nested editable regions
It comes up for each page that is connected to the template
and once I click ok on each of them, it comes up with the following
and nothing gets updated:
Updating E:\fredbabb.com\
index.html -- not updated, error in template or instance file
wholesaleapp.html -- not updated, error in template or
instance file
wholesale.html -- not updated, error in template or instance
file
thankyou.html -- not updated, error in template or instance
file
contact.html -- not updated, error in template or instance
file
about.html -- not updated, error in template or instance file
store.html -- not updated, error in template or instance file
Done.
files examined: 7
files updated: 0
files which could not be updated: 0
total time: (0:01:10)
I have tried to find a nested editable region and cannot find
anything. If you know how to read code, you can check the source on
the website to see if you can find anything...www.fredbabb.com
Thanks. I need help.
babbstudios

Your Template is horked.
Please upload it to the site and post a link to it so we can
see the code.
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
==================
"babbstudios" <[email protected]> wrote in
message
news:gfhuk9$rvl$[email protected]..
>I am trying to save a template and update all the
attached files but when I
>do,
> I get the following message:
>
> There is an error at line 8, column 7 (absolute position
507) of
> ?E:fredbabb.com\index.html?: nested editable regions
>
> It comes up for each page that is connected to the
template and once I
> click
> ok on each of them, it comes up with the following and
nothing gets
> updated:
>
> Updating E:\fredbabb.com\
> index.html -- not updated, error in template or instance
file
> wholesaleapp.html -- not updated, error in template or
instance file
> wholesale.html -- not updated, error in template or
instance file
> thankyou.html -- not updated, error in template or
instance file
> contact.html -- not updated, error in template or
instance file
> about.html -- not updated, error in template or instance
file
> store.html -- not updated, error in template or instance
file
> Done.
> files examined: 7
> files updated: 0
> files which could not be updated: 0
> total time: (0:01:10)
>
> I have tried to find a nested editable region and cannot
find anything.
> If
> you know how to read code, you can check the source on
the website to see
> if
> you can find anything...www.fredbabb.com
>
> Thanks. I need help.
>
> babbstudios
>

Similar Messages

Nested Editable Regions Error Message

I'm trying to create a dynamic template. I've saved a header
and footer as library items, and I want to include them in the
template. In addition I want to have an editable region between
them. For some reason, when I go to save as template, the error
message comes up. It says 'error at line 57, column 323(absolute
position 2998) of ... :nested editable regions' . I have narrowed
this error to be caused by the header (which was created as a
sliced image in photoshop), but for what reason I don't know. Any
ideas why I am getting this error message and what I can do to fix
it? The template won't save otherwise and I can't find any
information on dreamweaver 8 help menu.

There is a parent file and an included file. Here's an
example -
The parent file is this -
<html>
<head>
</head>
<body>

</body>
</html>
and foo.html (the included file) is this -
<p>Hello World</p>
The file you have linked me to is a badly broken template
page. It's broken
because the Library items have not been made properly since
they contain
redundant <body> tags, CSS, and javascript as well.
This will never work the way you want, particularly not in
DW....
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
==================
"Genius2112" <[email protected]> wrote in
message
news:eo41an$93v$[email protected]..
>
http://www.lyncourtrec.com/Lyncourt%20Rec%20Website/Pages/Template.dwt.asp
>
>
> Sorry, I'm not quite sure what you meant by "being
included". The images
> aren't with the header b/c I didn't adjust their source
folder since I had
> to
> upload it on a different site (I don't have a hosting
plan for this site
> yet).
> Hope this is what you were looking for. Thank you for
your help.
>
>

Please Help Nested Editable Region Image & Spry

Please Help Me.
New to Dreamweaver. I've been given a "grandchild" nested temple with only one editable region to alter. I've read and Googled since Saturday. My brain actually hurts.
Goal
- Insert my background image into region
- Add Spry accordion to mid left
- Add Spry collapsible to bottom right
How can 3 things be so hard? Please, can someone walk me through this? Thank you

I've been given a "grandchild" nested template with only one editable region to alter.
Nested templates. Aaaaaak! There's no advantage in nested templates, ever. They're so problematic it makes my head hurt just thinking about them.
If you have the parent and grandparent template.dwt files to work with, you'll need to insert Editable Regions to hold your scripts and other supporting widget code.
If you don't have those files and you can't edit the <head>, you can't insert widgets into Template child or grandchild pages. You'll need to detach the page from Templates.
Nancy O.

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

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

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

     Child Template CSS Links Here.

Child Template:

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

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

     Child PAGE CSS Links Here. (Accurately appearing Editable)

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

     Child Template CSS Links Here.

Child Template:

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

Child Page:

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

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

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

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
>

Nested regions best practice regarding inheritance of editable regions.

Have a template page, http://www.satgraphics.com/templates/main_01.dwt in which I have an area labeled "div#main_wrapper".
When attempting to make it an "editable" region, I received the following comment: "The selection already contains or overlaps with an editable, repeating, or optional region".
I had already made the "header" and "column_left" regions editable, but as the "column_left" is nested within the wrapper, my question would be; Would the correct process be to un-do the "column_left" editable region, make the "div#main_wrapper" editable, and be able to edit the "column_left" area as an inherited editable area?
When I did try to do so to the "main_wrapper" div, I did not get the identifier label (blue text block at top left of each area) and received the warning as mentioned previously.
Thank You...

I did attempt to specify the "main_wrapper" div, but did so after already creating the "column_left" div region as editable, (nested in the "wrapper") and that is when I received the error message.
As an aside, the site is fairly simple, so I am using a single template in which I do make content changes to header, column_left, and hopefully within the wrapper itself) for each new page, thus intentionally wanting editable region in content of "wrapper".
The "footer" and "menu" are the two areas in which I did not open up for change; the "menu" is a library item, so any changes are made from there.
So, question now becomes that of getting the "main_wrapper" div editable and how can that be done without the aforementioned message?
http://www.satgraphics.com/templates/main_01.dwt
Thank You for your help.

Nesting uneditable regions inside editable regions? [CS5]

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

Build your menu with a persistent page indicator and you won't need to change anything on your pages except the body class name.
I keep my menus in server-side include files and this method works great.
http://forums.adobe.com/message/2647186#2647186
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web-design.blogspot.com/

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

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.

Inputting a list into an alternative to inputting it into an editable region in a template

Hello all,
I did ask this question yesterday but only got partial feedback so I'm hoping someone can help as I can't find the answer anywhere.
I'm hoping you can help me.
I am creating an online clothing shop website and am having trouble.
I have created a main template from scratch that reflects in the mens and womens pages, and the contact, about etc pages with all headers, logos, footer, a spry menu etc. I made these pages from the main template via new - Page from template etc so any changes I made to the header, logo etc will easily reflect in all of these pages.
This part is all fine.
This is my issue - in the main template I have an editable region so that I can input different content ie. 'about' info on the 'about' page, and product info on the mens / womens pages etc.
Basically in each page Mens / Womens I need category pages - tops, shirts etc. These are all in the drop down spry menu but I also want them as a list in the mens and womens pages.
From the template I created the mens and womens pages and have now saved these as a template as there will be around 10 categories for each mens and womens (tops, shirts etc) that I want to be able to replect any changes, ie. in the 'mens template' instead of having to do it in each category page - as this will take a long time.
The problem is that I put the list in the editable region in the mens template, but I now know any changes I make wont be relfected in the category pages I have made from the mens template as this is an editable region.
How can I make a category list in the mens template page that will be reflected in each category page?
I'm really stuck and have no idea how to do this, I'd appreciate any help.
Thankyou in advance

I don't recommend using multiple or nested Templates. There are much better ways to do what you want without going down this very slippery slope.
Use Server-Side Includes alone or with your main Template.
Build a Dynamic Site with databases and server-side programming.
E-commerce Solutions:
Cartweaver (extension for Dreamweaver)
http://www.cartweaver.com/
Web Assist
http://www.webassist.com/support/ecommerce-options.php
Building an e-comm site with DW & PHP (video training)
http://www.lynda.com/Web-Interactive-Web-Design-Projects-tutorials/Building-eCommerce-Web- Site-Using-Dreamweaver-PHP/83091-2.html?utm_medium=affiliate&utm_source=ldc_affiliate&utm_ content=524&utm_campaign=CD4386&bid=524&aid=CD4386&opt=
Nancy O.

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

Child pages inheriting editable regions from template

I have looked far and wide and cannot find an answer to this problem:
We recently did a homepage update where the nested and/or second level template (index_template.dwt) was changed. Since much of the formatting was the same - I duplicated the original index_template and made all necessary changes. From this template two child pages were created for our US and UK site. Upon creating the page(s) from the index_template they are inheriting the editable regions, thus not having the ability to update when changes are being made to the template. I have tried multiple ways in an attempt to correct this - but to no avail. Does anyone have a clue how to correct this? As of now I have to manually update all 3 pages.
BTW I am also a relatively new user who was thrown into managing our company website and pretty much doing a redo on the whole thing. Talk about a learning experience!

My issue is when you create a page from a template they are not supposed to inherit the editable regions less otherwise marked.
But that is not true. A newly created child page will inherit ALL content from its template. But changes to the editable region contents in the template will NOT propagate to existing child pages.
So, for example, if I want all child pages to have an embedded stylesheet in the head that is EDITABLE, my template would look like this -

<style type="text/css">
</style>

All newly created child pages will then look like this -

<style type="text/css">
</style>

If I then go back to the template and change it like this -

<style type="text/css">
body { margin:0; }
</style>

that change will NOT propagate to existing child pages, but WILL appear in child pages created subsequently to the save of the template after the change.
And by the way, it's always been this way.

Creating template from template / editable regions

Hello all,
I'm hoping you can help me.
I am creating an online clothing shop website and am having trouble with creating category pages.
I have created the template with all headers, logos, footer, a spry menu etc.
I have then from the template (via new - Page from template etc) pages for mens / womens / shoes
This part is all fine.
However each of these pages ie. the 'mens' will have pages per category created from it for mens shirts, mens top etc.
For example I need a list of each category on the mens page that I dont want to appear on any other pages, just all of the mens category pages (tops, shorts etc) and this will also be done for the womens pages.
I saved the 'mens' page as a template but due to the section that the category list being in an 'editable region' when I have created new pages from the 'mens' template the changes wont filter through to each category page.
How can I insert a category list into the 'mens' template that will reflect the changes I make in the category pages? As I don't want to manually update each individual category page.
I hope this makes sense and someone can help me out
Thanks

What is your skill level with HTML and CSS?
I saved the 'mens' page as a template but due to the section that the category list being in an 'editable region' when I have created new pages from the 'mens' template the changes wont filter through to each category page.
This is not a good start. You do not want to begin using nested templates for anything.
One simple way (although not the optimal way) to do what you want to do is to make the place on the page where you want the lists to appear into an editable region in the template. Then create a variety of Library items (in DW) each of which contains only the list for each of your categories. On the appropriate child pages, insert the associated list into the editable region. So, for example, the men's page will have the men's list, etc.
A Library item is like a mini-template in that changes made to any given Library item are automatically propagated to all instances where that Library item is being used.
Is that what you are after?

DWCS3 Template Editable Regions and Editable Attributes?

Using DWCS3 / WIN XP
New to DWCS3 and templates AND CSS but I'm managing I
think....
QUESTION:
is there a way to allow the end user to edit the content of
an editable region and also the attributes of the cell in which the
editable region resides?
SITUATION:
I'm building templates for pages (styled with external CSS)
that will be editable by the end user via Contribute. I've put
editable and repeating regions (imgs and navigation menus) in
particular tds and would like the end user to be able to change the
color of the background of the cells in which the editable regions
reside.....
Of course I get "cannot place an editable region inside an
editable region" .......understandable...i've read more than a few
help/tutorial docs......
So I thought that I should click the tag selector for that td
and Make Attribute Editable.....
That's not working either....I know I'm missing something
because I haven't used DW in years and I'm just not getting some
big picture logic......
EXAMPLE: In the .html page attached for viewing, the upper
left image SRC is in an editable region. I would like the
background color of the cell it is in to be editable as well. Same
goes for the background color of the left navigation menu which
resides in a nested table by the way...........but i still want the
color to be editable.....
Thanks so much for any help you can give....
CoCo
PAGE based on Template:
http://www.methods.com/npsbweb/schools/NPSB_school_lev_1.html
CSS and TEMPLATE CODE: BELOW
@charset "utf-8";
p {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 10pt;
font-weight: normal;
h1 {
font-size: 16px;
color: #999966;
font-family: "Times New Roman", Times, serif;
h2 {
font-size: 18px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
text-align: center;
margin: 0px;
h3 {
font-size: 14px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
h4 {
font-size: 12pt;
color: #999966;
font-family: "Times New Roman", Times, serif;
text-align: center;
letter-spacing: 1px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 5px;
margin-left: 0px;
h5 {
font-size: 12px;
color: #999966;
font-family: Verdana, Arial, Helvetica, sans-serif;
h6 {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 8pt;
color: #333366;
text-align: center;
#tdDivideLineTop {
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #999966;
height: 2px;
#tdMainImgTop {
text-align: center;
vertical-align: middle;
height: 175px;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
background-color: #ffffff;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #D5D5AA;
#tdTitleRow {
height: 175px;
vertical-align: middle;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
#tdRightLineTop {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #CACAFF;
#tdMainNavigation {
display: block;
font-size: 9pt;
background-color: #D5D5AA;
#tdRightNavigation {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #D5D5AA;
background-color: #FFFFFF;
#tdMainNavigation a:link {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:visited {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:hover {
color: #FFFFFF;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #999966;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdMainNavigation a:active {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
font-weight: normal;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #D5D5AA;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdRightNavigation a:link {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:visited {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:hover {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #333399;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:active {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #666633;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
body {
margin-left: 0px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 0px;
a {
font-size: 10pt;
color: #333366;
a:visited {
color: #330066;
a:hover {
color: #999966;
a:active {
color: #999900;
body,td,th {
font-size: 10pt;

Using DWCS3 / WIN XP
New to DWCS3 and templates AND CSS but I'm managing I
think....
QUESTION:
is there a way to allow the end user to edit the content of
an editable region and also the attributes of the cell in which the
editable region resides?
SITUATION:
I'm building templates for pages (styled with external CSS)
that will be editable by the end user via Contribute. I've put
editable and repeating regions (imgs and navigation menus) in
particular tds and would like the end user to be able to change the
color of the background of the cells in which the editable regions
reside.....
Of course I get "cannot place an editable region inside an
editable region" .......understandable...i've read more than a few
help/tutorial docs......
So I thought that I should click the tag selector for that td
and Make Attribute Editable.....
That's not working either....I know I'm missing something
because I haven't used DW in years and I'm just not getting some
big picture logic......
EXAMPLE: In the .html page attached for viewing, the upper
left image SRC is in an editable region. I would like the
background color of the cell it is in to be editable as well. Same
goes for the background color of the left navigation menu which
resides in a nested table by the way...........but i still want the
color to be editable.....
Thanks so much for any help you can give....
CoCo
PAGE based on Template:
http://www.methods.com/npsbweb/schools/NPSB_school_lev_1.html
CSS and TEMPLATE CODE: BELOW
@charset "utf-8";
p {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 10pt;
font-weight: normal;
h1 {
font-size: 16px;
color: #999966;
font-family: "Times New Roman", Times, serif;
h2 {
font-size: 18px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
text-align: center;
margin: 0px;
h3 {
font-size: 14px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
h4 {
font-size: 12pt;
color: #999966;
font-family: "Times New Roman", Times, serif;
text-align: center;
letter-spacing: 1px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 5px;
margin-left: 0px;
h5 {
font-size: 12px;
color: #999966;
font-family: Verdana, Arial, Helvetica, sans-serif;
h6 {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 8pt;
color: #333366;
text-align: center;
#tdDivideLineTop {
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #999966;
height: 2px;
#tdMainImgTop {
text-align: center;
vertical-align: middle;
height: 175px;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
background-color: #ffffff;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #D5D5AA;
#tdTitleRow {
height: 175px;
vertical-align: middle;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
#tdRightLineTop {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #CACAFF;
#tdMainNavigation {
display: block;
font-size: 9pt;
background-color: #D5D5AA;
#tdRightNavigation {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #D5D5AA;
background-color: #FFFFFF;
#tdMainNavigation a:link {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:visited {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:hover {
color: #FFFFFF;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #999966;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdMainNavigation a:active {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
font-weight: normal;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #D5D5AA;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdRightNavigation a:link {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:visited {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:hover {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #333399;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:active {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #666633;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
body {
margin-left: 0px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 0px;
a {
font-size: 10pt;
color: #333366;
a:visited {
color: #330066;
a:hover {
color: #999966;
a:active {
color: #999900;
body,td,th {
font-size: 10pt;

Nested Editable Region

Similar Messages

Maybe you are looking for