Advertisement

sharepoint templates - ghosting

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

  1. 10/6/2005 3:01 PM | # re: sharepoint templates - ghosting
    Thanks guys - just sorted a debate out with my buddy.

    Question - why do we 'need' to unghost in the first place?

    Given that I could modify a site/library template prior to creating the site


 
Please add 4 and 7 and type the answer here:
First time here? You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting! (hide this)