Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Migrate sites from STS to MySTS template?

  Asked By: Kevin    Date: Oct 28    Category: Sharepoint    Views: 852

During 2003 site migration, how can I have sites auto-converted from
template STS to template MySTS?

I don't want to spiral into the complexities of migration definition
files.. I just want to map STS to MySTS (MySTS will be a copy of STS).

Being that STS is a base type in 2003 and 2007, the migration happily
brings the sites across and assigns the proper template. I want to
modify the destination site definition, but don't want to modify the
STS site definition as recommended by Microsoft. So, I want to copy
the STS site definition to MySTS, and have all the old sites
automatically using "MySTS" after migration.

Share: 

 

9 Answers Found

 
Answer #1    Answered By: Rodolfo Tate     Answered On: Oct 28

I don't know of any supported way to change a site definition after it
has been chosen.

 
Answer #2    Answered By: Jesus Foster     Answered On: Oct 28

What are people doing to do things like adding a web part zone to a
migrated site?
Modify the STS site definition files directly?

 
Answer #3    Answered By: Alfredo May     Answered On: Oct 28

Currently, the best approach I've seen is to "staple" a FeatureActivated
callout Feature (using a FeatureSiteTemplateAssociation Feature) to the
out of the box site definitions. I'd be happy to hear the approach that
others are taking to this problem.

 
Answer #4    Answered By: Preston Moreno     Answered On: Oct 28

You could copy STS to STS.original and then modify STS, rather than the
other way around. If you later decide to revert to the original, you have a
clean copy that you can simply rename.

 
Answer #5    Answered By: Rickey Strickland     Answered On: Oct 28

You could use the same process that you used in #1 to do #2 & #3. Write
a feature that will ghost a new Master page to the MasterPage Gallery of
a site and a modified Default.aspx to the root of the site. Then change
the MasterURL property of the SPweb object to point at the new
Masterpage. You can also build it to put it back to the original
settings when you deactivate the feature. No messing with Site
Definitions, just a Feature to be installed and enabled on each site
that you want to look like the standard you establish.

 
Answer #6    Answered By: Jonathan Thompson     Answered On: Oct 28

How does the ghosted page layout work for the standard web part
pages for a team site? Doesn't it always present the same 8 page
layouts ([Full Page, Vertical], [Header, Footer, 3 Columns], ...)
regardless of what I have in any catalog?

 
Answer #7    Answered By: Taylor Mills     Answered On: Oct 28

Ghosted/Unghosted is an operational detail (where the template  file is
stored), it doesn't have any impact on the available functionality or
layout combinations. Which layout gets used depends on the settings for
the page in question.

 
Answer #8    Answered By: Angel Jordan     Answered On: Oct 28

There is no layout page for the default.aspx in a team site. The
ghosted page contains content controls that reference
contentplaceholders on the MasterPage. If you edit the default page in
the Site Definition directory of the 12 hive to have a different set of
webpart zones it will have a different layout.

 
Answer #9    Answered By: Darrell Peters     Answered On: Oct 28

Yes, there are still eight "Smart Page" layouts for pages that can be
created in the browser within a Document Library for standard Team
Sites. These eight pages can still be changed to produce a CMS-lite
solution just like they could be changed in WSS v2. However, with WCM
getting embedded within MOSS, there isn't near the need to use this old
approach. Page Layouts are much more flexible that these old "Smart
Pages".

 
Didn't find what you were looking for? Find more on Migrate sites from STS to MySTS template? Or get search suggestion and latest updates.




Tagged: