• Security Announcement
• You found it! We fixed it!
• General
• Accessibility

Security Announcement 

In this release, we have updated the “Moment.js” libraries to its latest version (2.29.4) to protect your communities from possible vulnerability. 

You found it! We fixed it!

General

• In this release, the character limit of Content Filter's words has been increased to 400 characters to support complex regex.

• The issue where the Image Resizer service failed to resize uploaded images is fixed. 
  
  
• Previously, when moderators moved unanswered threads in the Spam Quarantine page to their original locations, these threads were not automatically escalated to Salesforce. This issue is now fixed. Now the service to escalate these unanswered threads successfully escalates them to Salesforce.
  
  
• When communities were migrating to Khoros Community and when you executed the API to bulk-load the TKB articles or Blog posts with a 50-limit call, the migration failed. This issue is fixed. 
  
  
• Previously, when you submitted an invalid ‘Product Catalog XML’ to run a product sync, all the previous products and categories were deleted without an error message being displayed. This issue is fixed. Now, when you run an invalid Product Catalog XML, an error message is displayed.
  
  
• The issue where members received error messages while adding emojis in the Biography field under My Settings page is now fixed.
  
  
• The issue where members receive email notifications for private messages even though the option to receive such messages (under User Profile > Preferences > Private Messenger >Turn on private messages) is turned off.
  
  
• Previously, members on communities v23.2 with the inline reply editor and forums v4.1, and the forum.topic.lazyLoad configuration set to true, were unable to reply to threads in the past. 
  
  
• Previously, community members using Forum v5 and the reply-list component on the Forum Topic Page quilt couldn't reply to threads if the forum.topic.lazyLoad configuration was set to false. An error message would appear. However, this issue has been resolved and the fix is now available on Communities v23.2 and later. 

Accessibility 

• The issue where members were not able to close the menu option using the Escape or Enter keys on the keyboard is fixed. 
  
  
• It was found that in communities that used the common.widget.user-navigation-combine component for the drop-down menu, the up and down arrow keys on the keyboard did not move the cursor accordingly. This issue is fixed.
   
• It was found that the Share, Reply, and options menus were not mapped with their respective post name, and the screen reader did not announce the members (Username) who created the post. This issue is fixed.
   
• The issue where in some communities the text did not have sufficient color contrast is fixed. 
  
  
• Previously, members were not able to navigate to and access the option to add cover images to their blog posts or knowledge base articles using the keyboard. This issue is fixed. Now, the screen readers read out the options to add cover images to their posts.