sharepoint templates - ghosting
| Comments Thanks for visiting! Just a fair warning this post is fairly 'old' in tech terms and may contain outdated information and/or broken links or pictures. Please verify info and feel free to contact me if questions!
well, i'm pretty swamped and haven't had an opportunity to finish my template 101 whitepaper. i came across new uploads on the gotdotnet sharepoint samples and found a presentation from mikefitz regarding site definitions.
as some of you may know (what i was writing in my little whitepaper) is that frontpage editing breaks the ghosting of your template...here's an excerpt from the presentation (forgive the copy/paste formatting). check out the presentation and other stuff on the gotdotnet sharepoint space
-
Pages and list schema are read from the site definition files
and cached at IIS process startup - Page source is on the disk, not in the DB
- Pulled from the cache at runtime
- It still appears to be present in the site, hence the term “ghosted”
- Pages are only written to the database when customized within a site
- Browser-based customization (i.e. adding/removing web parts) does not change the actual ASPX pages, hence doesn’t unghost
- FrontPage customization often changes ASPX pages
- Maximizes scalability
- Reuse un-customized pages across sites
- Reduce unnecessary data storage and retrieval
Please enjoy some of these other recent posts...
Comments