User Facing: Desktop
- Added code that allows users to save search results to the notifications system so they can be notified when new content is posted that matches their search results.
- Added a new, more visible, "alert banner" that will display at the top of Connect pages to alert users of important and/or special announcements. The alert banner will display until the user clicks a dismiss button.
- Updated the featured article carousels on Community overview pages with new, more visible, navigation.
- Updated the code behind the Facebook share widget to use the latest working code provided by Facebook.
- Changed our date logic so the "time ago" date format is never displayed on cached pages (that are served to unauthenticated users) or on pages published in the Security Response blog area.
- Added an API that allows external systems to update and display a user's status message.
- Added intelligence to the add/edit forms to keep users from posting content types, like downloads, in communities that don't support that content type (not all communities support all content types).
- Resolved an issue with the activity feed in the IT Trends communities where comments in the feed were being attributed to the author of the initial post and not the author of the comment.
- Fixed an issue with browser "jumping" when a user selected a machine translation from an article page.
User Facing: Mobile
- Fixed an issue that caused a system error when users accessed their private message mailbox via the mobile UI.
- Added featured discussion threads back to the top of forums (along with a button to easily hide them).
Admin Facing
- Fixed an issue with the "Move discussion" functionality that was not setting the timestamp on moved discussions nor was it disabling the source comments after they had been moved to a new target discussion.
Performance Wins
- Refactored the code that generates the cached "top contributors" blocks to be more efficient.
Behind the Scenes
- Added code to our RSS engine that properly escapes uploaded files that have spaces in their names. File names with spaces were causing Connect to generate invalid RSS (when the feed included an article with a file attachment that had spaces in its filename).