Blog Post

Release Notes
6 MIN READ

Khoros Communities 22.8 Release

AshaC's avatar
AshaC
Khoros Staff
3 years ago

Content

Enhancements

API

Bug Fixes

 

Enhancements

Support for additional content types for Content archive

Previously, you could individually or bulk archive only KB articles, blog posts, and forum discussions. With this release, you can now archive Events, Ideas, and Q&A discussions. You can also unarchive (one-at-a-time) any archived ideas, events, and Q&A posts from the Archives page.

The screenshot below displays the Bulk Archive page, now with the ability to archive all the above-mentioned discussion styles:

You can also archive Ideas, Events, and Q&A posts from the post level menu options. 

Learn more about content archival and bulk content archival.

Salesforce Connector v4.3 (General Availability)

In community version 22.6, we released early access to SFDC v4.3. With this release, we are happy to announce the General Availability of this feature. 
Learn more on Connector for Salesforce package versions and upgrades
Learn more about the issue fixes and enhancements on all Salesforce Connector Versions

E-mail notification status information in the Bulk Download Member Data

With this release we have introduced a new field - Email Notifications Allowed to the Bulk Download Member Data Report.

For members who have opted not to receive email notifications, this field shows “No”. Otherwise, it shows “Yes”. 

To set whether or not to receive email notifications, click your profile image and go to My Subscriptions > SUBSCRIPTION & NOTIFICATIONS > Notification Settings

The screenshot below shows that the member has opted to receive email notifications. For this member, the Email Notifications Allowed column in the Bulk Download Member Data Report displays “Yes”. 


Bulk Download Member Data Report for the above example:

Learn more about Bulk Download Member Data Report

Enable Moderators to access Closed and Hidden Group Hubs in Community

With this release, Moderators (who have permissions such as Mark posts as moderated, Bypass content filters, Bypass automatic spam rejection, and Approve, recall, or reject topics and posts) can access closed and hidden group hubs. When granted these permissions, moderators can moderate content within those group hubs without being a group hub member. 
This is controlled by a config, which is enabled by default (to disable it, contact Support).

Note: To enable Moderators to access and moderate Group Hub content (Closed or Hidden) without being Group Hub members, you must explicitly grant (not granted by default) the “See discussion style boards ” and “See Group Hubs” permissions to Moderators. 

Learn more about Group Hub roles and permissions

URLs to the Group Hubs .csv File Export

Earlier, links to the community’s Group Hubs page from the Group Hub reports’ .csv files were not provided. With this release, we have included links to the community's Group Hubs in the downloaded .csv files.

To download the Group Hubs report, go to Content > Group Hubs and click the Group Hubs tab. Then, open the gear menu and click Export (CSV).

The screenshot below shows the downloaded file with the URL to redirect you to that Group Hub in your community.

 

API Updates

Fetch users subscribed to a label

Previously, querying a label subscription provided the results of the label subscription specific to the logged-in user. With this release, we have updated the subscription collection to fetch all the community users subscribed to  a particular label. 

Learn more about target.type and target.id constraint.

Support additional content type for content archival

Previously, you could archive the content only for blogs, forums, and KBs. With this release, we have extended the content archival and bulk content archival APIs to support the archival of Ideas, Events, and Q&A.

 

You found it! We fixed it!

General Fixes

  • There was an issue where the contents of notification emails were displayed in a table even though the Remove HTML from mail option under My profile > Subscriptions & Notifications > Email Format was enabled. This is now fixed

  • Previously, when members with permission to bypass the read-only setting on the community submitted a post with a label, notifications were sent to the subscribers of the label. This post was lost during a migration process and was uploaded with an image instead of a message. When users clicked on the notification feed, the page errored out since the post was missing. This eventually led to page errors in the community. This issue is now fixed.

    Now the notification page loads successfully and any corrupt data for that notification is not displayed.

  • The issue where the daily digest emails are intermittently not sent from the community is now fixed.
     
  • The issue where KB authors were not auto-subscribed to their own articles is now fixed. 

  • Previously, when topics were merged from one forum board to another,  the notification email and notification feed text for merge messages were incorrect. This issue is now fixed. 

  • Previously, when admins ran catalog sync by enabling product catalog sync, product catalog sync failed on manual sync. This issue is fixed. Now, product catalog sync runs successfully on manual sync. Users must have the administrator role to run the auto and manual sync from community versions 22.6 and 22.8 onwards respectively. The relevant integrate your product catalog guide is updated with the fixed issue information.

  • Previously, when members replied to a thread for any topic and tried to preview the message they had entered in the message editor, the message editor preview failed to load and an error message was displayed indicating that the requested action was unable to complete. This issue is fixed. Now, members can preview the message they have entered in the message editor.

  • Previously, when members mentioned any registered users with their usernames using the “@” symbol while replying to a post via smartphone and if there was any space in the username that they mentioned, the system failed to list the appropriate username in the dropdown. This issue is fixed. Now, the system lists the appropriate usernames based on the specified mentions.

  • Previously, when members tried to attach an ICB file (.icb) to a draft post in the community, the file failed to upload and an error message was displayed indicating that the .icb content type does not match its file extension and the file has been removed. This issue is fixed. Now, members can successfully attach ICB files while creating a new post or replying to a post in the community.

  • Previously, when members tried to attach a .pbit file to a draft post in the community, the file failed to upload due to MIME type errors. This issue is fixed. Now, members can successfully attach .pbit files while creating a new post or replying to a post in the community.

  • Previously, signed-in users were able to retrieve the draft history of blogs or KBs of any authors via API even if they did not have any specific permissions. This issue is fixed. Now, users cannot view the draft history of other authors without appropriate permissions.

  • Previously , the ‘See discussion style boards’ permission was not exposed in the UI for Hidden Group Hub roles . This prevented a cloned role of hidden group hub from managing Group Hub membership.
    This issue is fixed. Now, the permission is visible for Group Hub roles (OOTB and cloned group hub roles) of hidden group hubs and admins can grant this permission. The Hidden Group Hubs continue to be not available for non-group hub members as the permission is not available at Group Hub node level defaults.

Accessibility Fixes

  • The issue where the screen reader did not announce the list item count for the “Options” menu on the Gallery page is fixed.

  • The accessibility issue where duplicate-id errors were thrown while running the Accessibility Insights Tool on the forum page is fixed.

  • Previously, when you selected tab items under the ‘Ideas’ pane on the community page, the screen reader focus moved to the top of the page. Members who use screen readers had difficulty interacting with the tab items. This issue is fixed. Now, the screen reader focus remains on the selected tab items on the community page. To implement this fix, your community must be on v22.8 or above, and Ideas v3.1

 

Updated 5 months ago
Version 4.0
  • SudheeshN  -- very happy to see the Email status in the bulk download member data. Thank you!! 

    Would also be a great enhancement to get added to the bulk data API. 

  • KrisS's avatar
    KrisS
    Khoros Alumni (Retired)

    allensmith81 the new behavior introduced in 22.8 is controlled by a config that will be enabled by default as of 22.8 and forward. For customers who do not want that behavior, they can either request Support disable the feature by config, or simply not make the necessary permission changes. Similar to many features it's made available out the gate so customers can opt to use it not, but there is an option through Support for those who do not wish for this behavior to even be an option.

  • We got this release last night and now we have 25 new notifications in our notifications feed. They cant be removed.

  • KrisS's avatar
    KrisS
    Khoros Alumni (Retired)

    Drew_C thanks for the info - you are spot on. irach15 this is likely the result of your email system either having new features pushed out or turned on that scan emails in real-time and click on links.

    In this case I can confirm this is indeed what's occurring based on the URI from the logs showing the reply by email is what generated the solution:

    uri=/t5/action/replybyemailactionpage

    Basically, once an email comes in it's being scanned and has links clicked, which in turn trigger the solutions or kudos. Disabling the email mechanism would be the true solution, but on the Khoros side it can be worked around by disabling reply by email for users like Drew mentioned.

  • Can someone clarify this:


    AshaC wrote:

     

    Enable Moderators to access Closed and Hidden Group Hubs in Community

    With this release, Moderators (who have permissions such as Mark posts as moderated, Bypass content filters, Bypass automatic spam rejection, and Approve, recall, or reject topics and posts) can access closed and hidden group hubs. When granted these permissions, moderators can moderate content within those group hubs without being a group hub member. 
    This is controlled by a config, which is enabled by default (to disable it, contact Support).

    Note: To enable Moderators to access and moderate Group Hub content (Closed or Hidden) without being Group Hub members, you must explicitly grant (not granted by default) the “See discussion style boards ” and “See Group Hubs” permissions to Moderators. 

     


     

     

    To me the first part is saying you need to have this turned off by support while the bit in the note is saying you only have to change the permission... am I not understanding something here?

  • JoseL's avatar
    JoseL
    Khoros Alumni (Retired)

    Hi TeroRe,

    That is a previously reported issue currently under investigation by our Engineering team.

     

    Please file a Support case so we can investigate further and provide updates on the permanent solution's progress if this issue is related.

     

    All the best,

  • we got the issues when the users replied to a post and  right away it has been  accepted as a solution.

    If they have no permissions to un-accept, our moderators have to track and do it.

    Support case already created last Friday.

  • irach15

    Some time back, I noticed an account seemed to be giving Kudos on replies nearly immediately. That’s great, except the account had been inactive for months, so I opened a support ticket to figure out why.

    Turns out, we believe the user's email was being scanned before delivery and the malicious link detection is "clicking" the Kudo button in the email.

    If you know which user it is, switching to the user's account and disabling the "reply by email" option should stop the behavior. I'm willing to bet there's something similar in your emails for "accept as solution."

  • KrisS 

    interestingly, it was our superuser and me, and I'm the Admin 🙂

    and it happened right after the upgrade and nothing changed at our side.

  • KrisS's avatar
    KrisS
    Khoros Alumni (Retired)

    irach15 the timing is definitely suspect and the first thing we look at is what changed on or around the date the issue was first reported. However, having encountered this before we knew where to check in the logs to quickly see the URI for the solution came from the reply by email path used in the email link.

    This is tied to the end user who gave the solutions and does not impact your account. Your post was marked as a solution because when you contributed to the thread it generated a subscription email for a new reply for the user we believe is using some type of security scanner on emails that's actually clicking the links generating solutions.