MOSS: Approval and Collect Feedback workflows cannot be associated to custom content types

Problem:
When I add a OOB Document Library to a site, Approval and Collect Feedback workflows are automatically visible for the documents. In other words, these workflows are associated with the 0x0101 content type.

When I create a custom document library using a custom content type that is a direct child of 0x0101 content type, these workflows cannot be associated to that content type.

Thoughts:
It doesn't do any good to set the BaseType of your custom content type to 0x0101.

Neither does it help to put a AssociationCategories tag into the ReviewWorkflows feature, trying to associate the OOB workflows to your custom content type.

If you include both your custom content type and 0x0101 content type in your custom Document Library feature's schema.xml, you can see the Workflows menu item in the menu when you hover mouse over a document in your custom list. But still there are no workflows associated.

Workaround:
Associate workflows to content types manually using a browser.

Solution:
Unknown.

MOSS: Discussion Board links point to default.aspx when creating List Views in site definition

Problem:
When defining Discussion Boards in Site Definition (in ONET.XML), the subjects of discussion threads point to default.aspx. This means that when clicking on a discussion subject the user is redirected back to the same page. Subject links should point to flat.aspx.

Thoughts:
Some blogs (1, 2) mention a KB article related to this problem and also a MS hotfix that might fix this problem, but it doesn't.

Solution:
Add ContentTypeID="0x012001" into the View element of the Discussion web part in your site definition like this:

<View list="Discussion" baseviewid="0" ContentTypeID="0x012001" webpartzoneid="LeftBottom" webpartorder="1"/>

ContentTypeID is now allowed there according to the schema, but it will still fix the issue.

SharePoint Designer 2007: A World Wide Web browser, such as Windows Internet Explorer, is required to use this function.

Problem:
When trying to export SharePoint Site Template with SharePoint Designer 2007, an error is shown when you try to export site template. You have IE7 installed.

Error is: "World Wide Web browser, such as Windows Internet Explorer, is required to use this function."

Solution:
Unknown

MOSS: Setting list view title in ONET.XML

Problem:
Title of a list view (ListViewWebPart) cannot be defined in ONET.XML so it cannot be set different from the title of the list it is showing.

If I modify the title with a browser (Modify Shared Web Part / Appearance / Title) and save the site as a template the new title is nowhere in the .stp file, still if I use that template to create a site the changes are there.

Solution:
Use the WebPart tag and define the Title under it. In the following example a minimized List View Web Part is added with a title My custom title.

<View List="Documents" BaseViewID="11"
WebPartZoneID="Left" WebPartOrder="3" Scope="Recursive">
<![CDATA[
<WebPart xmlns="http://schemas.microsoft.com/WebPart/v2">
<Assembly>Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c</Assembly>
<TypeName>Microsoft.SharePoint.WebPartPages.ListViewWebPart</TypeName>
<Title>My custom title</Title>
<FrameState>Minimized</FrameState>
</WebPart>
]]>
</View>

MOSS: Self-service Site Creation is not available because there is no inclusion defined

Problem:
When you have defined that you want to Create new site collections from Site Directory and you try to create a new site you get the error: "Self-service Site Creation is not available because there is no inclusion defined." You have enabled Self-Service Site Creation in Central Management Site.

Solution:
You don't have a path with wildcard inclusion in "Central Administration > Application Management > Define Managed Paths". Add one path with wildcard inclusion and you're all set. This requirement is also mentioned in TechNet.

MOSS: Unable to sort folders by ID if folders are created in ONET.XML

Problem:
Unable to sort custom list's folders by ID if folders are created in ONET.XML. Even though the OrderBy is defined correcty in the correct view in the schema.xml of the custom list feature, sorting by ID has no effect.

Solution:
Unknown

MOSS: Creating folders to list in ONET.XML

Problem:
One can easily create items to lists in ONET.XML, but how to create folders?

Solution:
Key is to use ContentTypeId and FSObjType.

<Row>

  <Field Name='ContentTypeId'>0x0120</Field>

  <Field Name='FSObjType'>1</Field>

  <Field Name='Title'>folder title</Field>

  <Field Name='LinkTitle'>folder title</Field>

</Row>

MOSS: Unable to send e-mail to lists

Problem:
When trying to send e-mail to MOSS list the mail SPTimerV3 deletes the .eml file from Drop directory, but items do not appear in defined MOSS lists. The following error is logged:

Exception when resolve principal "firstname.lastname@company.com" from domain "(null)". Exception: "Unable to contact the global catalog server"

Solution:
SPTimerV3 service and Central Management site Application Pool must run with the same account.