cmetral's blog

I just discovered this post from Daniel McPherson. It's very useful to know how to change the Category navigation bar on the home page of an SPS portal. I advice you to read his post, event if I give you the tip here : he explains why NOT delete the native topics area.

1. Open rogram FilesCommon FilesMicrosoft Sharedweb server extensions60TEMPLATE\SPSdefault.aspx
2. Search for the following string:   <SPSWC:CategoryNavigationWebPart runat="server" id="VerticalNavBar" DisplayStyle="VerticalOneLayer" /> 
3. Replace it with the following string:   <SPSWC:CategoryNavigationWebPart runat="server" id="NewVerticalNavBar" DisplayStyle="VerticalOneLayer" CurrentCategoryID="<INSERT CAT ID HERE>"/>
4. Where is equal to the Category ID of the area whose children you wish to display as navigation. To get the Cat ID: Browse to an area, then click on "Change Settings" and copy the string that appears after "CatID=" in the URL. "

I just discovered this post from Daniel McPherson. It's very useful to know how to change the Category navigation bar on the home page of an SPS portal. I advice you to read his post, event if I give you the tip here : he explains why NOT delete the native topics area.

1. Open rogram FilesCommon FilesMicrosoft Sharedweb server extensions60TEMPLATE\SPSdefault.aspx
2. Search for the following string:   <SPSWC:CategoryNavigationWebPart runat="server" id="VerticalNavBar" DisplayStyle="VerticalOneLayer" /> 
3. Replace it with the following string:   <SPSWC:CategoryNavigationWebPart runat="server" id="NewVerticalNavBar" DisplayStyle="VerticalOneLayer" CurrentCategoryID="<INSERT CAT ID HERE>"/>
4. Where is equal to the Category ID of the area whose children you wish to display as navigation. To get the Cat ID: Browse to an area, then click on "Change Settings" and copy the string that appears after "CatID=" in the URL. "

If you don't know it, you can waste a lot !

When registering new templates in WEBTEMP.XML and WEBTEMPSPS.XML, you have to set an ID greater than 10000 (maybe Microsoft hopes to release a lot of new templates in the SP). And IDs must be different in the two files. For example, you can't have a template id of 10001 in the WSS definitions (WEBTEMP.XML) and another with id 10001 in the SPS areas definitions (WEBTEMPSPS.XML).

Have a good templating time !

If you don't know it, you can waste a lot !

When registering new templates in WEBTEMP.XML and WEBTEMPSPS.XML, you have to set an ID greater than 10000 (maybe Microsoft hopes to release a lot of new templates in the SP). And IDs must be different in the two files. For example, you can't have a template id of 10001 in the WSS definitions (WEBTEMP.XML) and another with id 10001 in the SPS areas definitions (WEBTEMPSPS.XML).

Have a good templating time !

Well, I'm not currently working on SharePoint, that's why my posts are so rare … But I have a look at what's happening.

And there it is ! The SPout/SPin manifest file is decribed in this document from Microsoft.

What to do with it ?

• Create your own "Exporter" (from any technology) and use SPin to import into SharePoint 2003.
• Custom the SPout-generated xml file and use SPin to import into SharePoint 2003.

An alternative (with best and worse points) to the Extractors/Importers.

Enjoy !

Well, I'm not currently working on SharePoint, that's why my posts are so rare … But I have a look at what's happening.

And there it is ! The SPout/SPin manifest file is decribed in this document from Microsoft.

What to do with it ?

• Create your own "Exporter" (from any technology) and use SPin to import into SharePoint 2003.
• Custom the SPout-generated xml file and use SPin to import into SharePoint 2003.

An alternative (with best and worse points) to the Extractors/Importers.

Enjoy !

Relaying this post of Renaud Comte.

Or directly to : GotDotNet

Relaying this post of Renaud Comte.

Or directly to : GotDotNet