RANT
I remember pursuing that issue with certain web parts not working on any
other site definitions than MPS. Why would they do that?
It ends up that I deviated from the Microsoft recommended new site definition
model because it was ridiculous in practice.
I wanted to create new definitions for SPS, STS, MPS and DWS, so I copied them and
created my own versions (ala Microsoft best practice). Then discovered that SPS
and MPS are hardcoded IDs in certain web parts... and potentially even hardcoded
directory names. So this left me with modifying original SPS and MPS files. A
hardcore purist might still want to try to work with copies of STS, but not me.
Two reasons:
- DWS exists within STS
- Copying STS really would add complexity.
Result, I automate my changes, but change SPS, STS and MPS in place. Now if
Microsoft pushes me changes (ala patches) to those files, at least I can
reproduce them with my automated means.
Anyway... my little rant is done.
-AAron
--- In sharepointdiscussions@yahoogroups.com, "Todd Bleeker" <todd@m...> wrote:
> I wish that the PageTabsWebPart developer hadn't restricted that
> component to ID=2. Many people have lamented the inability to really
> extend the MPS Site Definition because of this issue.
>
> <Todd />