Can that be right? My website was working fine with a login based on php and
MySQL and I had an image changing using *.jpg. Then I found out about the use
of templates. So I designed a template and based my sites pages on that - now
nothing is working :0(
Can that be right? And can I use templates without having locked areas? The
template thing is great in terms of updating the design and I actually don't
need the option of making non-editable areas.

I would really appreciate some good advice here.
:0)
Lisbeth

> Can that be right? And can I use templates without having locked areas? The
> template thing is great in terms of updating the design and I actually don't
> need the option of making non-editable areas.

If there are no locked areas, there's no point in using a Template.



--
Alan
Adobe Community Expert, dreamweaver

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

On Tue, 5 Aug 2008 15:31:29 +0000 (UTC), "quma"
<webforumsuser@macromedia.com> wrote:

>Can that be right? My website was working fine with a login based on php and
>MySQL and I had an image changing using *.jpg. Then I found out about the use
>of templates. So I designed a template and based my sites pages on that - now
>nothing is working :0(
> Can that be right? And can I use templates without having locked areas? The
>template thing is great in terms of updating the design and I actually don't
>need the option of making non-editable areas.
>
> I would really appreciate some good advice here.
> :0)
> Lisbeth

If you don't think you need non-editable areas, then you don't
understand how templates work.

When you create a template, it's the NON-EDITABLE areas that are
common to all pages. When you update THOSE AREAS AND THOSE AREAS ONLY
in the template file, the changes propagate to all the child pages.

Changes made in the template to EDITABLE areas will NOT propagate to
the child pages.

Win
--
Win Day
Wild Rose Websites www.wildrosewebsites.com
windayNOSPAM@wildrosewebsites.com

Tak you for your replys.
As far as i have understood templates, there are two things they are usefull
for:
1. You can make a "dummy proove" homepage where the person who is editing the
page, only have access to edit in the regions you have made editable.
2. You can make the design as a template and make the rest of the pages from
that template, just with a different content of course. When you then want to
make changes to the design, you just edit the template and then update the
design of the other pages.
Have I misunderstood that?
The main php programming is before the head of the page based on a template -
could that cause problems to the php code?

:0/
Lisbeth

Ok, I now see I have definitely not made my template-planning structured
enough, but I still need to understand part 2 right:

>Next I create server-side include files containing all class 2 >elements and
place them on the template as needed. Note - >some of the class 2 elements may
be "section-specific elements", >and their placement on the template will be
subject to the next >item

Do you meen, next you create pages with the php code and save them as nested
templates or on the same main template... No sorry, I don't get it... Could you
descripe that in another way or you know of any step by step tutorial on that
topic? Pardon my newbieness :0)

OK - now SSI rings a bell to me :0)
But how about if a site needs to have a restricted area (php and MySQL),
you'll need a login page, some pages that are only viewable when authorised and
a logout funktion on one of these pages.
How to put that into a page created from a template?
On my php template I made a maincontent div tag that was editable inside the
body. Then I tried to make the login page build of that template. No problem
placing the login field inside the maincontent and I could make DW put the
right behaviours and php code on the top of the page. But it didn't work and
since I couldn't find the error elseware I "blamed" the template.
Would that be the right way to do it or would you use SSI in this situation?

:0)
Lisbeth

Well - again I can just say Dreamweaver (and Adobe support) is worth every penny it costs.
Thanks ;0) Liz