• Enhancements
• Changed forum discussion subjects rendered properly in replies and community widgets
• Move Blog or Knowledge Base drafts to a different community location
• Remove EXIF data from images based on allowed listed tags
• Announcements
• EOL: Email a Friend and Invite a Friend capabilities
• Redirects: HTTP-to-HTTPS for CloudFront backed communities
• API Updates
• Move Blog and Knowledge Base article drafts
• Support for Message Archive and Unarchive Event Subscription
• You found it! We fixed it!
• General bug fixes
• Accessibility fixes

 

Enhancements

 

Changed forum discussion subjects rendered properly in replies and community widgets

Prior to this release, when the subject (or title) of a forum discussion was modified, any new replies inherited the modified subject. However, all the older replies continued to refer to the old subject.

All widgets or places such as breadcrumbs, Permalinks, View History, Move Message flow, Spam Quarantine, My Contribution, Mentions, and Search results for replies showed the older title of replies.

Now, all replies (new and existing replies) under a root discussion reflect the most current subject (or title). Also, the most recent subject displays wherever this discussion renders in the community.

Note: To enable this enhancement on your community, contact Support. The config is not enabled by default in the community and you cannot turn off the config after it is enabled.

 

Move Blog or Knowledge Base drafts to a different community location

From time to time, you might want to move a blog or knowledge base draft to a more appropriate board. Or, you might want to move drafts out of a KB or Blog, or remove them from the community structure, but want to maintain the drafts. In these cases, you can now move these drafts to a different location.

With this release, you can now move drafts to different boards. Just open the Options menu of the draft you want to move and click Move Article.

 

Note: To use this feature, you must be on feature versions TKB v4 or later and Blogs v3 or later. Go to Studio > Features and select the appropriate versions for TKBs and Blogs.

Permission Requirements

• To move a draft of a blog post, you must have the Manage any article permission.
• To move a draft of a KB article, you must have the Create, edit, publish, and manage articles permission.
• To move your own Blog drafts, you must have the Start New Article and Manage Own Article permission.

Learn more about moving KB articles to a different knowledge base moving blogs post to another node.

Remove EXIF data from images based on allowed listed tags

With this release, when members upload the images such as Inline, Gallery, and Profile images to the community, community removes EXIF metadata that is not in the allowed list from the images. While removing this data, the community retains the allowed list of tags. This change is applicable only for the Inline, Gallery, and Profile images and for the ‘Download Images’ flow.

Announcements

EOL: Email a Friend and Invite a Friend capabilities

With the 22.10 release, we have turned off and removed the Email a Friend and Invite a Friend capabilities for all communities, including releases prior to 22.10. The decision to turn-off these features is two-fold: minimal use of the features and the potential for email abuse of these features given the current throttling restrictions.

There are already a wide variety of ways for people to easily share links across the web, including using their personal email. In the future, we will be looking at simple ways for people to share links with each other within the community via private messages and notifications. If you have questions about this change, contact your Khoros account manager.

Redirects: HTTP-to-HTTPS for CloudFront backed communities

With this release, we no longer allow HTTP traffic for all the CloudFront backed communities. All HTTP traffic to these communities is automatically redirected to HTTPS. This change is irrespective of the community version.

API Updates

Move Blog and Knowledge Base article drafts

We have enhanced the existing Move API to enable you to move blog and knowledge base drafts.

With this release, using the Community v1 Move API, you can move a blog or knowledge base drafts along with its comments and information to another blog or knowledge base board respectively.

Note: To use this feature, you must be on feature versions TKB v4 or later and Blogs v3 or later. Go to Studio > Features and select the appropriate versions for TKBs and Blogs.

Support for Message Archive and Unarchive Event Subscription

In this release, we have updated the Community v1 Event Subscription API to support the MessageArchive and MessageUnarchive event subscriptions.

Learn more about the Message Archive and Unarchive Event Subscription.

You found it! We fixed it!

General bug fixes

• Previously, when you ran the Kudo REST API in REST API v1 and v2 to give multiple kudos in quick succession to a member, the “Kudos given” count for that member was incorrect. This impacted Kudos Metrics in Community Analytics. This issue is now fixed. Now, when you run this API in quick succession, the Kudos metrics (net_kudos_events_received and net_kudos_weight_received count) increases only by 1 kudo per post.
  
  
• Earlier, when images were attached on a community page, some of the images displayed in their native resolution and others resized to a much lower resolution. This issue is now fixed. Now, when you attach images on any community page, they display close to the same size.
  
  
• Earlier, when you clicked any of the buttons on the Value Analytics Survey dialog box, the page focus scrolled to the bottom of the page. This issue is now fixed. Now, the page does not focus to the bottom of the page, but redirects according to the option you choose.
  
  
• Earlier, when you searched for labels in messages, the search returned only those labels with an exact match. It did not return those labels where the keyword matched with either the prefix or suffix.
  For example, assume that “Best Practices” and “Practices” are labels on your community. When you searched for “Practices” in the label section, the “Best Practices” label was not returned. Instead, only the “Practices ” label was returned. This issue is now fixed.
  
  
• Previously, when you tried to post an event with a Live Stream URL with emoticons in its title, you received an error message. This issue is fixed.
  
  
• Previously, when you uploaded a .SWRD file to a Case Portal, the upload failed. This issue is now fixed.
  
  
• Previously, when you added an emoji to any post on the community, the emojis appeared as broken images for a few seconds before the actual image displayed. This issue is now fixed.
  
  
• Previously, when members viewed notifications, the notifications count remained uncleared in the notification feed and received incorrect counts from the cache. This issue is now fixed. Now, when members view notifications, the notification feed clears the count and returns a valid count.
  
  
• Previously, in the Bulk Archive page, when members tried to re-submit the same search criteria after canceling the existing search, members were not able to perform the search and an error message was displayed indicating that the job already exists for the search criteria. This issue is now fixed. Now, members can perform the search by re-submitting the same search criteria after canceling the existing search.
  
  
• Previously, when non-SSO users tried to change their email addresses using dual authentication in the community, the email addresses were not updated but the user received a success message indicating that the email address had been updated. This issue is fixed. Now, non-SSO users can change their email addresses using dual authentication in the community.
  
  
• Previously, when members used API calls to get the user settings such as user signature on Studio, the API calls did not return value on the NotificationFeedPage. This issue is now fixed. We have updated the code to refresh the user cache before returning the settings for a user when loading the NotificationFeedPage.
  
  
• Previously, in the community, when members tried to access the archived posts of the deleted boards, an error message was displayed indicating that the specified parameters were invalid. This issue is fixed. Now, when members access archived posts of the deleted boards, they are redirected to the related URLs of the posts or indicated that the content has been archived.
  
  
• Previously, when members added a video URL or mentioned other members in their posts, the videos and mentions did not appear in the RSS feed reader as they did not render as valid HTML links in RSS feed. This issue is fixed. Now, videos and mentions added in posts appear in the RSS feed reader.
  
  
• Previously, when members tried to access any node or posts within the node and the URI path of the node contains asset or RSS keywords, the loaded page indicated that the members were not authenticated even if they were logged in to the community because of certain URI patterns. This issue is fixed. Now, the page successfully loads when members access the nodes which have asset or rss keywords in the URI paths.
  
• Previously, when community admins or moderators added a comment to a post, a Moderator flag was added to the post. This issue is fixed. Now, comments from admins and moderators do not display the Moderator flag.
  
  
• Previously, when members created content filter by enabling Ignore inline HTML and do not post option and inserted non-breaking spaces ( ) and HTML span tags (<span>) to any post through browser’s developer console, the content filter did not flag non-breaking spaces ( ) and HTML span tags (<span>) as spam and members were able to post the content in the community. This led to difficulty in identifying spam messages. This issue is fixed. Now, content filters flag non-breaking spaces and HTML span tags added in the posts through browser's developer console.
  
  
• Previously, when community members signed in to the community for the first time and their SSO IDs contained spaces at the beginning or end of their ID, the spaces added were stripped from SSO IDs. This led to authentication issues, which resulted in members signing in to the wrong account. This issue is fixed. Now, the spaces added in the beginning or end of the SSO IDs are not stripped, and these accounts are considered unique and valid.
  
  
• Previously, when community admins or moderators tried to update the SSO ID of a member account by adding space at the beginning or end of the same SSO ID, a new profile was created and the original profile was updated to the same SSO ID of the new profile as the space added was stripped from the SSO ID. This created duplicate profiles with the same SSO ID, which resulted in members logging in to the wrong account. Now, when community admins or moderators update the SSO ID of a member account by adding space at the beginning or end of the same SSO ID, a new profile is created that has a different SSO ID from the original profile.
  
  
• The issue where the Bulk Archive page displayed incorrect results when the specific bulk archive filters were applied is fixed.
  
  
• Previously, members with Manage own articles permissions were unable to move or delete their own blog posts to other nodes on the community. This issue is fixed.
  Now, for members to move or delete their own blog posts, they must have both the Start new article and Manage own article permissions and Manage own article permission on the destination node.
  For members to move or delete other member’s blog posts, they must have both the Start new article and Manage own article permissions and Manage any article permission on the destination node.

Accessibility fixes

• Previously, there was no heading defined for the Managed Friends and Ignored pop-up window. Since screen readers had no information to read out, people using screen readers did not understand the purpose of the page. This issue is now fixed.
  
  
• The issue where the screen reader did not announce the state as ‘disabled’ for the disabled items in the Options menu on the Gallery page is fixed.
  
  
• Previously, the descriptive labels were not available for various fields (drop-down menus, search fields, and so on). Since screen readers had no information to read out, people using screen readers did not understand the purpose of these fields. This issue is now fixed.
  
  
• Previously, the links that are disabled (.lia-link-disabled) within the application due to user permissions did not meet the color contrast specifications for accessibility. This issue is fixed.
  
  
• Previously, the form elements on Community pages did not have labels. Users who depend on the screen readers found it difficult to navigate through the pages. This issue is fixed. We have ensured that every form element has a label.