• Data is stored in custom lists.
• Custom display is generated by the DataViewWebPart.   You will need to know a little bit about xsl to really make the DVWP come to life.
• Users will need permissions to read all items.
• Users should be allowed to edit only their own items.
• You will need to create a few pages which are designed for particular tasks (i.e. view post+comments, summary view).

Model #1

• Based on only one list – let’s call it Blog
• Moderation is turned ON.  If you don’t do this, then everyone can post as the blog author.
• The Blog list has at a minimum the following columns
• Title – single line of text
• Body – multiple lines of text
• Type – Choice column with “Post” and “Comment” options
• Related To – Lookup column which references the ID column in the Blog list

Model #2

• Based on two lists – let’s call them Blog and Comments
• Only the admin has access to create/edit posts within the Blog list
• Everyone has create/edit rights to the Comments list
• The Blog list has at a minimum the following columns:
• Title – single line of text
• Body – multiple lines of text
• The Comments list has at a minimum the following columns:
• Title
• Body
• RelatedTo – Lookup column which references the ID column in the Blog list

1. Summary view with links to view individual posts (on default.aspx)
2. Invidual view (on viewpost.aspx)
3. Comment view, designed to show items related to the specified post (on viewpost.aspx)

• Default.aspx: A default view page where only posts are displayed and a button with “View comments”
• ViewPost.aspx: The page displays both posts and comments.

Instructions for Default.aspx:

1. Create a new web part page, call it "Default.aspx"
2. Add a list view part for the Blog list.
3. Modify the web part...
1. Select Edit the View, display only Title and Body
2. Set Toolbar Type to No Toolbar
4. Open FrontPage, convert the web part to a DVWP.
5. Adjust the display to your liking.  This provides a basic structure.  Note that your view is currently displaying both posts and comments.

1. Again, in FP and viewing the source, search for "<xsl:template name="dvt_1.body">"
2. Find the for-each block which is used to iterate through all items in your list (look for "<xsl:for-each select="$Rows">").
3. Add a display time filter to limit the view to only posts by wrapping the entire contents of the for-each section in an "if" block.  Thus, add the filtered view would look like...

<xsl:for-each select="$Rows">
  <xsl:if test="@Type='Post'">
    … original content …
  </xsl:if>
</xsl:for-each>

The next thing to do is to add a link to your view page.  Let’s say we wanted to create a link that looks like...

View comments (0)

1. Search "<xsl:value-of disable-output-escaping="yes" select="@Body"/>".
2. Insert the following text immediately after the <xsl:value-of> tag:

<div>
  <a style="text-decoration: none;"><xsl:attribute name="href">ViewPost.aspx?ID=<xsl:value-of select="@ID"/></xsl:attribute>View comments (<xsl:variable name="commentCount" select="@ID"/><xsl:value-of select="count(//@RelatedTo[.=$commentCount])";/>)</a>
</div>

1. Create a page called ViewPost.aspx
2. Add a DataViewWebPart for the Blog, filtered to show only Posts.  Let’s call this web part "Posts".
3. Add a DataViewWebPart for the Blog, filtered to show only Comments.  Let’s call this web part "Comments".
4. Create a WebPart connection between "Posts" and "Comments".  Starting from the "Posts" web part...
• Provide Data Values to "Comments"
• Target action = Filter View Using Data Values From "Posts" column ID to "Comments" column RelatedTo.
5. In the "Posts" web part, supply an additional filterParam binding so that the web part will be able to filter the display based on the query string parameter "?ID=x".  You will need to follow the directions posted at http://support.microsoft.com?id=831093.  The parameter name for this example is "ID"; thus, the complete string will be "QueryString(ID)".

Now let's add a "Post a New Comment" button in the "Posts" web part.

1. View the xsl data, find the area where the Body is pumped out (search for "<xsl:value-of disable-output-escaping="yes" select="@Body"/>")
2. Insert the following markup after the Body section (note: the display format is not really important, but the onclick handler GetID is crucial)...

<table border="0" width="140" cellspacing="0" height="8" cellpadding="0" >
  <tr>
    <td class="ms-navframe" bordercolor="#798073" style="border-style: solid; border-width: 1px; background-image:url('/_layouts/images/partgrad.gif')">
    <p align="center">
    <span style="cursor:hand" onclick="GetID()">
    <font style="font-size: 0.68em">Post a New Comment</font></span>
    </td>
  </tr>
</table>

Now add the GetID javascript method to the page source.  This is the onclick event handler that will redirect the user to the appropriate new item form for the Blogs list. 

1. View the page source. 
2. In the <head> of the page, add the definition for the "GetID" javascript function.     

function GetID () {
 var regex = new RegExp("(?:(\\?|\\&)id=|FilterValue1%3d)", "gi");
  var logID = document.location.href.split(regex);
  var pageURL = "Lists/Blog/NewForm.aspx";
  var returnURL = "ViewPost.aspx?id=" + logID[1];
  window.location = pageURL + "?Source=" + returnURL + "&LogID=" + logID[1];
}

• First, add the following script toward the top of the page (e.g. in the <head>)...

function LoadID () {
  var RegX = new RegExp("LogID=", "gi");
  var Log_ID = document.location.href.split(RegX);
  document.forms[0]["urn:schemas-microsoft-com:office:office#RelatedTo"].value=Log_ID[1];
  document.forms[0]["urn:schemas-microsoft-com:office:office#Type"].value="Comment"
}

• Add input tags after the <form> tag:

<input type="hidden" name="urn:schemas-microsoft-com:office:office#RelatedTo" value=""/>
<input type="hidden" name="urn:schemas-microsoft-com:office:office#Type" value=""/>

• then toward the bottom of the page markup (before the closing <form> tag), add the following:

<img border="0" alt="" onload=LoadID() src="/images/spacer.gif" width="1" height="1">

(Note: the src should point to an image on your system - in the templates listed in post 3/3, spacer.gif is a 1x1 transparent image)

• finally, update the input display.  This is done by right-clicking on the ListFormWebPart and selecting "Customize SharePoint List Form".  Highlight and delete the two table rows which contain the RelatedTo and Type dropdowns.  This is done so that users will not have to mess with those fields.