Khoros Communities 21.8 Release

21.8 is a minor release. As communicated earlier, minor releases contain defect fixes and minor enhancements. Minor releases are not made available in production by default. To request an on-demand upgrade, contact Support.

General fixes

• There was an issue on communities with Knowledge Bases that had the default user setting Start new articles and edit drafts set to grant and Use full HTML in posts and signatures and Allow user to use advanced HTML in posts and signatures set to deny.
  
  When members with no special permissions or roles tried to preview their post in the “Questions and Answers” or “Solutions” templates, they received an error. This issue is fixed and members can successfully preview or submit the article without receiving an error.
  
  
• We have fixed the issue where archived posts were not viewable or searchable from the Content Archives page. 
• We now enable content filters to support characters that require four or more bytes in UTF-8. With this change, the maximum character limit for a content filter is now 190 characters.
• We have fixed the issue when the message size of an email notification was too large, causing a memory issue that resulted in the email notification taking too long to send out. 
• In 21.5 and later releases, any case that was not created from the Case Portal displayed NULL in the Description field when the case was viewed in Case Portal. This issue is now fixed.
• In 21.7 and later releases, pages that displayed featured topics threw an error after topics were un-featured. This issue is now fixed.

Accessibility fixes

• Previously, the Options menu did not close automatically when changing focus from the menu to another UI element. Now, the Options menu closes automatically when you change focus using the Tab key. 
• We have fixed the issue where the keyboard focus moves to the top of the page after pressing the Escape key from the Group Hub Invite dialog box. Now, the focus remains on the Invite button after pressing the Escape key.
• When you opened the Options menu in the "Reply to a message" page, the focus was not on the menu and was not navigable using keyboard keys. Now the Options menu can be closed with the ESC key and is navigable through arrow keys. 
• The issue where screen readers did not announce “Notify moderator of inappropriate content” in the Edit Report field has been fixed.

API changes

• A query to the Community API v2 labels collection now returns the label text in the id field. Previously, the id field showed the unique numerical ID. The datatype of the id field remains unchanged (String). We made this change to support labels on draft revisions in the future and also enables the id of a label to remain consistent across community environments.