Discussion Board Style for the Content Query Web Part

When you want to create a rollup from all discussion board (or a specific one) in SharePoint, you will notice that the Content Query Web Part does not have an appropriate style for it.

Every out of the box style from the Content Query Web Part returns the following result.

As you can see in the image above, the content query web part returns (Blank) messages. These (Blank) messages are the replies users have made.

So why do messages return as (Blank)?

As you may or may not know, the discussion board contains two content types.

Discussion;
Message. Message can only be used when you do a reply on a discussion (which creates folders), and they do not contain a Title/Subject field (this is hidden by default).

Because you do not need to add the subject in your reply, the title/subject field automatically gets (Blank) as field value.

Discussion Board Content Query Web Part Style

The result of the Discussion Board Style will be the following:

As you can see the (Blank) messages are replaced with the discussion subject. To do this, you can retrieve the subject from the LinkUrl of the message.

Discussion subject can be retrieved from the URL

The subject of the discussion exists in the LinkUrl, because when a discussion is started, it creates a folder with the subject as folder value.

The XSL style looks like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
<!-- Discussion Style -->
<xsl:template name="DiscussionStyling" match="Row[@Style='DiscussionStyling']" mode="itemstyle">
  <!-- Retrieve the content type: 'Content Type' -->
  <xsl:variable name="Type" select="@Type" />
  <!-- Retrieve the discussion/message creatore: 'Created By' -->
  <xsl:variable name="Creator" select="@Creator" />

  <xsl:choose>
    <!-- Check if item is a reply -->
    <xsl:when test="$Type='Message'">
      <!-- Retrieve the ReplyId, ex: '7_.000' -->
      <xsl:variable name="MessageId">
          <xsl:call-template name="StripSlash">
              <xsl:with-param name="text" select="@LinkUrl"/>
          </xsl:call-template>
      </xsl:variable>

      <!-- Remove the ReplyId from the discussion URL -->
      <xsl:variable name="DiscussionUrl" select="substring-before(@LinkUrl, concat('/', $MessageId))" />

      <!-- Retrieve the discussion title from the URL -->
      <xsl:variable name="DiscussionTitle">
        <xsl:call-template name="StripSlash">
              <xsl:with-param name="text" select="$DiscussionUrl"/>
          </xsl:call-template>
      </xsl:variable>

      <span style="font-style:italic;">      
        [
          <xsl:value-of select="$DiscussionTitle" />
        ]({$DiscussionUrl}) (Replied by: <xsl:value-of select="$Creator" />)
      </span>
    </xsl:when>
    <xsl:otherwise>  
      [
        <xsl:value-of select="@Title" />
      ]({@LinkUrl}) (Posted by: <xsl:value-of select="$Creator" />) 
    </xsl:otherwise>
  </xsl:choose>
</xsl:template>  

<xsl:template name="StripSlash">
  <xsl:param name="text"/>
  <xsl:choose>
      <xsl:when test="contains($text, '/')">
          <xsl:call-template name="StripSlash">
              <xsl:with-param name="text" select="substring-after($text, '/')"/>
          </xsl:call-template>
      </xsl:when>
      <xsl:otherwise>
          <xsl:value-of select="$text"/>
      </xsl:otherwise>
  </xsl:choose>
</xsl:template>

For the messages the ID (12_.000) will be removed from the LinkUrl, otherwise you will end up on a page that does not exist.

The XSL style can be added to the ItemStyle.xsl, which can be found at the following location: http://your_sitecollection_url/Style Library/XSL Style Sheets/ItemStyle.xsl.

When you add the content query to you page, change the Styles and Fields settings to match as in the following image.

When you save these settings, the result should be like this:

Discussion Board Style for the Content Query Web Part

Discussion Board Content Query Web Part Style

Report issues or make changes on GitHub

Related posts

Comments