Blog Post

Release Notes
1 MIN READ

Khoros Communities 24.2 Release

AshaC's avatar
AshaC
Khoros Staff
9 months ago

 

You Found it! We Fixed it!

General fix

Accessibility fix

 

You Found it! We Fixed it!

General fix

  • It was found that after a Group Hub was moved to another category, the API to return the number of Group Hubs in a category did not return the correct result. This issue is now fixed. 

  • Previously, an exception was thrown when you tried to add custom cookies on communities version 23.10 and later. This issue is now fixed. Now you can successfully add custom cookies

Accessibility fix

  • It was found that screen readers read the Send message button under the FRIENDS and IGNORED tabs in Private messenger (Private messenger > > Manage Friends & Ignored) incorrectly. This issue is fixed. The screen readers now read the button as “Send message.”

 

 

  • The issue where screen readers did not announce the state for the selected controls, such as the From and To fields, in the Private Messages page is fixed.
  • The issue where a tooltip was not defined for the Compose notes icon control in the Private messages page is fixed.
  • The issue where an API call to return the Group Hubs that were moved from a category returned an incorrect result set is fixed. 
Updated 5 months ago
Version 2.0
  • Update: We rolled back but the LIQL issue persists and whats odd is i can add, and edit new items to the EN category, and have them appear in LIQL, but the other items, that have existed since we went live years ago no longer appear, specific to our EN category only? 

    CarolineS , if you roll back, does LIQL still show a issue? 

    The Q I'm trying to solve now, is there any setting that can prevent something from appearing in LIQL? As far as I know nothing like that exists? LIQL should return everything based on access of the person requesting and im using admin?

  • phoneboy, had a similar issue that we reported to Support. They provided us with an additional LiQL WHERE clause condition: 

    AND products.association_type='tag'

    Adding that to our products.id queries fixed them.

  • Yet another example of the inconsistent experience I receive when I need to engage Khoros TAC...I was never offered this workaround!

    I ultimately decided to move away from using Products for the purpose I was using them for.
    Seems like this functionality was never fully developed and, given the eventual migration to Aurora, it doesn't seem prudent to waste further time attempting to use it.

  • phoneboy, definitely inconsistent. Sounds like you had a higher level of time sensitivity around a resolution than I did. I imagine that they simply knew more by the time they replied to me.