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

Similar Messages

Can't make comments editable on template child pages

Is there a way to make comments editable on template child pages. When making editable regions, comments are not included. I need to make comments editable on child pages. How do I do this.
Thank you,
Jim

Open your Template.dwt file. Add an editable region around your comments section.

<p>Comments go inside here...</p>
<p>Comments go inside here...</p>

Save your template. Allow DW to update your child pages.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Cannot create editable region on php page

I was successful on the html page; to select the text and create editable region.
But when I select the same text on the php page; I get the error message: "Selection is outside the body tag. Select the text inside the body tag."
www.ndccalliance.org/resource.php
www.ndccalliance.org/resource.html
What am I doing wrong?
Thank you.

Hello JudyEllis,
Take a look at the output source code for your PHP page when viewed in the browser. You actually have multiple nested opening and closing HTML and body tags in your page. It appears maybe you're using includes, for instance with your header and footer, but your include files are entire HTML documents, not just the chunks of code you need.
Best regards,
Corey

Editable Regions Across Multiple Pages

Is it possible to create an editable region in a template
that when edited would update all the pages within a website? For
example, I am working on a website for a symphony. They want their
upcoming events listed on the sidebar of each page and want to
update this information frequently. But, they have over 50 pages.
Any suggestions?

I'm afraid that will make a mess. The entire body contents
will be placed
in the right editable region....
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
==================
"amadas" <[email protected]> wrote in
message
news:ea9i2c$i1t$[email protected]..
> Hi cbteel,
>
> I have a solution for you. Not sure if you are still
looking for?
>
> You should be having Dreamweaver to do this.
>
> Follow the steps below to create a new template:
>
> 1. Launch Dreamweaver
> 2. File->New->Template Page, Choose HTML Template,
click Ok
> 3. Insert->Table, 1 Row and 2 columns. Adjust the
size of the row and
> column accordingly so that you would see the first
coulmn to show the size
> of
> your upcoming events..
> 4. In Column1, click and Insert->Template
Objects->Editable Region,
> name it
> and click ok
> 5. In Column2, click and insert->template
objects->Editable Region,
> name it
> and click ok
> 6. Save the template (.dwt) file in your site.
> 7. Open all the 50 html pages in Dreamweaver and choose
one by one.
> 8. Modify->Template->Apply Template to this Page,
> 7. This will open up Mapping dialogue. Map the Body to
Right Site
> editable
> region as you want and save the html pages.
>
> Hope this helps.
>
> Thanks
> Arun (Contribute Team)
>

Editing in a non editable region in web page

After tiding up my site, (removing spaces etc in files names)
my links on the nav page did not work to the next page.
They are in a locked template area so i opened the template
up and changed them, but they do not update the pages based on the
template ? Will it because I changed my web page names (took out
the spaces)
How do i get them to update, either by putting the new file
names in the template or unlocking the locked template area and
manually putting in the new link names to the other pages ?

Please go to SITES | Manage Sites..., select the site name,
and click on
Edit. Click on the Advanced tab at the top. Tell me the
following -
Under LOCAL INFO
The contents of "Local root folder:"
It appears that your site is improperly defined. Your links
look like
this -
<a href="../webpages/index.htm"
and I'm betting that "webpages" is the name of the root
folder of the site.
There's no way that your template (or any page, for that
matter) should
contain the name of the root folder in any link to any file.
I believe you would be better advised to start over with a
fresh site
definition, honestly.
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
==================
"grahamdvddvd" <[email protected]> wrote in
message
news:[email protected]...
> hi this is part 1 of it
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN"
> "
http://www.w3.org/TR/html4/loose.dtd">
> <html>
> <head>
> 
> <title>index</title>
> <meta
http-equiv="Content-Type"
> content="text/html; charset=iso-8859-1">
> <link href="../stylesheet.css" rel="stylesheet"
type="text/css">
> <script language="JavaScript"
type="text/JavaScript">
> 
> </script>
> 
> <style type="text/css">
> 
> </style></head>
>
> <body class="backgroundgrey"
>
onLoad="MM_preloadImages('../buttons/buttons2_r1_c1_f3.gif','../buttons/buttons2
>
_r1_c1_f2.gif','../buttons/buttons2_r1_c2_f3.gif','../buttons/buttons2_r1_c2_f2.
>
gif','../buttons/buttons2_r1_c3_f3.gif','../buttons/buttons2_r1_c3_f2.gif','../b
>
uttons/buttons2_r1_c4_f3.gif','../buttons/buttons2_r1_c4_f2.gif','../buttons/but
>
tons2_r1_c5_f3.gif','../buttons/buttons2_r1_c5_f2.gif','../buttons/buttons2_r1_c
>
6_f3.gif','../buttons/buttons2_r1_c6_f2.gif','../buttons/buttons2_r1_c7_f3.gif',
>
'../buttons/buttons2_r1_c7_f2.gif','../buttons/buttons2_r1_c9_f3.gif','../button
>
s/buttons2_r1_c9_f2.gif','../buttons/buttons2_r1_c11_f3.gif','../buttons/buttons
> 2_r1_c11_f2.gif')">
> <table width="100%" border="0" cellpadding="0"
cellspacing="0"
> class="backgroundgrey">
> <tr>
> <th scope="col"><p
class="backgroundgrey">mmuk</p>
> <table width="680" border="0" cellspacing="0"
cellpadding="0">
> <tr>
> <th height="108" colspan="6" scope="col"><div
align="center"><img
> src="../images/logo.jpg" width="680" height="100"
border="1"></div></th>
> </tr>
> <tr>
> <td colspan="6"><table border="0"
cellpadding="0" cellspacing="0"
> width="680">
> 
> <tr>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="76" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="75" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="76" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="75" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="76" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="75" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="76" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="74" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="1" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="76" height="1" border="0"></td>
> <td><img src="../buttons/spacer.gif" alt=""
name="undefined_2"
> width="1" height="1" border="0"></td>
> </tr>
> </table></td>
>

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
alper

Create 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

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

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

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

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

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

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

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

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]

Open a QT movie in editable region of page (template)

I am using templates for my site. I'd like a movie link to open in a dependent page in the editable region of the page if possible. Can't seem to make it happen. The movie always opens in its own blank page.

Did you embed a QT Player on the page?
http://www.mediacollege.com/video/format/quicktime/streaming/
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Ap divs in editable regions

Hi, I have a site using several pages from templates. I have
3 different templates used for groups of different pages. In the
editables regions of my pages, I have several ap divs, depending on
page content. All looks fine until I update a template. After that,
all the ap divs turn into boxes with a dotted outline that fits
across the ed region.
No matter which template I update, the ap divs in their
associated pages disappear and wreak havoc with the layout in my
editable regions. My updates dates can be as simple as adding a
button or or enlarging the edit regions. Each time I have to
re-layout my edit regions.
Do you if this is a bug or am I just doing something wrong?
Any help would be greatly appreciated.

> Do you if this is a bug or am I just doing something
wrong? Any help would
> be
> greatly appreciated.
I am pretty sure we can find the answer by looking at your
code. Can you
show us one of the child pages on which this trouble occurs
by posting a
link to the page?
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
==================
"Fran in Brig" <[email protected]> wrote in
message
news:gqbl2f$eml$[email protected]..
> Hi, I have a site using several pages from templates. I
have 3 different
> templates used for groups of different pages. In the
editables regions of
> my
> pages, I have several ap divs, depending on page
content. All looks fine
> until
> I update a template. After that, all the ap divs turn
into boxes with a
> dotted
> outline that fits across the ed region.
>
> No matter which template I update, the ap divs in their
associated pages
> disappear and wreak havoc with the layout in my editable
regions. My
> updates
> dates can be as simple as adding a button or or
enlarging the edit
> regions.
> Each time I have to re-layout my edit regions.
>
> Do you if this is a bug or am I just doing something
wrong? Any help would
> be
> greatly appreciated.
>

Remove editable region *and* propagate?

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

Removing the editable region markup should certainly render
that region
uneditable in the child pages. Something is preventing that
from happening.
Can you show me the child page after removing the markup and
tell me which
region you are deleting?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"idRatherBeOutside" <[email protected]>
wrote in message
news:e4e3s6$j23$[email protected]..
> Hi all,
>
> I have an editable region in a template which I would
like to make
> uneditable.
> I can remove it in the template, but the change does not
seem to propagate
> to
> the child pages. In other words, the region is still
editable on the
> child
> pages after I apply the changed template. Is there a way
to do this or am
> I
> outta luck here?
>
> Thanks!
>

Site with editable regions won't allow editing

Hi, I have set up multple sites for InContext Editing. All works fine except this last one that won't allow editing online. When clicking "Edit Page" I get a message saying "There are no editable regions." I have checked and double checked the pages and the regions are there. I've reflowed the content into all pages (template) but I still get the same message in InContext.
Please help me figure out what's wrong and how I can get the pages editable.
Here's a link to the website http://www.nolimithockey.com
Let me know if you need anything else in order to help me figure this out.
Thanks a bunch!
Hanna in Tahoe

i'm done, thank you
2009/10/19 Dan POPA <[email protected]>
>
InContext Editing can edit only the elements having the ice:editable
attribute set.
Your page should contain something like this:
>

<div ice:editable="*">
some editable content here
</div>
>
But there are no such elements in the
http://www.nolimithockey.com/index.html page.
>
You say you can see the ICE regions in that page so I can only assume that
you didn't upload the file on the FTP server and you are looking at your
local version of the file, not the one from the server.
>
Another possibility is that you mistakenly treat Dreamweaver Template
Editable Regions as InContext Editable Editable Regions.
I can see that there are DW editable regions in your page: the elements
located between the  comments.
>
>
You can create ICE editable regions by selecting in Dreamweaver an element
and applying the Create Editable Region command under the DW menbu Insert ->
InContext Editing menu, see the image:
>
http://forums.adobe.com/servlet/JiveServlet/download/2242-505554-2323206-23866/create_ice_ er.png
>
Please let me know if any of these were of any help to you,
Regards,
Dan Popa
>

Editable Regions and Templates -- Problem in IE

Hello,
I have a template that I use throughout my site. The template
includes
the Spry Menu Bar and three editable regions. The pages all
look great
in Firefox. But in IE6 and IE7, there is a problem--white
space
vanishes and the text is too close to the objects above it.
Specifically, The <h3>Page
Title</h3>appears to close underneath
<td>. It's fine in
Firefox, however.
Any help is greatly appreciated.
Thank you,
=====================
Here's the code.
<style type="text/css">

</style>
</head>
<body text="#333333"
vlink="#333333" alink="#333333"
leftmargin="0"
topmargin="0"
marginwidth="0"
marginheight="0">
<TABLE width="800" border=0
align="center" cellpadding=0 cellspacing=0
bgcolor="#FFFFFF">
<TBODY>
<tr>
<td
width="2%">&nbsp;</td>
<td width="96%"><img
src="../SpryAssets/mainnav_logo.jpg"
/></td>
<td
width="2%">&nbsp;</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>
<h3>Page Title</h3>
</td>

TEST BED:
I shrinked my test site to just 1 photo page with only 3 pictures and I I published it to a folder:
Safari 3.1.1 has no problems
Mozilla Firefox 2.0.0.2 has no problems
Opera 9.5 has no problems
IE 7.0.5730.13 cannot render any picture !!!!
DEEP DIVE:
IE fails and if "notifications" are turned on complains about run time error "Error: Access Denied" on line 504 of a script. I went deeper and using the Microsoft Just in Time Debugging features apparently the offending javascript is "iWeb - iWebSite.js" with an ajaxRequest called "req.open('GET',url,true)"
iWEB on LEOPARD is no better
I booted with an external disk using Leopard and I used iWeb just 1 photos page
no way IE still complains (so far I am using Mac Tiger level)
HOW CAN YOU HELP
To those of you who succeeded with iWeb+IE (and have time to lend) I can send the zipped 2MB actual iWeb "package" named "Domain.site2" used by my iWeb to save the site under editing before any publishing.
you temporarily rename your "Domain.site2" + substitute it with my "Domain.site2" + start iWeb and see if you can publish/see it correctly.
Please send me a private mail if you think you can help.
Seriously thinking of dumping iWeb...
RAN

Editable region

Help! Is there a way to limit an editable region to a fixed size?
I have a pretty simple design sliced into four pieces: Header, horizontal navbar, main body, footer. I've made the mainbody into an editable region. But if I add more text that the exact size of the mainbody divtag, my page breaks apart wehre the mainbody and footer meet.
I have gone into CSS and typed in the height dimension in the div (#wrapper #mainBody #mainContent), but it didn't make a difference. When I added it to the paragraph div (#wrapper #mainBody #mainContent p), the type went crazy.
I've spent hours trying to work this out. I'm now considering just working around this -- ie, inserting content until I see the page breaks up. But there must be a simpler and safer method to do this.
Many thanks to anyone who can help. CSS and HTML coding is below:
@charset "UTF-8";
    padding: 0px;
    margin-top: 0px;
    margin-right: auto;
    margin-bottom: 0px;
    margin-left: auto;
#wrapper {
    background-color: #999;
    width: 800px;
#wrapper #header {
    background-color: #999;
    height: 150px;
    width: 800px;
#wrapper #navBar {
    height: 50px;
    width: 800px;
    background-image: url(../template%20images/navBar.jpg);
    margin: 0px;
#wrapper #mainBody {
    height: 990px;
    width: 800px;
    background-image: url(../template%20images/body.jpg);
#wrapper #footer {
    background-image: url(../template%20images/footer.jpg);
    height: 60px;
    width: 800px;
#wrapper #mainBody #mainContent {
    padding-top: 25px;
    padding-right: 80px;
    padding-bottom: 0px;
    padding-left: 80px;
    margin-bottom: 0px;
    font-family: Arial, Helvetica, sans-serif;
    font-size: 14px;
    height: 965px;
#wrapper #mainBody #mainContent p {
    height: 0px;
    margin: 0px;
#wrapper #footer #pageNumber {
     font-size: 18px;
     font-weight: normal;
     padding-top: 10px;
     text-align: center;
     font-family: Arial, Helvetica, sans-serif;
HTML:
<body>
10
<div id="wrapper">
<div id="header"><img src="template images/header.jpg" width="800" height="150" alt="project name" />
</div>
<div id="navBar">
<ul id="MenuBar1" class="MenuBarHorizontal">
    <li><a href="#">home</a>      </li>
    <li><a href="#">about</a></li>
    <li><a href="#">menu</a></li>
    <li><a href="#">contact</a></li>
    <li><a class="MenuBarItemSubmenu" href="#">index</a>
      <ul>
        <li><a class="MenuBarItemSubmenu" href="#">Homeland</a>
          <ul>
            <li><a href="#">submenu</a></li>
            <li><a href="#">submenu</a></li>
          </ul>
        </li>
        <li><a href="#" class="MenuBarItemSubmenu">subject here</a>
          <ul>
            <li><a href="#">submenu</a></li>
          </ul>
        </li>
        <li><a href="#">submenu</a></li>
      </ul>
    </li>
</ul>
</div>
<div id="mainBody">
<div id="mainContent"> 

<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed nisl metus, aliquam et ultricies vitae, faucibus ut libero. Fusce molestie lectus nunc, vel interdum leo. Nunc gravida mattis leo, a laoreet felis tincidunt eget. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Donec et sapien in felis consequat vestibulum eu ac felis. Praesent pellentesque dolor vel mi euismod eget ultrices velit dignissim. Duis erat urna, aliquam vel malesuada eu, sollicitudin vel ante. Maecenas vitae dui nisi, ac molestie dolor. Suspendisse non neque odio, et dapibus lacus. Pellentesque bibendum justo non turpis tempor a porta risus pharetra. Etiam a felis quis orci molestie aliquet. Phasellus aliquam lacus sed magna venenatis et accumsan justo blandit. Sed id velit turpis. Nunc sit amet placerat libero. Nam sollicitudin, sem ut sollicitudin convallis, dolor tellus volutpat risus, quis lacinia diam purus nec tellus. Quisque at purus euismod lorem semper rhoncus. In hac habitasse platea dictumst. </p>
   </div>
</div>
<div id="footer">
<div id="pageNumber">
<p><< Previous Page 1 : 2 : 3 Continue >></p>
</div>
</div>
</div>
<script type="text/javascript">

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

Nancy and Paul,
Many thanks for the quick reply.
To clarify, I am building a website that will feature a series of essays, so the content is very text heavy. There will be a photo and occasional graphic to break up the text on each page, but otherwise it's just words, words, words. Even with such a large display space (ie, the mainContent <div>, 800x990 px), these essays will run two to five pages long.
I have not yet gone live, so I cannot post a link. However, I've attached a jpg of the prototype:
As you can see, I've used a non-repeatable textured background. Hence my problem: The type that I fit into the mainContent cannot run longer than what the <div> allows, as the main content section will not expand. Rather, text runs off the maincontent section and the design breaks where the footer begins (page number at the bottom). I was fooling around with the height rule in a failed effort to create a bottom margin or padding that would stop the type from overflowing.
So, is there a way I can still work with this? Or as Nancy suggested, is my design too regid for the web?
Thank you again for your help. I am brand new to webdesign, and am rather befuddled at the moment....
PS to Gary: The mainContent <div> created a container that gave me my left, right and top padding for the text and photos. (The mainBody <div> margins ran into the black margins on both sides and up to the navBar at the top.) I had hoped the same <div> would set the bottom padding, too, but it didn't work.

Problem editing text color and page properties due to favicon link

I recently added a link to a sites favicon using the link tag. Following advice on the net this was added beneath the HTML tag and before the HEAD tag. I was using a Dreamweaver template for the site and it updated all pages with the new link in the non-editable area above HEAD and just after the template declaration.
This was fine, unitl the user went to edit the site. He found that he could no longer get to page properties as he got an error that no page properties existed in editable areas... although there was an editable region for the page title. Also text color and highlighting were now disabled.
Moving the link tag into the head area has resolved the editing issue, but it seems a strange bug. Is there some way to add something between HTML and HEAD and have it appear before the InstanceBegin of the template?

You can edit text in any PDF by using trial version but as for as my knowledge and limited experience with Adobe I could not find any text color option in Adobe Acrobat. But you can highlight text in Adobe Acrobat. If you want to change the text color in PDF, I would like to recommend some another software which allows you to change the color of text and is available for download here.
Let me tell you how can change text color using this software. Open PDF file > go to "edit tab" > Click "edit" then highlight text to change the color. As you can see in the below screenshot.
Free free to ask. Hope it helps you. Don't forget to come back to share your views.
Thanks

Editable regions in child page

Similar Messages

Maybe you are looking for