Archive for March, 2011

Adding the Social Note Board to a SharePoint Blog

March 2, 2011 1 comment

The Note Board is a pretty useful web part you can add to any page that can take web parts.  It allows you to store comments in the social database against that page using it’s URL – just like the Tags and Notes button in the ribbon.

The blog template is pretty much the same one from MOSS 2007, and uses the ol’ school comments functionality (stored in a separate list).  The problem with this is you can also add social comments to a blog post – very confusing.  It’d be nice to disable the blog comments, and just use the social comments.  So lets give it a shot.

What’re we’re going to do is:

1. Remove the blog comments web part from the post page

2. Add the Note board web part

3. Enable the publishing infrastructure site collection feature


Remove Blog Comments web parts

Open the blog site, and click on a post title to get to the post.aspx page.  From the Site Actions menu, select Edit Page.  Once in edit mode, you can delete the Comments and Add Comment web parts.


Deleting the Comments web part

Add Note Board Web Part

The Note Board web part is in the Social Collaboration folder in the web part categories. 

If the note board web part is not available, you will need to activate the feature PortalLayouts.  Use the following powershell command:
Enable-SPFeature –Identity PortalLayouts –url <site url>



Adding the Note Board web part

Enable the publishing infrastructure site collection feature

If you do not activate the publishing infrastructure feature, the note board will appear to work, but will not store comments correctly.  The note board does not use the correct url for the page, so the notes stored using the web part, will differ from the notes stored using the Tags and Notes button.  See the image below to see what I mean.


The note board web part differences from the Tags and Notes dialog.

If you discover this problem on the note board, activating the publishing infrastructure site collection feature will correct it.

Categories: SharePoint Tags: