Blog Post

Release Notes & Updates
6 MIN READ

16.2 Release Notes

JohnD's avatar
JohnD
Khoros Alumni (Retired)
10 years ago

In the 16.2 Release, we’ve continued to make enhancements to some key feature areas that improve the community member and admin experiences. Key features included in this release are user account management, Featured Threads, user profile settings, the LSI bulk data API, our FreeMarker context objects, and the Lithium-Klout SDK.

New Features

Enable one user to close another user’s account

We have added a new user management permission that enables permissioned users to close another user’s account without having to first “switch” to that user’s account. This new permission is denied to users (except Admins) by default, and you should only grant this permission to a few, trusted users--most likely the site admin and/or a senior moderator.

 

To enable a user to close the account of another user:

  1. Sign in to Community Admin as an Admin.
  2. Go to Users > Permissions.
  3. Click Roles.
  4. Click Edit next to the role.
  5. Scroll down to the User Management section.
  6. Grant the Close other users’ accounts permission.

    Note: The user must also be granted the Manage Communities permission.
  7. Click Save.

With this permission, you do not need to switch to another user to close that user’s account.

 

To close another user’s account:

  1. Go to Community Admin > Users > Edit Users.
  2. Enter the name of the user or the user’s ID and click Select User.

  3. Enter the username of the account you want to close.
  4. Click Close Account.

You will be prompted to enter your username to close the account.

Set the display order for Featured Threads

In the 15.4 release, we added the ability for you to manually sort the display order for TKB articles in a knowledge base. We have now extended this functionality to Featured Threads. Previously, you could sort Featured Threads only by Date or Kudos. Now, you can choose to sort these threads manually so they appear in a specific order in the Featured Threads component.

 

To sort Featured Threads manually:

  1. Sign in to Community Admin.
  2. Go to Content > Featured Threads.
  3. If needed, click Choose and go to the node where you want to sort Featured Threads.
  4. Click the Ordering tab.
  5. Click the Manual sort option and click Save.

  6. Click and drag Featured Threads up and down into the order you want them to appear on your community site. (Alternatively, you can enter the number in the Article Order column and click Enter on your keyboard.)

    Note: If no topics appear in the list, no topics have been set to be featured. Learn how to feature a topic so it appears in this list.
  7. When you are happy with the order of the topics, click Save Order at the bottom of the list.

Note: To revert the list back to the original order, click Reset before clicking Save Order.

Your changes are reflected in the Featured Threads component on your live community site.

Note: When new topics are added to the Featured Threads list, they are added to the bottom of the list, until you manually move it to a new position.

Learn more about Featured Topics and how to display them on your community.

Updates to the My Settings page

We have renamed and moved the Personal Profile and Social Connect tabs in the user My Settings section. Specifically, we have renamed Personal Profile to Personal and Social Connect to Social and moved them to be next to each other.

 

We’ve made these changes to simplify the language and co-locate these settings in preparation for other changes we’ll be rolling out in future releases.

Additions to LSI Bulk Data API

We have added new fields to the LSI Bulk Data API to enable users to now query for SSO ID, Geography, and Unique ID, as follows:

  • user.sso.id: SSO ID of user taking action, if SSO ID is available
  • document.id: Unique identifier for each event
  • request.geo.city: City of user taking action converted from browser IP using IP2Location DB 11
  • request.geo.country_code: Two-character country code from ISO 3166 of user taking action converted from browser IP using IP2Location DB11
  • request.geo.geohash: Geohash using latitude and longitude of user taking action converted from browser IP using IP2Location DB11
  • request.geo.postal: Zip/postal code of user taking action converted from browser IP using IP2Location DB11
  • request.geo.region:  Region or state name of user taking action converted from browser IP using IP2Location DB11
  • request.geo.timezone: + or - hour offset from UTC of user taking action converted from browser IP using IP2Location DB11
  • request.geo.latitude:  Latitude of user taking action converted from browser IP using IP2Location DB11
  • request.geo.longitude:  Longitude of user taking action converted from browser IP using IP2Location DB11

Learn more about Using the LSI Bulk Data API.

New method on http.response FreeMarker context object

If you use customized URLs in your community, you can set the canonical URL link element on the response using http.response.setCanonicalUrl(http.request.url). This method takes the request URL and sets it as the canonical URL to improve search engine optimization (SEO).

Note: This method, like other http.response methods that set something on the response, can be used only in the Page Initialization Script.

Let’s looks at an example. By default, Lithium enables you to filter on a single label, but some communities want to filter by multiple labels. You can filter by multiple labels by passing them in the request URL. A request URL for the Idea Exchange Page that filters on ideas with the labels "woodworking" and "furniture" looks something like this:

https://example_community.com/t5/IdeaExchangePage/idb-p/your_project_gallery/label-name/woodworking/label-name/furniture/page/2

This customized URL is supported; however, by default, Lithium includes only the first label in the canonical link element on the response:

<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/><link href="https://example_community.com/t5/IdeaExchangePage/idb-p/your_project_page/label-name/woodworking/page/2" rel="canonical"/>

Stripping the second label name can impact SEO for the community.

The code snippet below shows how to use http.response.setCanonicalUrl(http.request.url) to set the request URL as the canonical URL using FreeMarker code in your Page Initialization Script:

<#if page.name = "IdeaExchangePage" >

${http.response.setCanonicalUrl(http.request.url)}

</#if>

With this code in place, the canonical link element in the response includes both labels as passed in the request.

<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/><link href="https://example_community.com/t5/IdeaExchangePage/idb-p/your_project_page/label-name/woodworking/label-name/furniture/page/2" rel="canonical"/>

Submit email templates with the Lithium-Klout SDK (Open Beta)

This feature is released in Open Beta. We now support submitting email templates to your stage server using the Lithium-Klout SDK. Localized templates are supported. Note that the icons, alerts, and confirmations used to identify email templates in the SDK plugin which prevent Studio overrides are not implemented at this time.

For instructions on how to submit email templates, see the SDK documentation and go to Develop > Customize.

 

Wrap components in a div container

We’ve added documentation for a way to wrap components in a div container with a specified class name directly in a page quilt. Read about this feature in the Developers Knowledge Base.

You Found It. We Fixed It.

  • We have fixed the issue where you received an error when trying to view drafts or unpublished revisions of a TKB article from the TKB dashboard.
  • We have fixed the issue where the private note notification email was always using the “alternative” content type, even when the Plain text option was selected under My Settings > Subscriptions & Notifications > Email Format. Now, the text version of the email is set when this option is selected.
  • Previously, when the reason notifications feature was enabled, and you clicked the Cancel button while editing a message/thread (Options > Edit Message), you received an unexpected error. This issue is now resolved.
  • Responsive fix: We have fixed the issue where the User Slide Out menu did not open when the Community Navigation widget was not also on the page.
Updated 2 years ago
Version 9.0

4 Comments

  • Woot! Excited about being able to change sort order of featured threads. Hopefully the same can be applied to floated posts soon. 

  • Is there any way to order the list of featured threads returned through API calls in a way that respects the community admin settings?

     

    Currently Featured threads calls on the API are returned in date order but it would be useful where custom components are in use to display featured threads in the order specified in admin settings.

  • I had the same problem with TKBs + manual sorting a while ago, the following is a comment in my code:

     

    As a workaround to get threads in order of the manual sorting order which is only accessible by
    /topics API call, also topics/style/<style>/recent does not inherit this manual sorting order, so
    we have to first get the topics and then extract the thread objects with another REST call to message.thread.@href.

    The difference between topics and threads is that a thread contains the messages within it, a topic does not!

    It would be much easier if the Lithium devs had implemented this manual sort order option with a request parameter for "message_viewer.topic_sort_order", e.g. "topic_sort_manual" or something equivalent, so the REST request URL could be postfixed with <restapiqueryurl>?message_viewer.topic_sort_order=topic_sort_manual

     

    looks like nothing happened here regarding consistency between default components and API output. Please fix that =)!