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 windowsKhoros Communities 25.10 - Release Notes
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 20-21 Production Rollout: November 5-6 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 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.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, 2025Google+ vs. Facebook vs. ... Part 1: The Strength of Bidirectional Connections
Since its launch in late June, Google+ has been a hot topic of conversation. So before I proceed with either the engagement or the gamification series, I think it is appropriate to take a short detour to discuss Google+. I think by now everyone has most likely had the chance to play with Google+ (or at least know what it is). If you still don’t know, don’t miss the boat. There are already 25+ million people signed up. I am not going to repeat Google’s pitch, so take a look at the demo from Google. What I’m going to talk about today, are some of the network properties and social principles behind some popular social platforms. Of course, I will compare and contrast them to the new kids on the block (i.e. Google+), and talk about their behavioral implications.Khoros Communities: Classic 25.04 Release Notes
You Found It. We Fixed It. A fix was backported to address a security vulnerability that previously allowed users to add dest_url as a URL parameter in their posts to redirect those who clicked the URL to any website. If you have any questions, contact Khoros Support. For posts with emojis, the emojis are now retained as expected even after the post is edited and published again.
