Mike
Wed Jan 19 23:35:41 CST 2005
>As this straddles functionality in each technology, but the
>template is a WSS template, I posted to this group
As the only newsgroup that "straddles functionality in each technology" is
the SPS newsgroup, it should go to microsoft.public.sharepoint.portalserver
newsgroup.
This newsgroup is for WSS problems that are common to all WSS
implementations. A problem that publishes to something that is only in SPS
2003 is not common to all implementations.
Please post straddling questions to the SPS newsgroup in future.
People here (the majority) who do not run SPS aren't interested in
reading/seeing them here.
Mike Walsh, Helsinki, Finland
WSS FAQ at
http://wss.collutions.com
Please post questions to the newsgroup only.
"Brian" <nonono@noemail.noemail> wrote in message
news:7DBD8FDF-FE74-4962-A2B8-5D8904CE32D6@microsoft.com...
> Jim -
>
> Thanks for the reply. In the case that I am mentioning, portal is the
> correct term. These are WSS sites under a Portal. The template in question
is
> a WSS Site Template published to the Central Template Gallery of
SharePoint
> Portal Server. As this straddles functionality in each technology, but the
> template is a WSS template, I posted to this group.
>
> Take Care,
>
> Brian
>
> "Jim Buyens" wrote:
>
> > First, in the future, if you aren't referring to SharePoint Portal
Server,
> > please don't use the word "portal" as you did below in your point 2.).
> >
> > As to sites that from a template taken before your change to schema.xml,
> > you'll have to either change eash site manually, or write a program that
> > modifies each site. This could be a Web Part, a command-line program, or
a
> > Windows app.
> >
> > In my view, the *real* answer is to stop replicating your application
this
> > way. Otherwise, as you've discovered, you end up with dozens, hundreds,
or
> > thousands of team-level installations to maintain, instead of a single
> > enterprise app.
> >
> > Jim Buyens
> > Microsoft FrontPage MVP
> >
http://www.interlacken.com
> > Author of:
> > *----------------------------------------------------
> > |\---------------------------------------------------
> > || Microsoft Windows SharePoint Services Inside Out
> > || Microsoft Office FrontPage 2003 Inside Out
> > ||---------------------------------------------------
> > || Web Database Development Step by Step .NET Edition
> > || Microsoft FrontPage Version 2002 Inside Out
> > || Faster Smarter Beginning Programming
> > || (All from Microsoft Press)
> > |/---------------------------------------------------
> > *----------------------------------------------------
> >
> >
> > "Brian" wrote:
> >
> > > Hi Wei- Dong,
> > >
> > > Actually it is not portal areas. It is strictly WSS sites. Here is the
> > > sequence of events that I think illustrate the problem:
> > >
> > > 1.) A template is created from the default team template called
"Template A".
> > > 2.) This template is then added to the portal Central Template Gallery
via
> > > stsadm.
> > > 3.) Changes are then made to the schema.xml files for lists contained
in the
> > > STS subdirectory under template (drive:Program Files\Common
Files\Microsoft
> > > Shared\web server extensions\60\TEMPLATE\1033\STS\LISTS) which affects
all
> > > sites created with the default Team template.
> > > 4.) Sites created with "Template A" do not show the modifications made
to
> > > lists schema.xml files as described in step 3 above.
> > >
> > > Jim's post sounds correct to me. Essentially since the template was
taken
> > > prior to the modifications, it does not reflect those changes. That is
> > > logical and ok.
> > >
> > > The problem is that it does not appear there is a way to correct this
and I
> > > am left with sites that I cannot modify to include new functionality
that was
> > > made. I need to verify that indeed this cannot be corrected.
> > >
> > > Thanks,
> > >
> > > Brian
> > >
> > > "Wei-Dong XU [MSFT]" wrote:
> > >
> > > > Hi Brian,
> > > >
> > > > "All was going well when I noticed that some sites did not show the
button.
> > > > "
> > > > I guess these sites who don't show the button should be the area,
not the
> > > > WSS site. Is that correct?
> > > >
> > > > This is due to the product design of SPS and WSS. At the folder
below, we
> > > > can find the templates files for WSS & SPS.
> > > > Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server
> > > > Extensions\60\TEMPLATE\<LCID> (1033 for en-US)
> > > >
> > > > WSS Site Definitions:
> > > > STS Team Site
> > > > MPS Meeting Site
> > > >
> > > > SPS Site Definitions (Area):
> > > > SPS, SPSPers, SPSSITES, SPSTOPIC, ETC
> > > >
> > > > So if you are going to change the List template schema.xml, please
also
> > > > customize the corresponding list template of the area.
> > > >
> > > > Please note: Changing a site definition after it has already been
deployed
> > > > can break existing sites and is not supported!
> > > >
> > > > After the changing to the template, one IISreset is required.
> > > >
> > > > Please feel free to let me know if you have any question.
> > > >
> > > > Best Regards,
> > > > Wei-Dong XU (WD.XU)
> > > > Microsoft Product Support Services
> > > > Get Secure! - www.microsoft.com/security
> > > > This posting is provided "AS IS" with no warranties, and confers no
rights