New Features

• Performance improvements for communities using a Responsive-based skin (GA)
• New real-time virus scanner notification option
• New option to cancel an attachment upload
• Community Plugin SDK Version 1.7
• API updates

Performance improvements for communities using a Responsive-based skin (GA)

In the 19.5 Release, we announced the Early Access of some CSS performance improvements. Specifically, we improved the overall performance and page-load speeds for communities using Responsive or a Responsive-based skin. When enabled, you would see a Speed index improvement on CommunityHomePage, CategoryPage, SearchPage, ForumTopicPage, ForumPage, ViewProfilePage.

With these improvements, only the CSS that is sufficient and necessary to render each page type is loaded synchronously. The rest of the website CSS is served asynchronously.

Note: These performance improvements work best for communities with customizations that follow standard CSS syntax. Communities not adhering to these CSS rules might need to clean up their community's CSS before enabling this feature.

We are excited to announce the GA Release of this feature.

To enable these CSS performance improvements, open a Support ticket.

New real-time virus scanner notification option

Khoros's real-time virus scanner service checks for viruses in files attached to posts to protect your community from becoming a distribution point for malicious software. Basically, this service:

• Scans all attachments while they are being uploaded and removed any malicious attachments before getting posted to the community.
• Keeps the service’s virus definitions up to date.
• Periodically scans previously uploaded files to catch any malicious files based on latest virus definitions and updates. (Infected files are automatically removed, any references to the file are removed.)

In this release, we have added a new configuration option that enables you to disable the sending of the daily email digest if no malicious files were identified.

To set the daily digest option for when no malicious files are found: 

1. Sign in to the Community as an Admin.
2. Go to System > File Attachments.
3. Select or clear the Send daily digest email even when no malicious files found option as you want.
   
   When selected, the daily digest email is sent, regardless of whether malicious file attachments were found.
   When this setting is cleared, the daily digest is sent out only when malicious files have been found within the last 24 hours.
4. Click Save.

Learn more about the real-time virus scanner service.

New option to cancel an attachment upload 

In the 19.6 release, we announced the ability for authors to drag and drop file attachments into the text editor.

Depending on the size of the file attachment, an upload could take a long time. We have improved the UI for the drag-and-drop experience to provide a “cancel” option.

During the upload process, just click the “x” icon for the file you want to cancel the upload for.

Community Plugin SDK Version 1.7

We released version 1.7 of the Community Plugin SDK. This new version includes a bug fix that caused a Manifest.MF file unexpected error when a user ran li submit-plugin.

Customers using the SDK must update their plugin project. See update instructions in Update the SDK plugin.

API updates

We now support MATCHES when filtering LiQL queries to the Messages collection by author.login. Read more about MATCHES in Using LiQL.

A query like this:

SELECT id, author.login FROM messages WHERE author.login MATCHES 'user'

If multiple user logins contained the string 'user', the result would look something like this:

{
  "status" : "success",
  "message" : "",
  "http_code" : 200,
  "data" : {
    "type" : "messages",
    "list_item_type" : "message",
    "size" : 25,
    "items" : [ {
      "type" : "message",
      "id" : "982",
      "author" : {
        "type" : "user",
        "login" : "User1"
      }
    }, {
      "type" : "message",
      "id" : "935",
      "author" : {
        "type" : "user",
        "login" : "User1"
      }
    }, {
      "type" : "message",
      "id" : "1073",
      "author" : {
        "type" : "user",
        "login" : "User10"
      }
    }, {
      "type" : "message",
      "id" : "1074",
      "author" : {
        "type" : "user",
        "login" : "User10"
      }
    }, {
      "type" : "message",
      "id" : "570",
      "author" : {
        "type" : "user",
        "login" : "User1"
      }
    } ]
  },
  "metadata" : { }
}

You Found It. We Fixed It.

• We fixed an issue where the message editor displayed as blank on mobile devices using Editor V2 on communities which have Ooyala video upload disabled. Now, the message editor displays fine in this scenario.
• We have fixed the issue where, in some rare cases, the timestamp of the post date for a post was incorrect. This issue occurred only when friendly dates were not used, resulting in the “date” portion of the timestamp being formatted using the server timezone, while the “time” portion of the timestamp was formatted using the user’s timezone.