Table Hassle - Macromedia Dreamweaver

Sounds like you are talking about Templates... Make a template and then
create new pages from it. When you change anything in the template page,
all the children change as well...

Is that what your talking about?

Gary
"neil.pb" <webforumsuser@macromedia.com> wrote in message
news:gb2rlt$idu$1@forums.macromedia.com...
> Hi everyone, i've made a few websites out of tables, but my main problem
> is
> after im finished if i want to change something in the layout i have to
> edit
> every page singularly. When first making a site is there a way to set some
> cells as permanent with only one cell changing as the page changes? Like
> the
> way when using frames you can open pages in a certain frame?
>
> Thanks, Neil
>

Yeah i think so. I want all my pages with the same layout but with different
content, but if i want to change the layout i only have to change one page not
evryone. So do i design my oage with tables and then just go save as template?

That would be one way to do it. FILE | Save As Template....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"neil.pb" <webforumsuser@macromedia.com> wrote in message
news:gb55ju$cj3$1@forums.macromedia.com...
> Yeah i think so. I want all my pages with the same layout but with
> different
> content, but if i want to change the layout i only have to change one
> page not
> evryone. So do i design my oage with tables and then just go save as
> template?
>

"neil.pb" <webforumsuser@macromedia.com> wrote in message
news:gb55ju$cj3$1@forums.macromedia.com...
> Yeah i think so. I want all my pages with the same layout but with
> different
> content, but if i want to change the layout i only have to change one
> page not
> evryone. So do i design my oage with tables and then just go save as
> template?

As Murray said...

But first, define the areas you want to make editable and non-editable in
the child pages.

1/ Non-editable: non-changeable content. This only updates on the child
pages when the content of the non-editable region is changed on the
template.
2/ Editable: changeable content. This is for adding content to new child
pages and changing / updating editable content on the child pages.

Remember to create all new pages from the template... or else the template
will have no effect.

You can also save a template child as a new file and the template will
affect that page. (Someone please correct me if i am wrong on this score.)

> But first, define the areas you want to make editable and non-editable in
> the child pages.

Actually, it doesn't matter when you do this - either before, or after using
the FILE | Save as Template... option.

> Remember to create all new pages from the template... or else the template
> will have no effect.
>
> You can also save a template child as a new file and the template will
> affect that page. (Someone please correct me if i am wrong on this score.)

This is a bit confusing - are you saying that you spawn a child, add new
content, save as child1, then change the content, and save again as child2,
etc.? If so, then that's correct.

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


"Jay Jhabrix" <jhabrix@gmail.com> wrote in message
news:gb5gn8$oko$1@forums.macromedia.com...
> "neil.pb" <webforumsuser@macromedia.com> wrote in message
> news:gb55ju$cj3$1@forums.macromedia.com...
>> Yeah i think so. I want all my pages with the same layout but with
>> different
>> content, but if i want to change the layout i only have to change one
>> page not
>> evryone. So do i design my oage with tables and then just go save as
>> template?
>
> As Murray said...
>
> But first, define the areas you want to make editable and non-editable in
> the child pages.
>
> 1/ Non-editable: non-changeable content. This only updates on the child
> pages when the content of the non-editable region is changed on the
> template.
> 2/ Editable: changeable content. This is for adding content to new child
> pages and changing / updating editable content on the child pages.
>
> Remember to create all new pages from the template... or else the template
> will have no effect.
>
> You can also save a template child as a new file and the template will
> affect that page. (Someone please correct me if i am wrong on this score.)
>

"Murray *ACE*" wrote :
>> But first, define the areas you want to make editable and non-editable in
>> the child pages.
>
> Actually, it doesn't matter when you do this - either before, or after
> using the FILE | Save as Template... option.

True... once, it's a template and pages have been spawned off it... or pages
will be spawned off it... was just trying to simplify matters for the OP and
elaborate on what you said.

Hello! i just re-read what i wrote and what you said... if a change is made
to editable regions in a template (meaning the areas of editable and non
editable have changed) will it affect already created child pages? It
should...

>> You can also save a template child as a new file and the template will
>> affect that page. (Someone please correct me if i am wrong on this
>> score.)
>
> This is a bit confusing - are you saying that you spawn a child, add new
> content, save as child1, then change the content, and save again as
> child2, etc.? If so, then that's correct.

Yup, that's what i'm saying... what i meant was, in a typical workflow, you
dont't have to create each page from scratch. Assume you have a left nav
area in an editable region, you can create a new page from that and when the
template updates it'll change say, the header nav and footer content
automatically.

> Hello! i just re-read what i wrote and what you said... if a change is
> made to editable regions in a template (meaning the areas of editable and
> non editable have changed) will it affect already created child pages? It
> should...

Yes.

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


"Jay Jhabrix" <jhabrix@gmail.com> wrote in message
news:gbb9mo$s30$1@forums.macromedia.com...
> "Murray *ACE*" wrote :
>>> But first, define the areas you want to make editable and non-editable
>>> in
>>> the child pages.
>>
>> Actually, it doesn't matter when you do this - either before, or after
>> using the FILE | Save as Template... option.
>
> True... once, it's a template and pages have been spawned off it... or
> pages
> will be spawned off it... was just trying to simplify matters for the OP
> and
> elaborate on what you said.
>
> Hello! i just re-read what i wrote and what you said... if a change is
> made to editable regions in a template (meaning the areas of editable and
> non editable have changed) will it affect already created child pages? It
> should...
>
>>> You can also save a template child as a new file and the template will
>>> affect that page. (Someone please correct me if i am wrong on this
>>> score.)
>>
>> This is a bit confusing - are you saying that you spawn a child, add new
>> content, save as child1, then change the content, and save again as
>> child2, etc.? If so, then that's correct.
>
> Yup, that's what i'm saying... what i meant was, in a typical workflow,
> you
> dont't have to create each page from scratch. Assume you have a left nav
> area in an editable region, you can create a new page from that and when
> the
> template updates it'll change say, the header nav and footer content
> automatically.
>
>
>

Im not sure what you mean.

Ok, so i create my table, design my site, define the editable regions, save it
as a template. I then create a page (we'll call it template 1) from that
template (How? i know i can just go save as; template 1, but how do i create
from the original template so the two are connected?). Now that i have child1,
if i change an editable region in template, will it change automatically in
child1?

Thats what i want, if i change something in an editable region in the main
template i dont then have to change it manually in child1

1. Design the page
2. Build the layout in DW
3. Use FILE | Save as Template when complete
4. With the template file open, define the editable regions
5. Save the template again, and close it
6. Now use FILE | Page From Template, select this template's name, make
sure the update page checkbox is checked, and click CREATE
7. Add unique content to this child page, and save it
8. Repeat #6 and #7 until you have finished with the site

Like that.

> Thats what i want, if i change something in an editable region in the main
> template i dont then have to change it manually in child1

That's not how templates work. Changes to EDITABLE regions in the template
file do not propagate to child pages; that's only what changes to
NON-EDITABLE regions do.

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


"neil.pb" <webforumsuser@macromedia.com> wrote in message
news:gbgjtb$ih0$1@forums.macromedia.com...
> Im not sure what you mean.
>
> Ok, so i create my table, design my site, define the editable regions,
> save it
> as a template. I then create a page (we'll call it template 1) from that
> template (How? i know i can just go save as; template 1, but how do i
> create
> from the original template so the two are connected?). Now that i have
> child1,
> if i change an editable region in template, will it change automatically
> in
> child1?
>
> Thats what i want, if i change something in an editable region in the main
> template i dont then have to change it manually in child1
>