I have a template that is having problems to update all the pages built with
the template. When I edit > save > Update template used in these files,
everything looks fine- the updates log shows that it has updated 12 of 12
pages, BUT, when I check the pages, they won't have the changes made. Here are
some things that I have being trying:
1. When I created each page based on the template - In the new document log >
page from template, I checked the option "update page when template changes"
2. I tried changing the area that I edited (Menu Botons) to repeat region,
then to editable region, and so on... But the problem persist.
3. I chose modify > Templates > Apply Template to page.... and nothing.
4. I re-read the DW Help, tutorials and watch the adobe videos on this
topic...
If somebody can tell me what I might be doing wrong, I will appreciate your
help

first question: Are you uploading the changed local files to the remote
host?

Templates only affect LOCAL files. You have to upload the changed files to
show the changes on the hosted site.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/

No. I'm not uploading the website yet. Everything is done on my local files
because I want to finish the layout and settings before I upload the website.
Let me ask you: Do you mean that I won't be able to see changes in DW local
files?

> Do you mean that I won't be able to see changes in DW local
> files?

No, he doesn't mean that.

Here are seven common mistakes that will result in changes not propagating
from Template to child -

1. Rename the Templates folder
2. Move the Templates folder to some other folder level in the site other
than root level
3. Move a template out of the Templates folder.
4. Make changes to an editable region of the template (which will not
propagate)
5. Assume that template changes can be uploaded to the server without also
uploading the changed local files
6. Corrupt the site cache so that the link between template and child page
is broken
7, Improperly create your child pages by simply opening the template,
adding page specific content, and resaving the template with an *.html
extension rather that its *.dwt extension. (you can tell if this is the case
by looking at the code on a child page - if you see anything like <!--
TemplateBeginEditable... then this is what you have done). If you *have
done this*, then recreate the child pages (in DWCS3) using FILE | New > Page
from Template, select the template and click CREATE.

The 6th problem can be repaired by using SITE | Advanced > Recreate Site
Cache, and the six others can be fixed by just not doing them. Have you
done any of those?

Or, read this -
http://www.adobe.com/go/dd83ba8b


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


"Pablo163" <webforumsuser@macromedia.com> wrote in message
news:g7v6v6$rb3$1@forums.macromedia.com...
> No. I'm not uploading the website yet. Everything is done on my local
> files
> because I want to finish the layout and settings before I upload the
> website.
> Let me ask you: Do you mean that I won't be able to see changes in DW
> local
> files?
>

The region of the template that I'm changing was originally editable region,
but when I was trying to fix the problem, I changed it to repeating region and
also optional region. Since I still have the problem, I'm back to editable
region. Now, I see that a common mistake #4 is having changes in a editable
region. What should I do if I need that region to be editable but at the same
time I need it to be able to make the changes in all the pages related to the
template?

> What should I do if I need that region to be editable but at the same
> time I need it to be able to make the changes in all the pages related to the
> template?

The above sentence states two contrary things.

If that area is a locked area in the template, not an editable region, then
to edit it you open the Template, edit it, and the changes propagate to all
the child pages when you save it.

If you need that area to contain different things on different pages, then
it has to an Editable region, so you can alter the section's contents in the
individual pages.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/

Let me give you a detail example of what I mean. The design has a menu in the
left side made of image/buttons. In the template, they are all in gray color
and I indicated a swap image of the buttons in blue, BUT, I need that area
editable because I want to indicate for the viewers, that they are in a
specific topic when they see a different static blue button on each page while
the other buttons still in gray. Here is a link of one website (nott mine) with
a side menu similar to what I want: http://www.cdhcpa.com/about_us/
I originally tried to do this with code and with Spry, but It looks different
in every browser, specially IE and I already spend too many weeks trying to
solve code problems - its a Nightmare, thats why I'm doing the buttons with
images....

> BUT, I need that area
> editable because I want to indicate for the viewers, that they are in a
> specific topic when they see a different static blue button on each page

You can do that with css or javascript that is outside of that area, in an
editable section in the document's head for example.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/

Since I originally tried to do this with CSS and could not do it... and the way
I'm doing it now (manually with swap images) seems to be impossible, I think
that my next questions should be:
1. Is there's a step by step instruction about this somewhere? I already read
DW help, a tutorial and DW videos, but did not found solution to this specific
task.
2. Do you know if there's a service in which people could send a project
with an specific problem and we pay for the fix, so we can continue with the
rest. In my case after many weeks on this, I'm burn out....and very
frustrated....

> 2. Do you know if there's a service in which people could send a project
> with an specific problem and we pay for the fix, so we can continue with
> the
> rest. In my case after many weeks on this, I'm burn out....and very
> frustrated....
>

You can contact me offlist if you'd like to discuss a contract to complete
this project - please use "forums at great-web-sights.com" as an email
address (please replace the " at " with "@").

> Since I originally tried to do this with CSS and could not do it... and
> the way
> I'm doing it now (manually with swap images) seems to be impossible

The thread has actually touched on several different things - can you
describe what specific thing you are referring to here, please? And if it's
the issue where you want to indicate to the user which button they just
clicked on to get to the current page, that is done very simply using CSS.
As we have been saying all along, we need to see your page's code to make
specific suggestions to you.

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


"Pablo163" <webforumsuser@macromedia.com> wrote in message
news:g81ca5$auc$1@forums.macromedia.com...
> Since I originally tried to do this with CSS and could not do it... and
> the way
> I'm doing it now (manually with swap images) seems to be impossible, I
> think
> that my next questions should be:
> 1. Is there's a step by step instruction about this somewhere? I already
> read
> DW help, a tutorial and DW videos, but did not found solution to this
> specific
> task.
> 2. Do you know if there's a service in which people could send a project
> with an specific problem and we pay for the fix, so we can continue with
> the
> rest. In my case after many weeks on this, I'm burn out....and very
> frustrated....
>