Lithium Community 18.1 Release Notes

Community release 18.1 brings bug fixes and minor improvements to Moderation Manager. We are also happy to announce the Community iOS SDK open beta program, the Salesforce Lighting Connector 4.0 open beta program, and version 1.2.5 of the Community Android SDK.

• New Features
• API Changes
• You Found It. We Fixed It.

New Features

• Community iOS SDK Open Beta Program
• Lithium Salesforce Lighting Connector 4.0 Beta Program
• Define the length of a message displayed in Moderation Manager
• Community Android SDK version 1.2.5
• Deprecation Announcement: asset.get in Skins
• Spam Quarantine Alert Messages in Forum Boards

Community iOS SDK Open Beta Program

We are pleased to announce the Lithium Community iOS SDK Open Beta Program.

 

The iOS SDK makes it easy for developers to integrate Lithium Community in their iOS apps quickly and easily. Developers can get started with the mobile-support user interface (UI) or go deep with a fully-customizable API-backed integration.

 

We've tried to make getting the iOS SDK up and running as easy as possible. Check out the SDK projects on GitHub, and follow the instructions to get started. You can use our example project as both a starting point and a way to see how the libraries can work together in your app.

• GitHub: Lithium Community iOS SDK Core
• GitHub  Lithium Community iOS UI Components
• GitHub: Lithium Community iOS SDK Example

 Note: In order to create the best possible product and experience, we will continue to iterate on the SDK throughout the beta period. Features may change before the product is generally available. We will post updates and changes in the Current Betas forum.

 

See the Getting Started with the iOS SDK Open Beta article in our Online Communities blog for all the details you'll need to start your iOS integration.

 

Lithium Salesforce Lightning Connector 4.0 Open Beta Program

We are happy to announce our open beta program for the new Lithium Salesforce Lightning Connector. This connector is now available in beta to support the Lightning Experience and to ensure continued compatibility with updates introduced by Salesforce.

 

Watch the Online Communities blog next week for an article with details about participating in the beta program.

 

The Lightning version of the connector includes the following new features:

• UI redesign and refresh

The Lightning experience provides a redesigned UI and an overall update to the look and feel of the connector. The redesign does not change any of the functionality or workflows, but the arrangement of components in a page or the layout of some pages may have changed as part of the design improvements.

• Additional information in tooltip format

In the Lightning experience, hover over highlighted text to find additional information about a user or component. This information appears in the form of a tooltip or pop-over and supports rich text including clickable links.

• Drag-and-drop capability for the Record Page

The Lightning experience of Salesforce now includes drag and drop functionality while adding and arranging page components.

 

See Install and use the Salesforce Lightning Connector for installation and configuration instructions. See Features of the Lithium Salesforce Lightning Connector to learn more about the new connector.

 

Define the length of a message displayed in Moderation Manager

We have added the Length of the message that displays in Moderation Manager setting to the Community Admin > Mod Tools page. This setting defines how much of a message to display in Moderation Manager.

• An empty value displays the entire message. (This is the default setting.)
• Set the field to 2-500 (characters) to truncate the message to the desired length.

 

 

Community Android SDK Version 1.2.5

We've released a new version of the Community Android SDK. In this version, SDK initialization is decoupled from synching the Android app with the Community server. This decoupling requires that you make a separate call to sync your app with the Community server after initialization but before making any calls to the Community REST API. See details and examples in the Community Android SDK wiki.

 

Deprecation Announcement: asset.get in Skins

We will stop supporting asset.get("destination_url")to reference assets in skins in 18.4 and begin migrating customer skins that use the FreeMarker method.  See Deprecation Announcement: FreeMarker in Skins for details about the migration path.  Note that you will continue to use the asset context object when referencing assets in component and endpoint FreeMarker code.

 

Spam Quarantine Alert Messages in Forum boards

We have added visual alert messages to topic and reply posts marked as spam in Forum boards. (Support for this feature in other board types to come in a future release.) These new alerts appear when Community users come to a post that has been marked as spam via a permalink, say in a Community email digest or in a source from outside the community. The message will differ depending on the user viewing the message.

 

Administrator and Moderator View

An Administrator or Moderator sees a message that reads "Marked as spam. Visit the spam quarantine to manage this message" and includes a link to the Spam Quarantine page.

 

 

If the message marked as spam is a reply, the reply message is hidden and the alert appears directly under the subject.

 

Message Author View

When the message author arrives at the message via a permalink, the author sees a message that says "Marked as spam. If you believe this is an error, submit an abuse report." The message includes a link that opens an abuse report form.

If the message marked as spam is a reply, the reply message is hidden and the user sees the alert directly below the topic subject.

General User View

Users who are not Administrators, Moderators, or the message author see a message saying that the message is not available.

 

 

 

 

 

API Changes

Moving messages in a Lithium Community can cause orphaned messages (where messages have a root ID different from the topic message of the message thread).

The /messages/linear call in Community API v1 now skips orphaned messages in the response; however, the /message/linear/count call does not omit orphaned messages. Due to the different behavior between calls, you might see a discrepancy between the number of items returned from each.

 

If you experience a discrepancy between the number of results returned between /messages/linear and /messages/linear/count, contact Lithium Support to resolve the root ID issues with orphaned messages.

You Found It. We Fixed It.

• If the currently logged-in user had more than one community user associated with the same email ID, then, the postback action was associated randomly to one of the users associated with this email ID. To fix this issue, we have added a Fallback Community User field to Feature Settings.
• To configure the fallback user:
  1. Log into your Salesforce account.
  2. Go to the Custom settings tab > Feature Settings.
  3. Click Edit.
  4. In the Fallback Community User field, specify the valid community Username of the user that you want to configure as the preferred user for postback options. This is used when there is more than one community user associated with this email id or in scenarios where a community user does not exist.
     
     Note: If you do not specify a fallback user, the user associated with postback actions will be the default user specified in Salesforce > Custom settings tab > Community Settings.
     
  5. Click Save.

• We have fixed an issue where an invalid file name error was encountered while trying to save Sass-related changes in Studio even though a valid file name was specified.   
• We have fixed an issue where Private Categories were being duplicated in the hamburger navigation menu created by the common.widget.slide-out-nav-menu component for Responsive sites. This error would occur only if a user logged back in after an open Community page timed-out.  
• We have fixed an issue where new users could be duplicated if the new user was using a mobile device to view a page containing Active Cast content served by an SSO-enabled, horizontal-scaled (HS) community. 
• We have improved the workflow of the Password Reset token to increase security while using the password reset option. 

• We have fixed an issue that caused localized versions of the Moderation Reason Notification email template to be inconsistent with the original content specified in the primary version of the template. Localized versions of the email template are now are consistent with the original version. 
• Previously, a conflict would occur if SAML was enabled while using the URL Fetcher feature. This conflict between SAML and the URL Fetcher feature has been resolved. 
• We have fixed an issue that caused messages with JavasSript to be posted as messages containing the complete code if the Notify Moderators of filter action (board reports, email, or private message) option was enabled. The content filter notification would bypass normal HTML perms check. This issue has now been resolved.  
• The MATCHES operator in LiQL queries now handles custom fields as expected in the WHERE clause.
• We fixed a regression that caused the  MATCHES operator in LiQL queries to handle “one or more” search cases incorrectly.  The MATCHES operator once again works as described in the “Query for one or more terms” section under Combinatorial searches in the WHERE clause.

• We have fixed an issue where updates from Salesforce to Lithium Community did not work as expected when the Community used the Lithium API Proxy. To fix this issue, we have added two new fields to the Community Settings page in Salesforce. Note: You must contact Lithium Support to get the value of one of the new settings.
  Follow these steps if you have API Proxy enabled for your community and have a Salesforce integration:

  1. Contact Lithium Support and ask for the Tapestry Context Name for your community.

  2. Log into your Salesforce account.Go to the Custom settings tab > Community Settings.

  3. Click Edit. (If you have not created a custom configuration, then click Create.)
     

  4. Select the Is Proxy Enabled checkbox.

  5. In the Context Name field, specify the context name you received from Lithium Support.

  6. Click Save.

• We fixed an issue where, when a post had multiple labels, all the labels took the user to the same destination rather than the appropriate label page for the specific label.