Khoros Communities 25.08 - Release Notes
The Khoros Communities 25.08 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
Khoros Communities - Updated Release Process
To improve your experience and simplify our release process, we are updating how we handle Khoros Communities releases. This process will start to apply from Communities Release 25.09. What's Changing Communities will have two types of releases going ahead - Standard releases and Patch releases Standard releases are regular releases that will happen on a cadence during Maintenance Windows. All releases will be standard releases Patch releases are critical bug fixes or security fixes, which happen out-of-band During Standard releases, our teams will automatically upgrade customers on the latest release providing windows for feedback Customers can reach out to support for upgrading legacy instances or for any other feedback Standard Releases We will have a standardized release process for both Aurora and Classic. In a standard release, we will auto-upgrade customers on the latest release. These releases will include features and non-critical bugs. 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. 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 , customers will be notified and have a week to provide feedback to their Customer Representatives on the upcoming release. After this one week, we will upgrade the stage environments. We will open a two-week testing window, where customers can test on their stage environments and provide feedback. Again, Customer Representatives will be the points of contact during this phase. At the end of the two-week window, we will perform the upgrade in production for customers whose stage environments we have successfully upgraded and do not have any open feedback. For both stage and production, we will use existing Maintenance windows, as we expect downtime. If you are on an older version and want to opt back into auto-upgrades, please reach out to your Customer Representative. They can upgrade you to the latest version at any time Patch Releases We will release patches out-of-band for critical bugs that affect multiple customers or affect a release's stability, and security and vulnerability fixes. We will apply patch releases for all customers on the latest version, given that these are critical in nature. Our team will publish the release notes, notify customers and apply patches in a three-day window. Customer Representatives will handle any customer feedback during this phase. 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. Customer support will notify customers about downtime needs. Customer representatives will reach out if a patch applies to a Customer on an older version. As always, Customer Representatives are available for any feedback. What to expect next As we stabilize and 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.Google+ 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.
Aurora Product Coaching Session: Approaching Analytics in Aurora
Join our Classic to Aurora Analytics migratory coaching session to unlock the full potential of your community data. This session will guide you through practical applications of Aurora Analytics, from high-level overviews to detailed report analysis. Our coaching session will provide you with the knowledge and skills to effectively leverage Aurora Analytics for informed decision-making and community growth. Topics covered in the coaching session A detailed walkthrough of Aurora Analytics, based on real-world insights. A comparison of Aurora Analytics versus Classic Analytics, highlighting key changes and new features. Practical use cases demonstrating how to apply Aurora Analytics to your day-to-day work. Notes - Admin or analyst-level access to Aurora Analytics is recommended to conduct the call. 👉Click here to Sign Up Resources:- About Aurora Analytics Filter the Analytics Dashboard Aurora Analytics Dashboard Use Cases Khoros Academy Learning Path: Communities (Aurora) Analyst Level 1 Khoros Academy Learning Path: Communities (Aurora) Analyst Level 2
