Blog Post

Release Notes & Updates
5 MIN READ

Lithium Community 18.4 Release Notes

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

The 18.4 Release includes the GA Release of GDPR support for Lithium Communities, the ability to include user profile pages in Community search results, the release of the Community Android SDK 1.3.0, and more. 

 

New Features 

 

GDPR GA release 

General Data Protection Regulation (GDPR) is a data protection regulation that aims to give individuals higher control over how their personal data is collected and used. Using GDPR, the European Parliament, the Council of the European Union, and the European Commission intend to strengthen data protection for all individuals in the European Union. The regulation is intended to go into effect on the 25th of May 2018. This means that organizations that collect and use personally identifiable data of individuals must comply with the GDPR guidelines by the 25th of May 2018. 

Starting with the 18.4 Release, GDPR support for Lithium Communities is now officially GA.  

Refer to our documentation to learn more about Lithium Community GDPR SupportGDPR-related tasksand general FAQs. 

GDPR support is now available and enabled by default for all communities. However, to control the rollout of GDPR to your customers, the admin must manually turn it on from Community Admin, as follows:  

  1. Sign in to the community as an Admin.  
  2. Go to System > Admin.  
  3. Select or clear the Enable GDPR setting. 
     
  4. Click Save.  

New in this GA release ithe ability to remove personal Facebook-related information linked to your community account 

Ability to remove personal Facebook-related information linked to your community account 

If you have opted to connect your Facebook account to your community account, your Facebook user name and gender information is stored in the Lithium Community.  

As part of GDPR compliance, when you disconnect your social account from community, this information is also deleted from your Lithium account. 

Learn more about Lithium Community GDPR SupportGDPR-related tasksand general FAQs. 

SEO updates for user profile pages  

By default, we do not index user profile pages or included u in search results for external search engines (for example, Google).  

Lithium intentionally blocks profile pages from being crawled, but this new feature enables you to remove this restriction if you want your community's profile pages to be crawled for SEO purposes and enable external search engines to crawl the contents available on profile pages.

To enable the indexing of user profile pages and their inclusion in search engine results, open a Support ticket. 

Permission name change 

We have changed the name of the Use HTML which can embed third-party content permission (introduced in Community release 17.7) to better reflect its purpose and function. The Sse of HTML which can embed third party content permission is renamed to Embed content hosted by third parties. We have also updated the tooltip to clarify how the permission works. 

Add a View All link for the message-view.widget.tags component 

When we updated the Forum Message, Blog Topic Message, and Idea Message quilts for Lithium Responsive, we chose to remove the View All link on the tag display component (message-view.widget.tags). This link took the user to the Tag Details Page, which could then be used to access the Tag View Page. 

By popular demand, we now enable you to configure the tags display component in the default message view for forum, blog, and idea posts to add the View All link to the component. 

 

You can choose to display the View All link as an icon or as text. For instructions on how to configure the message-view.widget.tags component, see Configure tag display in the Responsive message view. 

Lithium Community Android SDK updates 

We are releasing version 1.3.0 of the Community Android SDK. Watch the Community Android SDK Release Notes for details.   

Updates to Product Mentions appearance

When you mention a product in a community using the #mention syntax, the hashtag is now included in the link generated. For example: Khoros Communities. We made this change to aid feature discoverability. If you can revert to the previous appearance using CSS, if desired. See About product mentions for details. 

API Changes 

Filter users by SSO ID 

You can now filter queries to the Users collection by the sso_id field in the WHERE clause. Supported operators are = and IN(). 

Examples: 

SELECT * FROM users WHERE sso_id = '12345' 

SELECT * FROM users WHERE sso_id IN ('12345', '67890') 

Change to /roles/id/role_id/users/count endpoint 

The Community API v1 /roles/id/role_id/users/count endpoint used to include deleted users in the count. This created confusion for customers expecting the count to return the same number of results as the /roles/id/role_id/users endpoint. The /roles/id/role_id/users endpoint does not include deleted users in its response. 

We have changed the /roles/id/role_id/users/count endpoint so that it no longer includes deleted users. 

Note that Community API v2 also excludes deleted users in response to queries to the Users collection for role count. For example, SELECT count(*) FROM users WHERE roles.id = 't:Administrator'. 

You Found It. We Fixed It. 

  • We have fixed the issue where quoting a reply to a post that includes an @mention resulted in an @mention email notification being sent to the mentioned person. These email notifications are no longer sent out when doing a quoted reply. 
  • We fixed an error that was causing errors when attempting to create Salesforce tickets via the Case Portal. 
  • Edits to the Robots Exclusion Protocol (robots.txt) made in Studio and published with Studio Publish now appear correctly only all nodes in a horizontal scale (HS) cluster.
  • Community API calls to retrieve subscription counts for boards (/boards/id/board_id/subscribers/email/board/count for API v1 or a call using a LiQL query like SELECT count(*) FROM subscriptions WHERE target.type = 'board' AND target.id = 'testBoard' for API v2now return the correct subscription result after a user account with a subscription to the specified board is deleted. 
  • We fixed an issue where previously uploaded attachments displayed a "Virus scan in progress" message indefinitely. The message now disappears after the virus scan is complete. 
  • As an unintended result of 17.8 bug fix, the Latest Posts By <Username> and Topics I've Participated In components began to apply the Jump to first unread post in a topic setting (set in My Settings > Preferences > Linear Layout) when clicking on replies in the components. This result inadvertently introduced confusion to end users. We have returned these components to their original behavior when the Jump to first unread post in a topic setting is selected. When clicking on a topic, the end user is taken to the first unread post in the thread for the selected topic. When clicking on a reply, the user is taken to the selected reply. 
  • We have fixed the trigger error that was preventing users from creating a Salesforce case through the Web-to-Case API format. 
Updated 7 months ago
Version 24.0

10 Comments

  • Ability to include user profile pages in community search results -- Thanks!

  • Regarding user profile pages appearing in community search results, does that just relate to the biography field? What other content on the profile page would be searchable?

     

    Thanks,

     

    Jason 

  • I'm perplexed at this. What is the advantage of exposing user information to search engines? Are there not GDPR implications? Managing an opt-in/opt-out for this on a community of a million or more members seems impossible.

  • With the return of the "View All" tags feature, will you now be able to manage tags from that page (if you have the correct permissions)?  With the switch to responsive, being able to edit/manage tags on a post level was cumbersome - you would need to edit the post itself as the original user. Hopefully, with bringing back the View All, it will also allow for managing of the tags in an easier fashion. 

     

    Thanks! 

  • JohnD's avatar
    JohnD
    Khoros Alumni (Retired)
    7 years ago

    Warren_Brill - 

    Per your GDPR concern, any PII on profile pages can only be viewed by users with admin-level permissions unless a user explicitly sets their privacy settings to display them to all users (this is limited to displaying first name, last name, email address and online status). Be default, user privacy options are set to display to “no one” in Community Admin > Users > Privacy Defaults. These settings apply to all newly registered users or users who have never saved a changed in their settings, but it will not override these options for users who have already made/saved changes in My Settings > Preferences > Privacy.

     

     

  • There is a spelling mistake in the GDPR tooltip. 

     

    Community Admin > Users > Profile Defaults | Hover over tooltip for 'Enable members to close their community account' 

     

     

     

  • JohnD's avatar
    JohnD
    Khoros Alumni (Retired)
    7 years ago

    Thank, tyw. Fixed in code; will be reflected in next release.

  • "Enable members to close their community account" is grammatically incorrect (incorrect singular/plural matching). It has to be "Enable members to close their community accounts" [note the "s" at the end]. An alternative, but somewhat unwieldy, would be "Enable a member to close his/her community account".