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" />
<!-- TemplateBeginEditable name="doctitle" -->
<title>Inland Empire Waterkeeper</title>
<!-- TemplateEndEditable -->
<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>
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
</head>
<body>
<div class="container">
<div class="header"><!-- TemplateBeginEditable name="header" --><img src="../_images/banner.jpg" width="933" height="300" /><!-- TemplateEndEditable --></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;"><!-- TemplateBeginEditable name="Content" -->Content<!-- TemplateEndEditable --><br />
</strong></h4>
</div>
<div class="emptyspace4"><!-- TemplateBeginEditable name="space" -->space<!-- TemplateEndEditable --></div>
</div>
<div class="footer"><!-- TemplateBeginEditable name="footer" --><img src="../_images/footer_transparent.png" width="933" height="100" alt="Inland Empire Waterkeeper" /><!-- TemplateEndEditable --></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"><!-- InstanceBegin template="/Templates/template.dwt" codeOutsideHTMLIsLocked="false" -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- InstanceBeginEditable name="doctitle" -->
<title>Inland Empire Waterkeeper</title>
<!-- InstanceEndEditable -->
<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>
<!-- InstanceBeginEditable name="head" -->
<!-- InstanceEndEditable -->
</head>
<body>
<div class="container">
<div class="header"><!-- InstanceBeginEditable name="header" --><img src="file:///C|/Users/Mondays/Desktop/iewaterkeeper/_images/banner.jpg" width="933" height="300" /><!-- InstanceEndEditable --></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;"><!-- InstanceBeginEditable name="Content" -->Content<!-- InstanceEndEditable --><br />
</strong></h4>
</div>
<div class="emptyspace4"><!-- InstanceBeginEditable name="space" -->space<!-- InstanceEndEditable --></div>
</div>
<div class="footer"><!-- InstanceBeginEditable name="footer" --><img src="file:///C|/Users/Mondays/Desktop/iewaterkeeper/_images/footer_transparent.png" width="933" height="100" alt="Inland Empire Waterkeeper" /><!-- InstanceEndEditable --></div>
</div>
<script type="text/javascript">
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
</script>
</body>
<!-- InstanceEnd --></html>
Similar Messages
-
Problem with editing Editable Region - HELP!
My website is www.yucholian.com
I have created a template and have assigned a main body to be
an Editable Region. However, I can't seem to use different fonts,
sizes or styles as I wish. If I go to Text drop down, go to size,
all options are greyed out. Can anyone help?
BTW, I'm using 30 day trial.
I find Dreamweaver to be very finicky. Even something simple
as applying a template that I created, view doesn't update, showing
doubles...
Thanks in advance.> I find Dreamweaver to be very finicky. Even something
simple as applying
> a
> template that I created, view doesn't update, showing
doubles...
The more you know about HTML, the less you will run into such
things - but I
have to say, I have no idea what you are describing here. It
sounds to me
like user error, but I can't say for sure.
> However, I can't seem to use different fonts, sizes or
styles as I
> wish.
Show me your template, tell me what you are trying to change,
and I'll
explain to you what is happening.
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
==================
"yucholian" <[email protected]> wrote in
message
news:edk7lr$73m$[email protected]..
> My website is www.yucholian.com
> I have created a template and have assigned a main body
to be an Editable
> Region. However, I can't seem to use different fonts,
sizes or styles as
> I
> wish. If I go to Text drop down, go to size, all options
are greyed out.
> Can
> anyone help?
> BTW, I'm using 30 day trial.
> I find Dreamweaver to be very finicky. Even something
simple as applying
> a
> template that I created, view doesn't update, showing
doubles...
>
> Thanks in advance.
> -
An editable region, how to keep text formatting?
Hello fellas.
Is there any way to keep the text formatting when I paste it
into my edible region of the template?
Every time I attempt it - dreamweaver gives me message "
making this change would require code change which is locked by a
template". The only way to paste anything into a region is by
turning off any copy/paste text formatting completely, which is
painful to edit, especially with a large number of articles.
Would greatly appreciate any help.This is a common alert when the page you are working on
contains *any*
coding anomalies (perhaps in a location other than the
editable region).
Does the page validate before the paste? Does the code you
are pasting
validate?
The answer is, of course, it's possible to retain formatting
(provided all
code is valid). What app are you pasting from?
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
==================
"dreamweaver_novice" <[email protected]>
wrote in message
news:f3s8v2$daj$[email protected]..
> Hello fellas.
>
> Is there any way to keep the text formatting when I
paste it into my
> edible
> region of the template?
> Every time I attempt it - dreamweaver gives me message "
making this
> change
> would require code change which is locked by a
template". The only way to
> paste
> anything into a region is by turning off any copy/paste
text formatting
> completely, which is painful to edit, especially with a
large number of
> articles.
>
> Would greatly appreciate any help.
>
>
> -
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" />
<!-- TemplateBeginEditable name="HEAD TAGS" -->
<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">
<!-- TemplateEndEditable -->
<link rel="stylesheet" type="text/css" href="../include/scripts/css/screen.css" />
<!--[if IE 6]> <link href="/include/scripts/css/ie6.css" rel="stylesheet" type="text/css" /> <![endif]-->
<!--[if IE 7]> <link href="/Include/Scripts/css/ie7.css" rel="stylesheet" type="text/css" /> <![endif]-->
<script language="JavaScript">
<!--
img = new Array(70);
for (i = 0; i < 70; i++)
img[i] = new Image;
img[0].src = 'http://www.recordsmanagementcenter.com/common/images/admin/add.gif';
img[1].src = 'http://www.recordsmanagementcenter.com/common/images/admin/add_f2.gif';
img[2].src = 'http://www.recordsmanagementcenter.com/common/images/admin/add1.gif';
img[3].src = 'http://www.recordsmanagementcenter.com/common/images/admin/add1_f2.gif';
img[4].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addcontent.gif';
img[5].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addcontent_f2.gif';
img[6].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addfeedback.gif';
img[7].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addfeedback_f2.gif';
img[8].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addforum.gif';
img[9].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addforum_f2.gif';
img[10].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addhotlist.gif';
img[11].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addhotlist_f2.gif';
img[12].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addnavlist.gif';
img[13].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addnavlist_f2.gif';
img[14].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addpage.gif';
img[15].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addpage_f2.gif';
img[16].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsection.gif';
img[17].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsection_f2.gif';
img[18].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addup.gif';
img[19].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addup_f2.gif';
img[20].src = 'http://www.recordsmanagementcenter.com/common/images/admin/adsection.gif';
img[21].src = 'http://www.recordsmanagementcenter.com/common/images/admin/adsection_f2.gif';
img[22].src = 'http://www.recordsmanagementcenter.com/common/images/admin/content.gif';
img[23].src = 'http://www.recordsmanagementcenter.com/common/images/admin/content_f2.gif';
img[24].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit.gif';
img[25].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit_f2.gif';
img[26].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit1.gif';
img[27].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edit1_f2.gif';
img[28].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editcontent.gif';
img[29].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editcontent_f2.gif';
img[30].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editfeedback.gif';
img[31].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editfeedback_f2.gif';
img[32].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editforum.gif';
img[33].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editforum_f2.gif';
img[34].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edithotlist.gif';
img[35].src = 'http://www.recordsmanagementcenter.com/common/images/admin/edithotlist_f2.gif';
img[36].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editnavlist.gif';
img[37].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editnavlist_f2.gif';
img[38].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editpage.gif';
img[39].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editpage_f2.gif';
img[40].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection.gif';
img[41].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection_f2.gif';
img[42].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection1.gif';
img[43].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsection1_f2.gif';
img[44].src = 'http://www.recordsmanagementcenter.com/common/images/admin/feedback.gif';
img[45].src = 'http://www.recordsmanagementcenter.com/common/images/admin/feedback_f2.gif';
img[46].src = 'http://www.recordsmanagementcenter.com/common/images/admin/forums.gif';
img[47].src = 'http://www.recordsmanagementcenter.com/common/images/admin/forums_f2.gif';
img[48].src = 'http://www.recordsmanagementcenter.com/common/images/admin/hotlists.gif';
img[49].src = 'http://www.recordsmanagementcenter.com/common/images/admin/hotlists_f2.gif';
img[50].src = 'http://www.recordsmanagementcenter.com/common/images/admin/navlists.gif';
img[51].src = 'http://www.recordsmanagementcenter.com/common/images/admin/navlists_f2.gif';
img[52].src = 'http://www.recordsmanagementcenter.com/common/images/admin/pages.gif';
img[53].src = 'http://www.recordsmanagementcenter.com/common/images/admin/pages_f2.gif';
img[54].src = 'http://www.recordsmanagementcenter.com/common/images/admin/questions.gif';
img[55].src = 'http://www.recordsmanagementcenter.com/common/images/admin/questions_f2.gif';
img[56].src = 'http://www.recordsmanagementcenter.com/common/images/admin/resources.gif';
img[57].src = 'http://www.recordsmanagementcenter.com/common/images/admin/resources_f2.gif';
img[57].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsup.gif';
img[58].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsup_f2.gif';
img[59].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsdn.gif';
img[60].src = 'http://www.recordsmanagementcenter.com/common/images/admin/addsdn_f2.gif';
img[61].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsup.gif';
img[62].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsup_f2.gif';
img[63].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsdn.gif';
img[64].src = 'http://www.recordsmanagementcenter.com/common/images/admin/editsdn_f2.gif';
function gfAdminOver(img)
{ window.event.srcElement.src = "/common/images/admin/" + img + "_f2.gif";
function gfAdminOut(img)
window.event.srcElement.src = "/common/images/admin/" + img + ".gif";
function gfGoAdmin(url)
window.location = url;
function poppoll(dest, ff)
var d = document;
var ans, ii, jj, pname;
ans = 0;
dest = dest + "&FEEDBACK=" + d.frm["feedback_" + ff].value;
dest = dest + "&SQ=" + d.frm["startq_" + ff].value;
dest = dest + "&EQ=" + d.frm["endq_" + ff].value;
dest = dest + "&SN=" + d.frm["startn_" + ff].value;
dest = dest + "&EN=" + d.frm["endn_" + ff].value;
pname = "";
for (ii = 0; ii < d.frm.length; ii++)
if (d.frm[ii].name.substr(0,7) == "pinput_")
ans = "";
if ((d.frm[ii].type == "radio") || (d.frm[ii].type == "checkbox"))
if (d.frm[ii].checked)
ans = d.frm[ii].value;
else
ans = d.frm[ii].value;
if (ans != "")
if (d.frm[ii].name == pname)
dest = dest + "|" + ans;
else
dest = dest + "&" + d.frm[ii].name + "=" + ans;
pname = d.frm[ii].name;
popup(dest);
function gfClick(dest)
window.location = dest;
function gfNavOver()
{ window.event.srcElement.style.cursor = "hand";
function gfNavOut()
window.event.srcElement.style.cursor = "default";
function gfNavImg(fld,img)
if (document.images)
document[fld].src = img;
function gfNewStyle(sid)
var i;
for (i = 0; i < document.styleSheets.length - 1; i++)
document.styleSheets[i].disabled = ! (document.styleSheets[i].id == sid);
function popup(dest)
window.open(dest,null,"width=800,height=600,location=no,menubar,toolbar,scrollbars,resizable,top=0,left=0");
function popupres(dest,wi,ht)
window.open(dest,null,"width=" + wi + ",height=" + ht + ",location=no,menubar,toolbar,scrollbars,resizable,top=0,left=0");
CSInit = new Array;
function CSScriptInit() {
if(typeof(skipPage) != "undefined") { if(skipPage) return; }
idxArray = new Array;
for(var i=0;i<CSInit.length;i++)
idxArray[i] = i;
CSAction2(CSInit, idxArray);}
CSAg = window.navigator.userAgent; CSBVers = parseInt(CSAg.charAt(CSAg.indexOf("index.html")+1),10);
function IsIE() { return CSAg.indexOf("MSIE") > 0;}
function CSIEStyl(s) { return document.all.tags("div")[s].style; }
function CSNSStyl(s) { return CSFindElement(s,0); }
function CSFindElement(n,ly) { if (CSBVers < 4) return document[n];
var curDoc = ly ? ly.document : document; var elem = curDoc[n];
if (!elem) { for (var i=0;i<curDoc.layers.length;i++) {
elem = CSFindElement(n,curDoc.layers[i]); if (elem) return elem; }}
return elem;
function CSClickReturn () {
var bAgent = window.navigator.userAgent;
var bAppName = window.navigator.appName;
if ((bAppName.indexOf("Explorer") >= 0) && (bAgent.indexOf("Mozilla/3") >= 0) && (bAgent.indexOf("Mac") >= 0))
return true; // dont follow link
else return false; // dont follow link
function CSButtonReturn () {
var bAgent = window.navigator.userAgent;
var bAppName = window.navigator.appName;
if ((bAppName.indexOf("Explorer") >= 0) && (bAgent.indexOf("Mozilla/3") >= 0) && (bAgent.indexOf("Mac") >= 0))
return false; // follow link
else return true; // follow link
CSIm = new Object();
function CSIShow(n,i) {
if (document.images) {
if (CSIm[n]) {
var img = (!IsIE()) ? CSFindElement(n,0) : document[n];
if (img && typeof(CSIm[n][i].src) != "undefined") {img.src = CSIm[n][i].src;}
if(i != 0)
self.status = CSIm[n][3];
else
self.status = " ";
return true;
return false;
function CSILoad(action) {
im = action[1];
if (document.images) {
CSIm[im] = new Object();
for (var i=2;i<5;i++) {
if (action[i] != '') { CSIm[im][i-2] = new Image(); CSIm[im][i-2].src = action[i]; }
else CSIm[im][i-2] = 0;
CSIm[im][3] = action[5];
CSStopExecution = false;
function CSAction(array) {
return CSAction2(CSAct, array);
function CSAction2(fct, array) {
var result;
for (var i=0;i<array.length;i++) {
if(CSStopExecution) return false;
var actArray = fct[array[i]];
if (actArray == null) return false;
var tempArray = new Array;
for(var j=1;j<actArray.length;j++) {
if((actArray[j] != null) && (typeof(actArray[j]) == "object") && (actArray[j].length == 2)) {
if(actArray[j][0] == "VAR") {
tempArray[j] = CSStateArray[actArray[j][1]];
else {
if(actArray[j][0] == "ACT") {
tempArray[j] = CSAction(new Array(new String(actArray[j][1])));
else
tempArray[j] = actArray[j];
else
tempArray[j] = actArray[j];
result = actArray[0](tempArray);
return result;
CSAct = new Object;
// -->
</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>
<!-- TemplateBeginEditable name="BODY" -->
<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="">
<!-- gfShowAllContent(137,) -->
<a name="1"></a>
<!-- gfShowOther(137,130,) -->
<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>
<!-- End gfShowOther(137,130,) -->
<!-- End gfShowAllContent(137,) --> </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>
<!-- TemplateEndEditable -->
</body>
<!-- Mirrored from www.recordsmanagementcenter.com/ by HTTrack Website Copier/3.x [XR&CO'2008], Tue, 18 Aug 2009 14:14:38 GMT -->
</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:
<!-- InstanceBeginEditable name="doctitle" -->
<title> Your title here </title>
<meta name="description" content="Description here." />
<meta name="keywords" content="keywords here " />
<meta name="robots" content="index,follow" />
<!-- InstanceEndEditable -->
Further down in this same document, I find:
<!-- InstanceBeginEditable name="head" -->
<link href="styles.css" rel="stylesheet" type="text/css">
<style type="text/css">
<!--
.style4 {color: #FFFFFF}
-->
</style>
<script src="../Scripts/swfobject_modified.js" type="text/javascript"></script>
<!-- InstanceEndEditable -->
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 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" ><!-- InstanceBeginEditable
name="Title" -->@@("")@@Roger
> Riordan: Technical notes<!-- InstanceEndEditable
--></p>
> <p class="hdgstn"><!-- InstanceBeginEditable
name="Subtitle" -->Notes<!--
> InstanceEndEditable --></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"><!-- InstanceBeginEditable
name="Subtitle" -->Nested
> Templates<!-- InstanceEndEditable --></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 -
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. -
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" />
<!-- TemplateBeginEditable name="title" --><title>Party Invitation Boutique</title> <!-- TemplateEndEditable -->
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"><!-- InstanceBegin template="/Templates/index.dwt" codeOutsideHTMLIsLocked="false" -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- InstanceBeginEditable name="title" --><title>Baby Blue</title> <!-- InstanceEndEditable -->
-------------then further down on the page is the editable region-------------
<!-- InstanceBeginEditable name="main_content" -->
<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>
<!-- InstanceEndEditable -->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 englishHello 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" />
<!-- TemplateBeginEditable name="doctitle" -->
<title>Untitled Document</title>
<!-- TemplateEndEditable -->
<style type="text/css">
<!--
body {
background-color: #666;
margin: 0px;
padding: 0px;
margin: 0px;
padding: 0px;
#wrapper {
padding: 0px;
width: 900px;
margin-right: auto;
margin-left: auto;
margin-top: 0px;
overflow: hidden;
#navigation {
height: 122px;
#mainContent {
background-color: #FFF;
overflow: hidden;
#header {
background-color: #033;
height: 248px;
#navigationlinks {
font-family: Arial, Helvetica, sans-serif;
font-size: 14px;
font-weight: bold;
color: #000;
height: 42px;
background-color: #0C0;
#footer {
height: 100px;
background-color: #F39;
#orangebox {
height: 100px;
width: auto;
background-color: #F60;
-->
</style>
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
<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">
<!--
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
//-->
</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; -
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">
<!--
body {
font: 100% Verdana, Arial, Helvetica, sans-serif;
background: #666666;
margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
padding: 0;
text-align: center; /* this centers the container in IE 5* browsers. The text is then set to the left aligned default in the #container selector */
color: #000000;
background-color: #D7D7D7;
background-repeat: repeat-x;
border-top-color: #066;
border-right-color: #066;
border-bottom-color: #066;
border-left-color: #066;
/* Tips for Elastic layouts
1. Since the elastic layouts overall sizing is based on the user's default fonts size, they are more unpredictable. Used correctly, they are also more accessible for those that need larger fonts size since the line length remains proportionate.
2. Sizing of divs in this layout are based on the 100% font size in the body element. If you decrease the text size overall by using a font-size: 80% on the body element or the #container, remember that the entire layout will downsize proportionately. You may want to increase the widths of the various divs to compensate for this.
3. If font sizing is changed in differing amounts on each div instead of on the overall design (ie: #sidebar1 is given a 70% font size and #mainContent is given an 85% font size), this will proportionately change each of the divs overall size. You may want to adjust based on your final font sizing.
.twoColElsLtHdr #container {
width: 46em; /* this width will create a container that will fit in an 800px browser window if text is left at browser default font sizes */
background: #FFFFFF;
margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
border: 30px none #C4C4C4;
text-align: left; /* this overrides the text-align: center on the body element. */
padding-left: 10px;
background-color: #FFF;
border-top-color: #C4C4C4;
border-right-color: #C4C4C4;
border-bottom-color: #C4C4C4;
border-bottom-style: outset;
border-left-style: outset;
border-top-width: thick;
border-right-style: outset;
border-top-style: outset;
border-left-color: #C4C4C4;
border-right-width: thick;
border-bottom-width: thick;
border-left-width: thick;
.twoColElsLtHdr #header {
padding: 0 10px; /* this padding matches the left alignment of the elements in the divs that appear beneath it. If an image is used in the #header instead of text, you may want to remove the padding. */
background-color: #FFF;
.twoColElsLtHdr #header h1 {
margin: 0; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
padding: 10px 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
/* Tips for sidebar1:
1. Be aware that if you set a font-size value on this div, the overall width of the div will be adjusted accordingly.
2. Since we are working in ems, it's best not to use padding on the sidebar itself. It will be added to the width for standards compliant browsers creating an unknown actual width.
3. Space between the side of the div and the elements within it can be created by placing a left and right margin on those elements as seen in the ".twoColElsLtHdr #sidebar1 p" rule.
.twoColElsLtHdr #sidebar1 {
float: left;
width: 12em; /* the background color will be displayed for the length of the content in the column, but no further */
padding: 15px 0; /* top and bottom padding create visual space within this div */
background-color: #066;
background-repeat: repeat-x;
border-top-width: thin;
border-top-style: none;
border-right-style: none;
border-bottom-style: none;
border-left-style: none;
border-right-width: thin;
border-bottom-width: thin;
border-left-width: thin;
color: #FFF;
padding-left: 0px;
clear: left;
.twoColElsLtHdr #sidebar1 h3, .twoColElsLtHdr #sidebar1 p {
margin-left: 10px; /* the left and right margin should be given to every element that will be placed in the side columns */
margin-right: 10px;
background-color: #066;
text-decoration: inherit;
/* Tips for mainContent:
1. If you give this #mainContent div a font-size value different than the #sidebar1 div, the margins of the #mainContent div will be based on its font-size and the width of the #sidebar1 div will be based on its font-size. You may wish to adjust the values of these divs.
2. The space between the mainContent and sidebar1 is created with the left margin on the mainContent div. No matter how much content the sidebar1 div contains, the column space will remain. You can remove this left margin if you want the #mainContent div's text to fill the #sidebar1 space when the content in #sidebar1 ends.
3. To avoid float drop, you may need to test to determine the approximate maximum image/element size since this layout is based on the user's font sizing combined with the values you set. However, if the user has their browser font size set lower than normal, less space will be available in the #mainContent div than you may see on testing.
4. In the Internet Explorer Conditional Comment below, the zoom property is used to give the mainContent "hasLayout." This avoids several IE-specific bugs that may occur.
.twoColElsLtHdr #mainContent {
margin: 0 1.5em 0 13em; /* the right margin can be given in ems or pixels. It creates the space down the right side of the page. */
color:#069;
background-color:#FFF;
border-top-style: none;
border-right-style: none;
border-bottom-style: none;
border-left-style: none;
.twoColElsLtHdr #mainContent a:link {
text-decoration: none;
color: #069;
.twoColElsLtHdr #mainContent a:visited {
text-decoration: none;
color: #069;
.twoColElsLtHdr #mainContent a:hover {
text-decoration: underline;
color: #069;
background-color:#FFF
.twoColElsLtHdr #mainContent a:active {
text-decoration: none;
color: #069;
.twoColElsLtHdr #footer {
padding: 0 10px;
line-height: 0pt;
color: #069;
background-color: #FFF;
font-size: 10px;
.twoColElsLtHdr #footer p {
margin: 0; /* zeroing the margins of the first element in the footer will avoid the possibility of margin collapse - a space between divs */
padding: 10px 0; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
background-color: #FFF;
/* Miscellaneous classes for reuse */
.fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
float: right;
margin-left: 8px;
.fltlft { /* this class can be used to float an element left in your page */
float: left;
margin-right: 8px;
.clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
clear:both;
height:0;
font-size: 1px;
line-height: 0px;
h1 {
color: #069;
font-size: 16px;
border-top-color: #069;
border-top-width: thin;
border-right-width: thin;
padding-right: 0px;
padding-left: 0px;
body,td,th {
font-family: verdana;
text-decoration: none;
color: #069;
border-top-color: #069;
border-right-color: #069;
border-bottom-color: #069;
border-left-color: #069;
border-top-style: solid;
border-right-style: solid;
border-bottom-style: solid;
border-left-style: solid;
border-top-width: thin;
border-right-width: thin;
border-bottom-width: thin;
border-left-width: thin;
a:link {
text-decoration: none;
color: #FFF;
a:visited {
text-decoration: none;
color: #FFF;
a:hover {
text-decoration: underline;
color: #FFF;
background-color: #;
background-repeat: repeat-x;
background-position: center;
border-top-color: #069;
border-right-color: #069;
border-bottom-color: #069;
border-left-color: #069;
a:active {
text-decoration: none;
color: #FFF;
border-color: #FFF;
padding-left: 20px;
-->
</style><!--[if IE]>
<style type="text/css">
/* place css fixes for all versions of IE in this conditional comment */
.twoColElsLtHdr #sidebar1 { padding-top: 30px; }
.twoColElsLtHdr #mainContent { zoom: 1; padding-top: 15px; }
/* the above proprietary zoom property gives IE the hasLayout it needs to avoid several bugs */
</style>
<![endif]-->
<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>
<!-- end #mainContent -->
</div>
<!-- This clearing element should immediately follow the #mainContent div in order to force the #container div to contain all child floats -->
<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>
<!-- end #footer -->
</div>
<script type="text/javascript">
<!--
//-->
</script>
</h3>
<!-- end #container -->
</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. -
How to insert a widget in a editable region from a template
Hi there,
ok so basically I am trying to create a HTML page from a template i have already designed.
when I try to insert a widget (Lightbox Gallery) in the editable region I get the following error.
"the widget requires code that must be inserted into the head of the document. insertion cannot happen because this document is read only"
I saw a previous thread (http://forums.adobe.com/thread/901299) that had the same problem with a solution but cant seem to make sense of it.
Not exactly sure where and what to paste in the header of the HTML page.
Any help will be much appreciated.
ThanksHi Murray,
ha funny you would say that is the exact answer you would give me seeing you posted it
I understand the logic behind it though not sure what i need to copy and where.
Basically i craeted a "dummy page" and inserted the widget-no problem there.
next step- what code do i copy from the dummy page and where do i paste it? in the template or HTML page.
Dummy HTML with widget code
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Untitled Document</title>
<script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/jquery.js" type="text/javascript"></script>
<script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/lightbox.js" type="text/javascript"></script>
<link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/lightbox.css" rel="stylesheet" type="text/css" />
<link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/sample_lightbox_layout.css" rel="stylesheet" type="text/css" />
<style type="text/css">
/* BeginOAWidget_Instance_2127022: #gallery */
.lbGallery {
/*gallery container settings*/
background-color: #CCC;
padding-left: 20px;
padding-top: 20px;
padding-right: 20px;
padding-bottom: 20px;
width: 540px;
height: auto;
text-align:left;
.lbGallery ul { list-style: none; margin:0;padding:0; }
.lbGallery ul li { display: inline;margin:0;padding:0; }
.lbGallery ul li a{text-decoration:none;}
.lbGallery ul li a img {
/*border color, width and margin for the images*/
border-color: #3e3e3e;
border-left-width: 10px;
border-top-width: 10px;
border-right-width: 10px;
border-bottom-width: 20px;
margin-left:5px;
margin-right:5px;
margin-top:5px;
margin-bottom:5px:
.lbGallery ul li a:hover img {
/*background color on hover*/
border-color: #ffffff;
border-left-width: 10px;
border-top-width: 10px;
border-right-width: 10px;
border-bottom-width: 20px;
#lightbox-container-image-box {
border-top: 0px none #ffffff;
border-right: 0px none #ffffff;
border-bottom: 0px none #ffffff;
border-left: 0px none #ffffff;
#lightbox-container-image-data-box {
border-top: 0px;
border-right: 0px none #ffffff;
border-bottom: 0px none #ffffff;
border-left: 0px none #ffffff;
/* EndOAWidget_Instance_2127022 */
</style>
<script type="text/xml">
<!--
<oa:widgets>
<oa:widget wid="2127022" binding="#gallery" />
</oa:widgets>
-->
</script>
</head>
<body>
<div id="gallery" class="lbGallery">
<ul>
<li> <a href="/images/lightboxdemo1.jpg" title=""><img src="/images/lightboxdemo_thumb1.jpg" width="72" height="72" alt="Flower" /></a> </li>
<li> <a href="/images/lightboxdemo2.jpg" title=""><img src="/images/lightboxdemo_thumb2.jpg" width="72" height="72" alt="Tree" /></a> </li>
<li> <a href="/images/lightboxdemo3.jpg" title=""><img src="/images/lightboxdemo_thumb3.jpg" width="72" height="72" alt="" /></a> </li>
<li> <a href="/images/lightboxdemo4.jpg" title=""><img src="/images/lightboxdemo_thumb4.jpg" width="72" height="72" alt="" /></a> </li>
<li> <a href="/images/lightboxdemo5.jpg" title=""><img src="/images/lightboxdemo_thumb5.jpg" width="72" height="72" alt="" /></a> </li>
</ul>
</div>
<script type="text/javascript">
// BeginOAWidget_Instance_2127022: #gallery
$(function(){
$('#gallery a').lightBox({
imageLoading: '/images/lightbox/lightbox-ico-loading.gif', // (string) Path and the name of the loading icon
imageBtnPrev: '/images/lightbox/lightbox-btn-prev.gif', // (string) Path and the name of the prev button image
imageBtnNext: '/images/lightbox/lightbox-btn-next.gif', // (string) Path and the name of the next button image
imageBtnClose: '/images/lightbox/lightbox-btn-close.gif', // (string) Path and the name of the close btn
imageBlank: '/images/lightbox/lightbox-blank.gif', // (string) Path and the name of a blank image (one pixel)
fixedNavigation: false, // (boolean) Boolean that informs if the navigation (next and prev button) will be fixed or not in the interface.
containerResizeSpeed: 400, // Specify the resize duration of container image. These number are miliseconds. 400 is default.
overlayBgColor: "#999999", // (string) Background color to overlay; inform a hexadecimal value like: #RRGGBB. Where RR, GG, and BB are the hexadecimal values for the red, green, and blue values of the color.
overlayOpacity: .6, // (integer) Opacity value to overlay; inform: 0.X. Where X are number from 0 to 9
txtImage: 'Image', //Default text of image
txtOf: 'of'
// EndOAWidget_Instance_2127022
</script>
</body>
</html>
thanks again -
Adding text to editable region creates space in the rest of my layout
I created my layout in PS, sliced the images and then imported to DW (html and images).
Layout looks great.
I created editable regions in the template I created from the .html
One I start inserting text into these regions, my container moves and it throws the rest of the layout off by adding space between the editable region and the area above it (a big black line horizontally through the page).
Is there a way to keep the container/editable region from moving or growing with the text so that it doesn't change my layout?
On a side note, this change doesn't appear in live view. When I preview in browser, Safari layout looks great, but text doesn't appear. In firefox, text appears, but layout is a mess.
Here is the code from the editable region to which I am trying to add text:
<!-- TemplateBeginEditable name="main_content_area" -->
<div id="site_layout_contentmain">Content for id "site_layout_contentmain" Goes Here</div>
<!-- TemplateEndEditable --></td>
ANY help is GREATLY appreciated!!!!!MHarvey2001 wrote:
Yes, the design is appearing to pull apart when I add content, but only in the Firefox preview.
If it pulls apart in Firefox, chances are it pulls apart in all browsers when text size is increased.
The problem with Photoshop code is that it is a) rigid, b) unstable and c) invalid.
To illustrate, run your code through the on-line validation tools below.
CSS - http://jigsaw.w3.org/css-validator/
HTML - http://validator.w3.org/
Photoshop is OK for designing quick comps to show the client but they won't hold up on a real site.
IMO, the benefits of starting over far outweigh the inconvenience.
HTML & CSS Tutorials - http://w3schools.com/
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com/ -
Cannot add layers/tables to an editable region
I created a template the other day, and then created pages
from that template. The main editable region which was meant to be
for all my info, pictures, wont let me add layers or tables to
position my text/images.... Have I missed something here?
\RobertYes, there would be no restriction on what you can place in
that editable
region. But I don't like the way you have started with this
page. Layers
should not be used as a primary layout methodology....
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
==================
"the full monty" <[email protected]> wrote
in message
news:epqp0m$lrc$[email protected]..
> This is the code: The whole of the layer region should
be editable... ie.
> be
> able to add layers/tables to position text?
>
> <!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=iso-8859-1" />
> <!-- TemplateBeginEditable name="doctitle" -->
> <title>Untitled Document</title>
> <!-- TemplateEndEditable -->
> <!-- TemplateBeginEditable name="head" --><!--
TemplateEndEditable -->
> <style type="text/css">
> <!--
> #Layer1 {
> position:absolute;
> left:382px;
> top:30px;
> width:329px;
> height:268px;
> z-index:1;
> }
> -->
> </style>
> </head>
>
> <body>
> <div id="Layer1"><!-- TemplateBeginEditable
name="EditRegion1" --> <!--
> TemplateEndEditable --></div>
> </body>
> </html>
>
> \Robert
> -
Copying html contents to editable region
hi all,
is there an easy way to convert simple html files (with some text and images, nothing fancy) to editable regions of a template? I have one template with only one editable region and I want to apply this template to all files in that folder.
many thanks
alperCreate a new page from Template (child page).
In code view, copy and paste just the relevant markup from HTML file to Editable Region of child page.
Save As some-filename.html
Repeat with other files.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com -
Templates in DW CS5.5 and editable regions
I have a template page that has an editable region defined as follows:
<div class="sidebar1">
<nav>
<ul>
<li><a href="#">Home</a></li>
<li><a href="#"></a></li>
<li><a href="#"></a></li>
<li><a href="#"></a></li>
<li><a href="#">Members Only</a></li>
<li><a href="#"> Gallery</a></li>
<li><a href="#">Constitution</a></li>
<li><a href="#">Links</a></li>
</ul>
</nav>
<!-- InstanceBeginEditable name="all" -->
</div>
<!-- end .sidebar1 -->
<article class="content">
<h1>BCEF Clubs</h1>
<section>
other code goes here
</section>
<!-- InstanceEndEditable -->
Note the </div> tag after the start of the editable region. This is a proper tag, as it is needed to close the sidebar1 div.
When it is not in an editable region, the </div> does not show up in yellow in design veiw and it works in every repect.
When the editable region is introduced, the </div> shows yellow in design view, and it works in every respect.
It validates using the W3C validation page.
Pages built with it also show the tag as yellow but they do not display it when live or in a browser.
If I delete the </div> as dreamweaver suggests, the css breaks and the page will not work.
It seems that DW thinks that this is an illegal tag. If I click my mouse on the <!-- InstanceBeginEditable name="all" --> tag, and collapse the tag, all the code in the editable region + that in the sidebare 1 div, ( even that before the editable region begins) collapses. The editable region does not allow edits in the sidebar1 code outside the region.
I need to put the editable region within part of the sidebar 1 div so that I can add aditional floated items in the sidebar 1 div if needed later.
Is this a bug or am I missing something?This would make more sense.
</nav>
<!-- InstanceBeginEditable name="sidebar1" -->
<p>Some unique sidebar1 content goes here</p>
<!-- InstanceEndEditable -->
</div><!-- end .sidebar1 -->
<article class="content">
<!-- InstanceBeginEditable name="content" -->
<h1>Unique heading here</h1>
<section>
other code
</section>
<!-- InstanceEndEditable -->
</div> <!--end .content-->
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
Message was edited by: Nancy O. Forgot to close the .content div.
Maybe you are looking for
-
An error occurred while configuring your server
The following actions failed or were not attempted: Configuring network Starting push notification server. DNS is killing me. I am an accountant. I have a new out of the box mac mini server. I want clients (real people with pcs and macs) to have exte
-
Change default calendar in iCal?
I have two google calendars which sync properly with iCal. However, the wrong calendar is on top (listed alphabetically). When I enter a new event from iCal, the default is to go to the wrong calendar. How can I switch them, or convince iCal to only
-
Suddenly, with iTunes 11.1.4, my iPhone 5S (iOS 7.0.4) disconnects from my Win7 PC when I select "Trust." When I plug it in I can hear the tone of a device being plugged in, but when I select "Trust" (haven't seen this dialog box...ever?) I hear the
-
SELECT-OPTIONS in WHERE condition
Hi All, SELECT-OPTIONS : S_TCODE FOR TSTCT-TCODE. START-OF-SELECTION. SELECT * FROM TSTCT INTO TABLE IT_TSTCT WHERE TCODE = S_TCODE. The same code results in SYNTAX ERROR in 4.7c. In ECC 6.0, no such error resulted, but SUBRC is 4. Why i
-
Cannot display Thai. character in List box elements
Hi all, I have set the Fonts to Ms San Serif to all items in a form, all items seems can display Thai. character correctly. For List box, it can display Thai also, but the elements in the selections cannot. Does any expert know how to fix this ? Than