Lithium Community 18.4 Release Notes
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.
- GDPR GA release
- SEO updates for user profile pages
- Permission name change
- Add a View All link for the message-view.widget.tags component
- Lithium Community Android SDK 1.3.0
- Updates to Product Mentions appearance
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 Support, GDPR-related tasks, and 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:
- Sign in to the community as an Admin.
- Go to System > Admin.
- Select or clear the Enable GDPR setting.
- Click Save.
New in this GA release is the 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 Support, GDPR-related tasks, and 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.
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.
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'.
- 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 v2) now 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 a 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.