darkelfpoet
Programmer
Hi 
I've been set with a task here of upgrading our existing website to use Dreamweaver templates. We support multiple different websites from many different organizations - every website follows a common look & feel standard, but is also quite different in some regards. In addition, every page appears in two different languages (English & French).
My solution to this was DW nested templates, where I create a single, top-level template followed by two language dependant templates, followed by site-specific templates (one for each language) followed by possibly sub-site specific templates (again one for each language).
All the existing files are within a common root folder and are in different directories based on sites/subsites. We have DW site connections which are imported into DW in order to faciliate connecting new employees to the websites.
What I'd like to do is set this up so that each site can track its own two templates (most likely by having it in its own Templates folder) so that creating new pages is easy (via File > New > from Template). This also involves putting the top level templates into the site root /Templates folder.
My first problem was that DW refused to nest the templates properly - my work around was to manually edit the TemplateInfo tag to find the template in a subdirectory instead of in /Templates (ie ../../Templates/templatename.dwt).
However, after that I ran into a larger problem which is that the changes made in the top level template won't cascading properly into the sites - it will update the site's DWT file but it will not cascade into its instance files.
Does anybody have a workaround or a solution for this? My other options do include putting all the template files in the site root, but this seems a bit messy (though the updates work properly). Another solution that has been suggested is using the library to keep track of multisite code and use only a single level of templates.
I've been set with a task here of upgrading our existing website to use Dreamweaver templates. We support multiple different websites from many different organizations - every website follows a common look & feel standard, but is also quite different in some regards. In addition, every page appears in two different languages (English & French).My solution to this was DW nested templates, where I create a single, top-level template followed by two language dependant templates, followed by site-specific templates (one for each language) followed by possibly sub-site specific templates (again one for each language).
All the existing files are within a common root folder and are in different directories based on sites/subsites. We have DW site connections which are imported into DW in order to faciliate connecting new employees to the websites.
What I'd like to do is set this up so that each site can track its own two templates (most likely by having it in its own Templates folder) so that creating new pages is easy (via File > New > from Template). This also involves putting the top level templates into the site root /Templates folder.
My first problem was that DW refused to nest the templates properly - my work around was to manually edit the TemplateInfo tag to find the template in a subdirectory instead of in /Templates (ie ../../Templates/templatename.dwt).
However, after that I ran into a larger problem which is that the changes made in the top level template won't cascading properly into the sites - it will update the site's DWT file but it will not cascade into its instance files.
Does anybody have a workaround or a solution for this? My other options do include putting all the template files in the site root, but this seems a bit messy (though the updates work properly). Another solution that has been suggested is using the library to keep track of multisite code and use only a single level of templates.