Khoros Communities: Classic 24.12 Release Notes

Bypass Event Invitation Flood Control Limits

We’ve introduced a new permission, Bypass Event Invitation Flood Control, that allows admins to send more invitations than the flood control limit set for the community.

This permission is available under Admin > Users > Permissions > Events.

You Found It. We Fixed It.

Content Workflow and approval

Members with the TKBAuthor role no longer receive email notifications for submitting an article for review or for editing and saving a draft. Notifications are sent only to relevant users, excluding the author performing the actions.

When a draft is published by a TKBPublisher, members with the TKBAuthor role now receives a single email notification indicating that the publisher has posted the article. The email includes additional context stating that the article was originally created by the author, eliminating redundancy and ambiguity.

Content Archival

Archived posts instantly reflected in the Archives page.

3 Comments

Alex-VFZ
Expert
2 days ago
We're currently on Classic 24.10 and are experiencing the issue where sorting threads on 'most recent'/new isn't correct anymore (also mentioned here). I learnt Khoros presumably fixed this in the newest Classic Communities update. I couldn't find it anywhere in the release notes, although I did find a mention of this bug(+fix) in the Aurora Release Notes.
Can anyone on this version confirm this bug has been solved? It would help(/comfort) a lot, thanks in advance!
caroleighdeneen
Ace
11 days ago
Hi Lief , on our community, workflow notifications are tied to the default TKB role names (we're using v4). When we tried setting up three parallel roles with the same permissions, but a different name, notifications were not sent. We got around it by:
Setting all the permissions for TKB Author / Editor / Publisher to the default community permissions.
Set the desired TKB-related permissions on the custom role we created, for example like your TKBAuthor_<nodename1>.
Assigned both the custom role and default TKB role to relevant users.
The custom roles granted the permissions desired, the default roles triggered the emails according to the TKB workflow.
If there's another way, would love to hear about it!
Lief
Executive
11 days ago
In my community we extended TKBAuthor to apply special permissions for specific nodes.
TKBAuthor_<nodename1>, TKBAuthor_<nodename2>
We don't give the OOB TKBAuthor role. Will this new email notification apply in those cases as well?
If so, can you confirm how it works?
If not, how do we make it so?

Blog Post