Blog Post

Release Notes
4 MIN READ

Khoros Communities 21.7 Release

AshaC's avatar
AshaC
Khoros Staff
4 years ago

Features

Integrate Zoom with Community Events

API Updates

RSVP API

You found it. We fixed it!

Features

Integrate Zoom with Community Events

Today, more and more meetings are moving to virtual spaces. Khoros Community Events now supports full integration with Zoom Meetings and Webinars. Integrating Events with Zoom enables community members to join the Zoom meetings and webinars directly from the community.

With this integration you can:

  • Create events to host Zoom meetings and webinars! All you have to do is paste in the Zoom URL. Now you can ask questions, discuss, and share follow ups to increase overall engagement in the threaded discussion.

         

     

  • Host Zoom Meetings from a community event while providing full access to the Zoom options and features

        

     

  • Host Zoom Webinars from a community event while providing full access to the Zoom options and features

         

     

More info

API Updates

RSVP API

We have updated the Events RSVP API to enable a member to add or remove the RSVP response on behalf of another member. Members with the “Create Events” permission now gain this ability.

Learn more about move events API

You Found It. We Fixed It.

  • Earlier, the Internet Calendar Scheduling(ICS) files for community events uploaded incorrect schedule information in the Outlook calendar. This issue is now fixed, and all community events are now added to external calendar programs with correct information.

  • We have fixed the issue where your editing position jumped to the beginning of a post while formatting any text at the bottom of a lengthy post. 

  • The issue with the preview of attachments to posts throwing misleading error messages is now resolved.  You can now preview all attachments successfully.
     
  • We have fixed the issue where some HTML characters in the case related fields in the Case Portal were encoded while sending information to Salesforce. Now, these HTML tags are no longer encoded. 

  • We have fixed the issue where the Top Tagged Posts widget displayed archived content.

  • We have fixed the issue where the post count for a particular label on the Labels page did not decrease when posts with this label were archived. With this release, the post count for labels associated with archived posts will decrease as the post is archived. 

  • The Forum Topic Pages in Forums v5 with the Inline Editor enabled took more time than expected to load. We have improved the load time with this release, and all the inline reply controls load faster. 

  • We have fixed the performance issues with the load time when users with a large number of subscriptions navigate from the Notification Feed page.

  • There was an issue with the notifications feed page, that when members use the notification bell icon to view new messages, the page was empty. The messages are loaded only after a page refresh. With this release, the notification feed page will display the notifications correctly when members access them from the bell icon. 

  • Khoros Communities has upgraded to the latest version of the XStream library. 

  • We have fixed the issue where users with simple HTML privileges could access and edit unpermitted HTML classes. This issue was specific to communities using a security feature designed to restrict allowed class values. This fix is available to all communities using this feature and are on version 21.5 or later. Note that this will prevent the use of all but a predefined list of values for HTML classes and can be customized on request. Reach out to Support if you have any questions or concerns. 

Accessibility fixes

  • Earlier, the tooltip popup did not collapse when you clicked the Esc key, thus preventing users from viewing other controls. We have fixed this issue. On pressing the Esc key, the tooltip popup collapses for all tooltips across the community platform. 

  • There was an issue where the color contrast between community page elements and the background was insufficient for low-vision users to view the elements clearly. This fix ensures the contrast between foreground and background colors meets the WCAG 2 AA contrast ratio thresholds. 

  • We have fixed the issues where the JAWS screen reader did not identify the mandatory fields on the forms. Now, screen reader-dependent members can recognize the required fields, controls, and functionality. 

  • We have added titles for iFrame in the HTML code for all the dialog and drop-down menu components with this release. 

  • We have fixed the issue where the error message “Please input a complete URL”, while uploading an Image via URL to a given post, was not being read by VoiceOver.  

  • We have fixed the issue where while navigating on the search page, the tab focus and element role was not present on the “clear” link on the search form component. 




 

Updated 5 months ago
Version 4.0
  • I'm doing some testing on my stage environment and I noticed two new options that exist in the discussion style and idea exchange that allow the OP to not allow:

    Tags or Kudos.

    I don't see any admin settings for this. 

    if someone checks that box on the Idea exchange post, they will be blocking others from voting on it.

    Anyone else see/notice this?

     

      

  • AshaC with 21.7 the items in the top right of our header are reversed. Support says this is an expected change due to an accessibility fix. But I don't see it mentioned here. Is it truly expected?

    Please see this thread for more info.

  • AshaC our Production environment went to 21.7 yesterday but we discovered that now only users who have the 'create event' permission can RSVP to an event, which to be does not seem to be the objective of the above change to the API.

    We have opened a support case but, especially if you use the API for RSVPs, be careful when updating to 21.7 as you may encounter this issue to.


  • SohilM's avatar
    SohilM
    Lithium Alumni (Retired)

    allensmith81 We are working on this on priority and will roll out a fix soon. I will update once resolved. 

  • SohilM 

    Love it thank you, for now we have implemented a workaround by making the api call a restadmin call, not ideal but it works.