Khoros Communities 25.11 Release Notes
The Khoros Communities 25.11 release delivers critical security updates, comprehensive accessibility improvements, enhanced survey targeting capabilities, and numerous stability fixes across content management, authentication, and search functionality. Classic Applied critical security patches addressing vulnerabilities in jQuery and TinyMCE components. Enhanced username validation to prevent impersonation attempts using visually similar characters from different language scripts. Improved flood control performance, significantly reducing processing time for users with many product associations. Fixed Rich Text Editor alignment not applying correctly to text with inline formatting such as bold or italic. Fixed custom table background colors and styling being stripped when saving blog posts. Fixed Events module errors preventing users from creating, publishing, or viewing events after upgrade. Fixed deleted article history records causing entire version history to be wiped when removing individual draft versions. Added comprehensive accessibility improvements including: keyboard operability for Reply and Follow buttons; proper carousel navigation with skip options; corrected focus order in Tags modal; disabled auto-focus in private message compose modal; added missing alt attributes to images throughout the application; and programmatically associated error messages with form fields. Aurora Implemented advanced survey targeting with configurable prompts based on user authentication status, roles, location, and visit patterns. Fixed critical memory leak in integration points registry that was causing system crashes and performance degradation after 24-40 hours of operation. Fixed private messages failing to load for users with large recipient lists. Fixed users being unable to join hidden groups via email invitations. Enhanced search functionality to properly handle Traditional Chinese, Japanese, and Korean characters. Fixed language preference cookie expiring after 24 hours instead of persisting for the configured 30-day period. Fixed CSV export failures when survey responses were linked to deleted user accounts, now properly marking these as "Anonymous". Added dimension validation for image uploads to prevent pixel flood attacks that could cause memory exhaustion and system crashes. Fixed navigation error flash when users return from profile pages to discussion threads using the browser back button. Fixed blog article delete confirmation dialog intermittently not appearing for users. Fixed page index resetting to first page when unfollowing items on the Follows and Notifications page. Fixed navigation links being replaced instead of appended when adding more than 10 links in the community header. Fixed missing locale parameter causing incorrect privacy policy URLs during SSO registration. Fixed Aurora search bar displaying category IDs instead of user-friendly board names as placeholder text. Fixed custom fields and mandatory native fields not appearing on SSO registration forms for partially registered users. Fixed page crashes when users with Employee role attempted to use @mentions in comments. Fixed ZIP file attachments being stripped when submitting forum replies despite being configured as allowed. Fixed anonymous and deleted users appearing in Top Taggers leaderboard. Enhanced security for video embedding with improved validation and localized error messages. Enabled DNG (Digital Negative) file uploads for communities requiring professional photography file support. Updated robots.txt configuration to prevent Google from crawling legacy Classic URLs, eliminating 404 errors in Search Console. Enabled API access to archived messages using client credentials authentication with proper pagination support. Fixed BrandMessenger component causing page errors when encountering loading issues. Fixed custom React components failing to load on newly created development branches. Fixed custom component localization displaying text keys instead of translated values for Portuguese (Brazil) and other regional locales. Fixed message indexing errors that were preventing proper search functionality for archived content. Added content-type header to SAML logout calls to ensure proper session termination across integrated systems. Prevented OIDC SSO authentication tokens from being exposed in Personal Information exports. Pre-Prod Rollout: November 26-27. Testing window open from November 27 through December 8. Production Rollout: December 10-11 The rollout will follow the standard maintenance windows.Aurora: Filter the Analytics Dashboard
Aurora Analytics enables you to filter data for more granular insights. You can filter based on: Roles Ranks New Topics Username Thread ID To add filters to your dashboard: Open the Account menu and select Analytics. On the dashboard page, select + Filter. Select a filter. Enter relevant values to filter. Select Add. The dashboard displays data for the selected filter. Let's look at an example of filtering data for specific roles. Assume that you want to view metrics and activities by Administrators for the "Products" category in your community for the last 30 days. To filter for this data: Change the scope to Products. Set the date range to Last 30 days. Select +Filter. Select Roles. Select Administrator from the menu. Select Add. The Dashboard displays metrics and activities by Administrators for the "Products" category for the last 30 days. Thread ID You can use this filter to view the metrics related to a particular thread or topic in your community. The Thread ID is the ID found at the end of the community URL. For example, in the below URL, "236502" is the Thread ID for a topic in the community: https://community.khoros.com/kb/supportinformation/khoros-cookies-datasheet-community-care-marketing-khoros-bot/236502 You can add this filter under Dashboard and Reports by selecting the Filter option. You can add more than one Thread ID to the filter. After you select Add, the dashboard displays the metrics for the added Thread IDs or, in other words, the topics with those Thread IDs. Related topics: About Dashboard Settings Scope Analytics data to specific place in the community Set date ranges and data comparison time frame for Aurora Analytics Dashboard Set the Trending Discussions options for Aurora Dashboard View metrics by content type Aurora Analytics Metric DefinitionsKhoros Communities 25.10 - Release Notes
Due to unforseen circumstances, the rollout has been delayed. The updated dates are reflected below. The Khoros Communities 25.10 release includes accessibility improvements, localization enhancements, performance optimizations, and bug fixes across search, messaging, and community management features. Classic Fixed a memory leak affecting system stability by improving object deduplication in integration point processing. Enhanced image upload security validation to prevent potential issues with malformed or malicious image files. Fixed global and embedded search not returning results when using Traditional Chinese characters. Upgraded Image Service to Node.js 22 for improved security, stability, and long-term compatibility. Aurora Fixed recurring 503 Service Unavailable errors affecting community pages by implementing automated service stability improvements. Added full localization support for Turkish (tr-TR). Added full localization support for Indonesian (id-ID). Added full localization support for Vietnamese (vi-VN). Corrected French translations for "Board" and "Post" across UI and email templates. Fixed private messages in the inbox not loading for users with large recipient lists. Fixed an issue preventing users from joining hidden groups via email invitations. Fixed global and embedded search not returning results when using Traditional Chinese characters. Fixed an error preventing administrators from accessing Localized Categories Settings due to duplicate key entries. Upgraded to official undici library release for improved long-term maintainability and security updates. Upgraded Image Service to Node.js 22 for improved security, stability, and long-term compatibility. Enhanced image upload security validation to prevent potential issues with malformed or malicious image files. Fixed intermittent HTTP/2 connection timeout issues by implementing client-side TTL management for pooled connections. Improved accessibility across the platform including: correcting heading structures in Tags modal, editor, and Notifications; properly grouping radio buttons with fieldset and legend elements; updating placeholder text contrast to meet WCAG standards; enhancing tooltips with hover persistence and ARIA labels; grouping related form controls; correcting labeling for filters in Manage Content; adding proper scope attributes to table headers in Manage Members; fixing invalid ARIA attributes in Inbox; and ensuring form error messages are properly announced by screen readers. Pre-Prod Rollout: October 25-26. Testing window open from Oct 27 through Nov 8. Production Rollout: November 10-11 The rollout will follow the standard maintenance windows.
Khoros Communities - Updated Release Process
Updates 13-Oct-2025: Added more details and clarified communication process To improve your experience and simplify our release process, we are updating how we handle Khoros Communities releases. This updated process will start to apply from Communities Release 25.10. What's Changing Communities will have two types of releases going ahead - Standard releases and Patch releases Standard releases happen on a regular cadence and include features and bug fixes. Opted-in customers are automatically upgraded with clear windows to change their decision throughout the process Patch releases address critical issues outside the regular release schedule and are automatically applied to all customers on the latest version Automated support tickets make it easy to manage your upgrade preferences, request immediate upgrades. Normal support tickets can be used to update your Upgrade Notification Contacts (and for all of the requests your account team is also available) Email notifications keep your Upgrade Notification Contacts informed at every stage: release notes publication, stage upgrade completion, and production upgrade completion Production releases are published as scheduled maintenances on our status page, providing real-time visibility and updates if anything changes Clear timelines provide transparency with defined windows to adjust your preferences Standard Releases We will have a standardized release process for both Aurora and Classic. In a standard release, opted-in customers will be auto-upgraded to the latest release. These releases will include features and bug fixes. Version numbers for the standard release will follow the existing version numbers. However, we will no longer be treating releases as major or minor - we will treat every release as a standard release. Throughout this process, you can manage your upgrade preferences using automated support tickets or by contacting your account team, who can assist with any of these requests. The process will begin when we publish the release notes. The release notes will announce the plan and scope of an upcoming release. After we post the release notes here on ATLAS Community, customers will be notified by email and will have six days to change their automatic upgrade preference (opt-in or opt-out). After this period, we will upgrade the stage environments. We will then open a testing window, where customers can test on their stage environments and report any issues through support tickets. Customers will have thirteen days to opt-out if needed, allowing you additional time to validate the release with your specific customizations and integrations, for example. At the end of the testing window, we will perform the upgrade in production for customers who have not opted out during this period. For both stage and production, we will use existing Maintenance windows, as we expect downtime. Production releases will also be published as scheduled maintenances on our status page, where you can find real-time updates if anything goes out of schedule or is delayed. If you are on an older version, you have the following options: Use the automated opt-in ticket to opt back into auto-upgrades (you will receive the next scheduled release) Use the automated upgrade request ticket to upgrade to the latest released version at any time Communication All email notifications for standard releases are sent to your Upgrade Notification Contacts for each instance. To add, remove, or change your Upgrade Notification Contacts, contact our support team or your account team. Release Notes Publication Email When we publish the release notes here on ATLAS Community, your Upgrade Notification Contacts will receive an email containing: Link to the release notes Your current upgrade decision (opt-in or opt-out) The upgrade timeline for this release All customers, regardless of their upgrade decision, can change their preferences at any time using the automated support tickets. Stage Upgrade Completion Email After your stage environment is successfully upgraded, your Upgrade Notification Contacts will receive an email confirming: Stage upgrade completion Your current upgrade decision (opt-in) The scheduled production upgrade date How and when you can opt-out if needed (anytime during the two-week testing window) Production Upgrade Completion Email After your production environment is successfully upgraded, your Upgrade Notification Contacts will receive a confirmation email. Example Timeline Here's a typical timeline for a standard release: Day 1: Release notes published here on ATLAS Community; Upgrade Notification Contacts receive email with release details, current upgrade decision, and timeline Days 1-6: Period to change automatic upgrade preference Day 7: Release preparation (not possible to change decision anymore) Day 8-9: Stage environments upgraded; Upgrade Notification Contacts receive email confirming stage completion, upgrade decision, and production upgrade date Days 10-22: Stage testing window (opt-out available anytime during this period) Day 23: Release preparation (not possible to change decision anymore) Day 24-25: Production upgrade for opted-in customers; Upgrade Notification Contacts receive confirmation email Patch Releases Patch releases address critical issues outside the regular release schedule. These include security vulnerabilities, bugs affecting multiple customers, or issues impacting release stability. Patches are automatically applied to all customers on the latest version and cannot be opted out of due to their critical nature. Our team will publish the release notes, notify customers, and apply patches in a three-day window. Upgrade Notification Contacts will receive email notification when patch release notes are published. Version numbering for patch releases will follow <standard release version number>.<number>, where number will be incremented for each patch and reset after a particular standard version. As an example, the first patch after 25.8 will be numbered 25.8.1, the second patch as 25.8.2 and so on. However, the first patch applied after 25.9 will be 25.9.1. We will use Change windows for non-downtime needs and maintenance windows timeslots for downtime needs. Patch releases will also be published as scheduled maintenances on our status page, where you can find real-time updates if anything changes. If a patch applies to customers on an older version, your account team will reach out to coordinate the upgrade. Tickets We provide two types of support tickets to help you manage your upgrades: Automated Support Tickets Opt-in ticket: For opted-out customers who want to opt back in for automatic upgrades Opt-out ticket: For customers who want to opt out of automatic upgrades Upgrade request ticket: To upgrade to the latest version immediately at any time For more information on managing your instance upgrade settings, see How to Manage Instance Upgrade Settings with the AI assistant. Regular Support Tickets Manage Upgrade Notification Contacts ticket: To add, remove, or change contacts who receive upgrade notifications [Khoros Classic can also use this guide] Use these to enquire about a release, report bugs, or any issues encountered during testing or in your environment: How to Make the Best Use of the Khoros AI Support Agent. You can go to our product-specific support portal here: Khoros Community Classic and Khoros Community Aurora. What to expect next Moving forward, based on feedback on the new release process, we will also be reviewing the cadence of releases, which is right now monthly. The intent is to provide high-quality releases, minimizing customer disruptions, and allowing customers time to provide feedback and adjust.Khoros Communities 25.9 - Release Notes
The Khoros Communities 25.9 release includes performance improvements, stability enhancements, and bug fixes across search, caching, authentication, and moderation features. Classic Fixed inbox search not returning results for partial word matches. Fixed an issue where the private notes page would error when performing an empty search. Fixed image URLs not being indexable by search engines due to incorrect robot headers. Fixed an issue where Salesforce user ranks were not updating after the initial sync. Fixed archive dashboard totals showing incorrect counts due to deleted boards being included. Fixed delete confirmation errors preventing content deletion. Fixed event pages showing errors after creating and publishing new events with optional livestream details. Aurora Fixed an issue where Salesforce user ranks were not updating after the initial sync. Fixed archive dashboard totals showing incorrect counts due to deleted boards being included. Fixed an error that occurred when viewing analytics for occasion reply messages. Fixed unread and view counts not updating without a page refresh. Fixed inbox search not returning results for partial word matches. Fixed an issue where the private notes page would error when performing an empty search. Fixed image URLs not being indexable by search engines due to incorrect robot headers. Fixed an authentication issue where cookies were not being properly echoed during login/logout flows. Fixed an issue where session cookies were being incorrectly cached for anonymous users. Improved page caching performance by moving from memory-based to filesystem-based storage. Fixed a page caching issue that was reusing parent frame IDs across different users. Fixed the 3-dot action menu not working properly in text key mode within Manage Content. Fixed the 3-dot action menu not appearing for reported private messages in Manage Abuse. Fixed message action menus not responding consistently across different content types. Fixed message preview pages reloading endlessly and preventing user actions. Fixed duplicate replies being created when responding to messages at deeper thread levels. Fixed pagination issues with archived messages where the cursor was not advancing properly. Fixed a null pointer exception occurring when deleting articles via API. Fixed an issue where followers were not consistently receiving edit notifications according to their preferences. Fixed subscribers receiving unnecessary emails for non-publish workflow actions. Fixed an infinite initialization loop occurring in SDK preview for custom components. Fixed an issue where component assets were not loading correctly when switching branches. Fixed database errors caused by custom field metadata keys exceeding the allowed size limit. Fixed an issue where pasted email addresses were being replaced with suggested users when pressing Enter in group/event invites. Fixed delete confirmation errors preventing content deletion. Fixed event pages showing errors after creating and publishing new events with optional livestream details. Staging and Pre-Prod rollout: September 15 Production rollout: September 29 The rollout will follow the standard maintenance windowsAurora: Managing group members
Community Administrators and Group Owners can manage memberships from a group’s Manage Members page. From this page, you can: View group members Assign or edit group member's role Invite new members to the group Remove members from a group Manage pending invitations Manage requests to join Note: Group Inviters and Curators cannot access the Manage Members page. Inviters and Curators invite members using the Invite Members option in the Options menu. View group members Group members (who are not a group owner) can see a list of group members on the main Group page in the Members widget. To view group members in Manage Members page: Sign in to the community and go to a group. Open the Options menu and select Manage Members. The Manage Members page opens with the Members tab by default. Group members are listed along with their membership role and the date that they joined the group. You can sort this list by newest or oldest members or search for a specific member by typing a name in the filter. Change a group member's role Administrators and Owners can change a group member’s role. From the Manage Members page, click the Options icon > Edit Role next to their name in the list, select the role(s) to grant for the member, and click Apply. Invite a member to a group From the Manage Members page, members with the Send group invitations permission can invite other community members to join the group. To invite a community member to join a group: Go to the Manage Members page for a group. Click Send Invitation. Search for the member by entering their username in the To field. Select the Role to grant the person and enter a welcome note (optional). Click Send Invite. Remove a member from a group From the Manage Members page, Administrators and Owners can remove a member from a group. To remove a member in the Community UI: Go to the Manage Members page for a group. Click the Options icon > Remove next to the member you want to remove from the group. Click Remove to confirm. Manage pending invitations To manage pending invitations: Go to the Manage Members page for a group. Click the Pending Invites tab. For each member in the list, you can Resend or Cancel the invitation request. Manage requests to join For Closed groups, community members can request to join the group. You can manage these requests from the Manage Members page for the group. To manage invitation requests: Go to the Manage Members page for a group. Click the Requests tab. Accept or Deny each request in the list.About Aurora Email Notifications
As a community member, you receive email notifications for different types of activity across the community. To manage your email notification preferences, see Manage Follow and Notification preferences for your account. Email notification triggers Email notifications may be sent in a variety of situations. Some may require action while others may be purely informational. Below are descriptions of the notifications you may receive. More email notification types will be available in future releases. Community member notifications Content Workflow notifications Admin-only notifications Community member notifications Notification Description New Accepted Solution A post is marked as a solution on a topic a community member is following Accepted Solution Reminder Reminder to check answers on content and to mark applicable posts as solutions Answer Accepted as Solution A post is marked as a solution on a topic a community member created New Follow (Digest) Daily or weekly digest that provides updates from the community member’s followed content New Follow (Immediate) Immediate notification that provides updates based on the community member’s email notification settings Group Email Invitation Member or non-member is invited via email to join a Group Group Join Request Group owner is notified that someone has requested to join their closed Group Group Membership Accepted Community member is notified that they have been accepted into a Group Group Membership Denied Person is notified of being rejected entry into a Group. Group owners can add an optional description explaining the reason the person was rejected. Group Private Message Invitation Community member is invited to join a Group. They receive a private message invitation to join and an email notification for the new private message. New Private Message Community member receives a new private message in their Inbox Private Message Sent Admin is notified when a broadcast private message is delivered Private Community Invitation Person is invited to join the community by email and receives instructions on how to register via email New Like Community member receives a like on their content New Content Mention Community member’s content is mentioned by another user Member Mention Community member is mentioned by username by another person Email Address Change Confirmation Community member attempts to change their email address (non-SSO authentication) Forgot Password Community member begins the Forgot Password flow Confirm Registration When registered, community member confirms their email address in this notification to complete the registration process (non-SSO authentication) Email Verification Required to Publish Content Community member attempts to publish content when their email address is not verified Email Address Verification Community member requests the verification email to be resent Rank Change Community member achieves a new rank Event Email Invitation Member or non-member has been invited to an event Event Private Message Invitation Member or non-member is invited to an event. They receive a private message invitation and an email notification for the new private message. New Badge Community member is granted a new badge Content Workflow notifications Notification Description Edited Saved Draft Someone edited a saved draft in a place you follow. Submitted for Review Someone submitted a draft for review in a place you follow. Submitted for Publication Someone submitted a draft for publication in a place you follow. Recalled Draft Someone recalled a draft for publication in a place you follow. Schedule for Publication Someone scheduled a draft for publication in a place you follow. Return to Author Someone returned a draft to its author in a place you follow. Return for Review Someone returned a draft for review in a place you follow. Admin-only notifications Notification Description Abuse Report Notification Admin or moderator receives a report of abusive content, private messages, or member profiles. Related topics: About NotificationsAurora: Recent Content widget configuration
The Recent Content widget displays the most recent items from blogs, knowledge bases, forums, ideas, and/or events within your community. It can be configured with different layouts, a specified number of items, and a variety of other elements. Layouts The layouts included for the Recent Content widget are Detailed list, List, and Card. From the Edit Widget panel, select any of these options to change the layout. Each layout has its own set of unique options available. Detailed list The Detailed list layout features a smaller thumbnail accompanied by the item's title, various elements, and a preview of its content. List Card Configuration Options List style The available List style options for Detailed list and List include: Space: Uses whitespace to create space between items. Divide: Adds a horizontal line to divide items. Border: Creates a border that separates items into individual boxes. Title The Title sets the title that appears at the top of the widget. If the Visible only to screen readers toggle is enabled, the title remains hidden to most visitors; however, the title information is still relayed to visitors using screen readers. Scope The Scope field enables you to select where the widget is scoped. You can scope to the community, a category, a group, or a specific board. If you select a specific board, the Content types to include drop-down menu becomes inactive. Content Types to Include Use the Content Types to Include drop-down menu to select the type(s) of content types to display in the widget. Options include: All (All content types) Blogs only Knowledge Bases only Discussions only Ideas only Sort You can set the default Sort By filter to one of the following options: Newest topics Most recent (applies only to top-level posts and replies, not nested replies) Detailed list Options The available sort options for the Detailed list layout depend on the state of the Show additional filter/sort tabs toggle. If deactivated, you can set the default Sort By filter to one of the options listed in the previous section. Below Sort and filter options, you can also turn on Show filter and sort controls to add a Tagged line where members can click + Tag to enter a tag to filter content by that tag. If, however, the Show additional filter/sort tabs toggle is active, you can configure the different sort options available to visitors through tabs that appear on the top of the widget. These include: Sort by Most Viewed Sort by Most Liked Sort by Most Replies Filter by Newest Topics Filter by Most Recent Filter by Items with No Replies Yet Number of Items The Number of items slider gives you control over the number of items displayed on the initial page load before a Show More option appears. List item/Card elements Elements are additional pieces of information that can be displayed along with each item in the widget. The list of available elements changes depending on which layout you've selected. Detailed list and List layouts have an additional Lead with drop-down menu. It enables you to choose to display the item author's Avatar, discussion style Icon, or None along with the item in the widget. More options Additional options are available at the bottom of the Edit Widget panel. Hide if empty hides any tabs that don't have corresponding items. Include "Show More" link adds a link to the bottom of the widget to enable visitors to display additional items once the Number of items has been reached.Khoros Communities 25.8 - Release Notes
The Khoros Communities 25.8 release includes several important security improvements and bug fixes. [Classic] Fixed a cross-site scripting (XSS) vulnerability affecting embedded YouTube videos on community pages. [Aurora] Certain specific custom access permissions was blocking user registration, due to attempting to verify permissions before the user was registered. This has been addressed so that permissions are checked in the correct sequence. [Aurora] Fixed an issue where users were unable to join Zoom meetings when registration was set to "required"; users would instead see an error message. [Aurora] Fixed an issue with headers and footers appearing multiple times on some community pages. [Aurora] Addressed an Aurora GraphQL API issue where certain custom fields were omitted from responses. These values now appear correctly. [Aurora] Resolved an issue where the "CurrentUser" endpoint returned information about the anonymous user, not the actual current user, when using the Authorization header method of authentication. Release Date: August 20, 2025
