2

Something is going on with my SharePoint Foundation 2010 installation and I'm not sure how to fix it.

Here is the sequence of events:

  1. Create a site, modify and get approval that is this the look of all future sites.
  2. Create a template of the site.
  3. Upload this site template (WSP) to a number of collections.
  4. Use the template to create a few sites.
  5. Change the look so much, that the original template is now useless for creating new sites.
  6. Disable and Delete the "Solution" from all the collections.
  7. Enjoy the fact that some of the sites created using the templates are now really screwed.

In the logs, there are sequences of entries with:

Relying on fallback logic in VghostPageManager::getGhostDocument()

Where it's looking for:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features************Modules\Files_themes\0\WIKI-ECF524AA.CSS

(NOTE: the * is the template name that was deleted. I've removed it for legal reasons from this post).

How can we set the site to NOT look for stuff (in this case a CSS) in a template that's now gone. I tried putting the WSP back for old template, but it's still broke. I can't seem to figure out where a site references what template it was originally created from.

And, the really odd thing, is that not all my sites have this issue... just a couple. I'm really confused

Thanks

j0k
  • 22,600
  • 28
  • 79
  • 90
Jason Nethercott
  • 373
  • 3
  • 20
  • ok... I've patched the problem for now. I've reinstalled the old template and now the sites work again. BTW, We use "Add-SPSolution" and "Install-SPSolution" from the Managment Shell to do the installs... And uninstall and remove to get rid of them. Not sure if that's the cause. Regardless, I need (want) to be able to remove the old templates completely, and have any sites originally created from those template still work. – Jason Nethercott Feb 21 '12 at 22:48

1 Answers1

1

Unfortunately, the feature used to include some of the site template resources (css) needs to remain. is not "old" if it is still being used. I suggest you hide the site template so it can no longer used in the future. Use a new site template for the changed visual look and feel if the old sites must remain as they are.

No question that this is a mess though.

Nat
  • 14,175
  • 5
  • 41
  • 64
  • That just doesn't seem right. Somewhere, the site must reference the template from which it came... But I've been digging all over trying to figure it out. I have not yet reached into the database to see if I can figure it out. It just seems, well, short sighted. I've learned my error though. The templates will now be named consistently over time. My first attempt was to name them with a date so I could keep track of when it was created etc. I.E. "MySiteTemplate20120222"... obviously, that was taking a long walk down a short plank. – Jason Nethercott Feb 22 '12 at 13:27