Community release 18.2 brings the limited release of GDPR features, migration to full HTTPS encryption for all communities, and bug fixes.
New Features
- Limited Release: GDPR for Community
- Migration to full HTTPs Encryption for all Customers
- Search Filter in the Product Editor tab
Limited Release: GDPR for Community
GDPR (General Data Protection Regulation) is a privacy-related regulation standard introduced by the European Parliament, the Council of the European Union, and the European Commission. This regulation is intended to strengthen data protection for all individuals in the European Union. GDPR enables individual users (data subjects) to view, edit, export, and delete the Personally Identifiable Information (PII), that they may have provided to data controllers (brands) and data processors (online communities). This regulation will come into effect from the 25th of May 2018.
GDPR-related capabilities from Lithium will be available in phases. For those customers interested in using some of the initial features, please contact Lithium Support to discuss your needs. In the 18.2 release, Lithium supports a few features such as PII retrieval and PII deletion. Additional GDPR-related features will be available as part of upcoming releases and are planned to be delivered by early May 2018.
Enabling GDPR
Please contact Lithium Support to discuss your needs. The Support team will enable the limited features as needed.
For more information see:
Migration to full HTTPs Encryption for all Customers
Lithium is moving all customer communities to full HTTPS encryption. This change protects your organization and your end-users, while paving the way for performance improvements and great, new features.
With the 18.2 Release, Lithium is deprecating support for the following community configurations:
- HTTP-only community mode
- "Mixed mode" HTTPS support
These configurations will remain available through Community release 18.7 (August 2018). After 18.7, support for these configurations will be removed.
For details about the migration path, see Full HTTPS Encryption for all Communities.
Search Filter in the Product Editor Tab
We added a search field to the Community Admin > Features > Products > Product Editor tab.
API Changes
- FreeMarker: Clear the top-level category with FreeMarker
- Community API v2: Pass the API Session Key in the Header
FreeMarker: Clear the top-level category with FreeMarker
We've added the top.clear() method to the FreeMarker nodes context object to clear the top-level category set for a community.
Use this method if you need to reset the top-level category. After you have cleared the top-level category, you can set a new top-level category using nodes.top.setCategoryDisplayId.
Community API v2: Pass the API Session Key in the Header
As of Community 18.2, you can pass the API session key as the value of the Li-Api-Session-Key header when using the Community API instead of passing the session key in the URL. Passing the session key in the header is now the recommended way of passing the session key. See API session key authentication for details. The Li-Api-Session-Key header is supported by both Community API v1 and v2.
- We have fixed an issue where Admin Metrics were not visible to Admins or other users with the similar permissions while using the 18.1 version of Community.
- We have fixed an issue where a question could not be posted for a product if the product category did not have a board attached to it.
- We have fixed an issue where the Forgot Password link would redirect to the wrong page.
- We have fixed an issue where skins created in SDK were not marked as created in SDK and could not be edited in Studio. This issue occurred only when using Community release version 17.12 and later.
- Previously, when the Use Search Before Post "similar articles" workflow feature was enabled, clicking the View More Results link after search would display an error. This error would occur only for the TKB discussion style. This issue has now been fixed, and the View More Results workflow now works as expected.
- We have fixed an issue where the Insert Video button remained enabled even after the video had been uploaded. Clicking this button again would upload the same video a second time. This issue has now been fixed.
- We have fixed an issue where the Sync History tab under Community Admin > Features > Products would fail to work as expected and display an exception.
- We have fixed an issue where CSV files of badges could not be downloaded if the badge name contained commas. This issue occurred only while using the Chrome browser.
