As of the 4.5 release, the Social Search BDC Model to integrate with SharePoint search has been changed.

Consequently, after upgrading from any version prior to 4.5 to 4.5 or later, the search integration will need to be setup again.

When upgrading from 1.1 to higher versions of Aurea Social (then called “Social Sites”), any users that had been granted the Delete Events permission in the NewsGator Social Platform Services application will lose that permission.

After completing update, you have to regrant this permission to anyone that should retain it.

For further details on how to do this, see How to Grant Rights to Delete All Events .

If you upgraded from any version of Aurea Social (then called “Social Sites”) before 2.0, some platform features you have enabled will become disabled.

These include:

• Activity Authors Can Delete Comments
• Append user's full name After @target
• Enable Terms of Use

Go to the NewsGator Social Platform Management page and re-enable these. For further details see the Social Sites v3.5 Admin Guide.

In some cases, incremental crawls of the social content source (the BCS content source of public microblogs, questions, comments and answers that was introduced in 2.0) did not pick up new or changed items.

This issue was corrected in the 2.1 release. We recommend customers run a full crawl of this content source upon install of v2.1 or higher, especially for upgrades from 2.0.

This section applies to two scenarios:

• whether you have a customized email digest template or
• a customized Email Instant Notification template

If you upgraded from Aurea Social (then called “Social Sites”) v2.0 and had a customized Email Digest template, your customized template is kept, so you won't get new lines that were added to the default template that provide the new View link feature in posts.

To add these new lines to your customized template, find the lines that generate the “Comment” link. To the end of that line add this:

In v2.1 we added two new methods to our helper class:

• EmailXsltFunctions: ShowViewLink which looks at a url string and returns true if it’s the url of an event we want to display.
• EmailXsltFunctions: GetViewLink which takes the view link URL and returns a nicely formatted and localized <a> tag to display.

If you upgraded from any version of Aurea Social (then called “Social Sites”) prior to v3.0 and had a customized Email Digest template or had a customized Email Instant Notification template, your customized template is kept, so you won't be able to take advantage of the changes made to the Digest Email functionality in 2.5/2.6 unless you make changes to your template along the lines of those listed below.

However, there were several additions to the output XML and consequent changes to the XSLT.

We suggest that customers consider downloading the default XSLT and study it to understand the changes we’ve made. It may be easier to download our updated template and apply customer specific changes to it rather than trying to update the customer’s custom template.

The biggest changes between the 2.1 release and the 2.5/2.6 release are:

• Added a function to URI encode URIs (there isn’t a default XSLT way to do this and some email clients want it.)
• Displaying polls
• Displaying attachments
• Added Like link to posts
• Added Follow-up link to posts
• Added Mute link and message to bottom of email (Instant Notification emails only)

The function to URI encode URIs can be added to any URI (For example where they show atom:author/atom:uri)

The code for displaying polls is as follows:

Here’s an example of displaying an attachment:

Here’s an example of displaying a Like link:

Here’s an example of displaying the “Mute” link (Instant notification emails only):

If you upgraded from any version of Aurea Social (then called “Social Sites”)prior to v3.0 and had a customized Email Digest template, your customized template is kept, so you won't be able to take advantage of many of the changes made to the Digest Email functionality in 3.0 unless you make the changes listed below to your template.

These modifications were required to make the XML output more extensible in the future and to add further functionality.

Steps 1 through 5 are required. Email digest functionality stops working if these are not implemented:

1. Add a new namespace to the template xmlns:digest="uri://newsgator.com/social/digest".
2. Replace references to the element named atom:groupName with digest:name
3. Replace references to the element named atom:colleagueName with digest:name
4. Replace references to the element named atom:colleagueRecordId with digest:id
5. Replace references to the element named atom:groupId with digest:id
6. Add a section to call the template for the new chronological ordering option. By default it is in the root (/digest) template and looks like this:
7. Add a template for the new chronological ordering option. By default it looks like this:
<xsl:template match="ChronologicalFeed/atom:feed"> <xsl:if test="count(atom:entry) > 0"> <div> <table cellpadding="5" cellspacing="0" width="100%"> <xsl:apply-templates select="atom:entry"> <xsl:sort select="atom:updated" order="ascending"/> </xsl:apply-templates> </table> </div> </xsl:if> </xsl:template>
8. Add code to the root (/digest) template to call the template for the new My Activities content source. By default it looks like this:
<xsl:if test="count(ConversationFeed/atom:feed)"> <div> <h1> <xsl:value-of select='EmailXsltFunctions:GetLocalizedString("DigestEmailMyActivityHeading")'/> </h1> </div> <!--All activity in chronological order--> <xsl:apply-templates select="ConversationFeed/atom:feed"> </xsl:apply-templates> </xsl:if>
9. Add a template to display the new My Activities content. By default it looks like this:
<xsl:template match="ConversationFeed/atom:feed"> <xsl:if test="count(atom:entry) > 0"> <div> <table cellpadding="5" cellspacing="0" width="100%"> <xsl:apply-templates select="atom:entry"> <xsl:sort select="atom:updated" order="ascending"/> </xsl:apply-templates> </table> </div> </xsl:if> </xsl:template>
10. There is a new helper function to display the logo of a community if it has one. It can be used like this:
<xsl:value-of select="EmailXsltFunctions:GetSocialGroupLogoPictureCid(digest:id, digest:imageUrl)"/>
11. The elements atom:entry and ng:comment can now have a child called ng:LinkPreviewInfo. The default template to render it looks like this:
<xsl:template match='ng:LinkPreviewInfo'> <table> <tr> <td width="5"></td> <td colspan="1"> <xsl:if test="ng:ThumbnailUrl"> <a href="{ng:Url}" title="{ng:Title}"> <img src="{ng:ThumbnailUrl}" alt="{ng:Title}"> <xsl:choose> <xsl:when test="ng:ThumbnailLandscape='false'"> <xsl:attribute name="height">125</xsl:attribute> </xsl:when> <xsl:when test="ng:ThumbnailLandscape='true'"> <xsl:attribute name="width">125</xsl:attribute> </xsl:when> </xsl:choose> </img> </a> </xsl:if> </td> <td colspan="2"> <a href="{ng:Url}" title="{ng:Title}"> <xsl:value-of select="ng:Title"/> </a> <br></br> <xsl:value-of select="ng:Summary"/> </td> </tr> </table> </xsl:template>

There should be no changes required to your customized template to maintain full email digest functionality when upgrading from Aurea Social (then called “Social Sites”) v3.0 or v3.1.