Project Sites & Site Templates
I have tried searching but not found advice on avoiding creating a new project site template from an existing site linked to an existing project. I recall advice from many years ago not to do this but cannot remember the reasons. Is my memory playing tricks with me or were/are there genuine reasons as to why this is not advisable?
In a similar vein I am working with an instance of Project Server where a large number of Site Templates and associated solutions have emerged over the past 8 years and I am concerned that different Site Templates have evolved from the original single source and that in turn new templates based upon earlier templates have had changes made that mean lists with the same name may not be configured the same. We are getting regular queue errors that columns cannot be found in site lists which suggests this is the case.
Would there be any way to correct this divergence across a population of sites?
Trying to understand where the divergence may have occurred is not helped by the fact that it is not possible to know the “parentage” of existing sites when viewing the sites and workspaces list – _layouts/15/mngsubwebs.aspx – as the majority of sites have no description which they would have from the template name or description provided when using the Save as Template options on the /_layouts/savetmpl.aspx page
I have tried searching but not found advice on avoiding creating a new project site template from an existing site linked to an existing project. I recall advice from many years ago not to do this but cannot remember the reasons. Is my memory playing tricks with me or were/are there genuine reasons as to why this is not advisable? In a similar vein I am working with an instance of Project Server where a large number of Site Templates and associated solutions have emerged over the past 8 years and I am concerned that different Site Templates have evolved from the original single source and that in turn new templates based upon earlier templates have had changes made that mean lists with the same name may not be configured the same. We are getting regular queue errors that columns cannot be found in site lists which suggests this is the case. Would there be any way to correct this divergence across a population of sites? Trying to understand where the divergence may have occurred is not helped by the fact that it is not possible to know the “parentage” of existing sites when viewing the sites and workspaces list – _layouts/15/mngsubwebs.aspx – as the majority of sites have no description which they would have from the template name or description provided when using the Save as Template options on the /_layouts/savetmpl.aspx page Read More