Link to home
Start Free TrialLog in
Avatar of rascal
rascalFlag for United States of America

asked on

Dreamweaver template designations changed?

I am using Dreamweaver MX 2004 and built a site using templates. Whenever I created a new page, the template location was created by Dreamweaver using a relative path as such:

<!-- InstanceBegin template="../../Templates/01_top.dwt.asp"-->

All seemed to be ok during development, but lately when I try to "open attached template", dreamweaver tells me there is an error in the path.

So I tried creating a new page based on the template and now I see dreamweaver define the template location as a virtual path such as:

<!-- InstanceBegin template="/Templates/01_top.dwt.asp"-->

What happened to cause this?

I didn't change my directories, my site definition, my anything. This may be related to another problem I am having where Dreamweaver no longer knows which pages belong to my template. (i.e. I update the template non-editable area and DW only updates a couple pages. In fact it only lists a couple pages as being candidate for update!)

Anyway, I left another question for the issue of not updating all the pages, but would like to know what's going on with the location specification described above. Perhaps it will clue me in on how to fix the other issue as well. (i.e. perhaps DW needs to re-index all the pages belonging to the template.... is there a way to do this?)

Thanks for any help!

Mark
SOLUTION
Avatar of rockmansattic
rockmansattic

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rascal

ASKER

I arrived at a fix. I did 2 things in this fix so I don't know which one really fixed it:

1) I updated my Dreamweaver from 7.0 to 7.01
2) I deleted my site profile for the site I was working on and re-imported the site definition from a previously saved export of the site definition.

Thereafter all pages were recognized.

I wish I had done one or the other first to see which one fixed it, but I'm just happy to be running normally again.

Thanks for all your help!

Mark
Glad to hear you're up & running.