MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Web parts in custom templates don't match the original site

  Asked By: Gregory    Date: Jul 12    Category: MOSS    Views: 966

I've been working a bit with deploying global site templates so that
we can provide users with relevant content fairly quickly. I've
deployed a template from a site that was originally created in
SharePoint 2003 and that got upgraded during our move to MOSS 2007.
Deploying the template works perfectly both within the site collection
and globally, but I've noticed that the main page of sites that are
created off of this template don't match the main page of the site the
template is based off of. Web parts are missing toolbars, some web
parts don't list the same columns as the original site, and some links
are missing (notably "Add new member" under the "Members" web part,
which appears just fine on the original site).

These are all cosmetic problems, really, but are nonetheless rather
odd. I do check the "Include Content" box when creating the template
file, so I wouldn't expect that to be a problem (especially since
content shows up just fine).

Any ideas as to why this is going on?



9 Answers Found

Answer #1    Answered By: Moises Harrington     Answered On: Jul 12

Different security groups??????????

Answer #2    Answered By: Kory Brock     Answered On: Jul 12

This might be a case where a picture is worth a thousand words. The
original layout that the template  is based on looks like this:


After the template is deployed, it looks like this:


There are a number of columns that are supposed to be showing in the
web part itself that are simply missing - this doesn't seem to be a
problem with access, since I wouldn't expect columns to disappear
based on access permissions.

Answer #3    Answered By: Ernesto Dawson     Answered On: Jul 12

Just a shot in the dark here, but maybe the original  site that the template  was
created from was modified in the personal view, rather than the shared view?

Answer #4    Answered By: Santiago Hood     Answered On: Jul 12

This is a known issue in SiteTemplates with MOSS 2007. Sites whose
webparts have been customized to use a custom  view will revert to the
default view when used for a SiteTemplate. A HotFix was released for
this sometime in March, but was later pulled. There is no fix for this
as of now, but there is a workaround.

Pull up the original  site in SharePoint designer and right click on each
customized webparts and use the context menu to convert it from a list
view web  Part to a DataForm webpart. Then save the SiteTemplate. Now
when using the SiteTemplate to create new sites the customizations
should remain. This will work whether the "include content" switch is
turned on or off.

Answer #5    Answered By: Alonzo Richard     Answered On: Jul 12

Seems like the hotfix is available again


Answer #6    Answered By: Toby Singleton     Answered On: Jul 12

So is this the same hotfix that was pulled or is this a re-release?

I'll try applying it when I get a chance.

Answer #7    Answered By: Felipe Osborne     Answered On: Jul 12

The fact that the fix was released and then pulled back has been a major
point of frustration around here. We put together a lot of site
templates for our customers and encounter this issue routinely. A couple
of times, we've had to resort to writing event handlers that would
re-apply the correct web  part settings on the effected web parts. It
works, and it gets the job done, but renders the site  templates
difficult to change after the fact.

I'm curious to know what other workarounds people have come up with to
address this issue.

Anyone know if Microsoft plans to re-release a fix in the near future?

Answer #8    Answered By: Steve Fernandez     Answered On: Jul 12

The primary workaround other than using DataForm webparts as I described
(which I agree has its limitations) would be to create the custom  Site
as a Site Definition and not a Site Template. More difficult to do, but
it also gives you a great deal more power and control. You can even
start with a Site Template and using the Solution generator reverse
engineer it into a Site Definition.

Answer #9    Answered By: Travis Turner     Answered On: Jul 12

Check if this hot fix applies