Latest Posts

Last month I created a couple pretty basic commands to help me with setting the navigational elements of my site: gl-enumnavigation and gl-addnavigationnode. You can find information about those commands here: Site Navigation Settings.

I finally figured it out! This was supposed to be one of those very simple tasks that I should have been able to do without any custom code. Turning a sub-site (or web) into a site collection (or top level site) turned out to be the most difficult task I’ve yet to face with SharePoint 2007.

This command was created to fix an issue with our upgraded sites as well as issues I discovered with sites that had been imported to new farms. What happened was that after the upgrade (or an import) the Page Layout URL (page.

I created this only because I needed to debug some issues I’ve been having with Page Layouts – try to convert a sub-site to a site collection and you’ll see what I mean :).

This turned out to be a lot more challenging than I was expecting it to be. Duplicating a content type required that I learn a lot about how to programmatically create things like site columns and workflows associations and policies.

One of the tasks I needed to do for my upgrade was to convert a sub site to a site collection. This is something I’m still trying to get right as of this writing but figured I’d share a new command I had to create to help with that.

Setting the navigation is another common post upgrade/deployment task that should be easy to script. One of the challenges in using the commands I created was that it’s necessary to know the node ID of the navigational elements.

Update 9/25/2007: This command has been deprecated in favor of the gl-mysitesettings command. Update 9/18/2007: I’ve modified this command so that it no longer manipulates the database directly. The content below has been updated to reflect the changes.

One of the common tasks that administrators will need to perform across various site collections upon initial deployment is to set which site templates (and page layouts) are available for creating subsites and pages.

This ended up being one of those simple commands to create that took way to long to figure out how to create. Fortunately though there is an API available for setting this property (unlike most of the profile import related tasks such as the timer jobs).