I am new to SharePoint development. We have created a base site template and have used that template to start new sites in other locations on the same server. This works fine but the newly created site seems to "flatten" the custom content types created in the original site. I would think there would be a way to keep the original content type inheritance intact to help support any necessary modifications on the new site. They can still make the modifications but they take longer because you have to visit each list individually. Does anyone know how to fix this or know a better way to approach this?
2
votes
2 Answers
4
votes
The problem you are having is the move from your original site collection to another. The site template does not store the complete definition of a site - only the differences from the underlying site definition. Move from one site collection to another and you lose the underlying site definition and run into problems such as the loss of your content types.
Site templates and site definitions are two separate customizations you can undertake. You need to make a decision based on your requirements as to which is best.
Site templates
Pro's:
- Easy to create and reuse through the SharePoint interface
- Ideal for end users
- A site template is a customization of the underlying default site definition
Con's:
- Dependency on underlying site definition means SharePoint updates could break your site templates
- Poor performance since the modifications are held in the database and are read from the DB and compiled on each request
- Limited customization options
Site definitions
Pro's:
- Harder to create: involves coding XML
- Made by developers and site administrators
- Independent of SharePoint default site definitions so not affected by SharePoint updates
- Limitless customization options
Con's:
- Difficult to modify when deployed
- Can be cached on the file system so is fast to load
Check out Google for info on creating custom site definitions.
Hope this helps!
Jonny
