Content

Enhancements

• Send Group Hub invitations by email
• Use external URL while archiving content

API Updates

• External URL while archiving content
• Invite by Email for Group Hubs
• Contributor Type accessible through LiQL
• LiQL Updates

Bug Fixes

• General Fixes
• Accessibility Fixes

Enhancements

Send Group Hub invitations by email

Until now, you could send invitations to community members to join Group Hubs only via Private Messages. 

With this release, we’ve introduced the Invite by Email feature for Group Hubs. 

You can now send invitations for Group Hubs to non-community and community members via email. This also eliminates the limitation with communities that do not have the Private Messenger feature; such communities can send invitations via email. You also can track the invitations sent from the Member Management board.

Enablement

Contact the Support team to enable this feature.

After the Support team enables the feature, go to Admin> System > Invitations and choose Email for Select Invitation via option.

Send invitations

When you send invitations for Group Hubs using the Email option, this window now opens:

 

• In the Enter usernames field, add the username of community members.
• In the Enter email addresses field, add email addresses of non-community and/or community members.
• In both the above cases, the invitations are sent to the email addresses only.
• Members who have already joined the Group Hub do not receive an invitation.
• You can send a maximum of 10,000 invitations at a time.
• You can copy/paste a list with a maximum of 10,000 email addresses.
• If you copy/paste a list of email addresses, all the invalid email addresses are ignored and the invitation is sent to the remaining valid email addresses. 

Track Email Invitations for open, closed, or hidden Group Hubs

On the Member Management page, click the PENDING EMAIL INVITES tab. This lists the pending email invitations sent to community and non-community members.

 

Learn more about inviting users to join Group Hubs via Private messengers and email

Use external URL while archiving content

Earlier, while archiving community content, you could redirect users only to pages within your community. With this release, while archiving content, you can add an external URL to redirect users. To use this feature, your community must

• Be on version 22.4 or later
• Have the Turn on content archive option turned on
• Have the Allow external alternate URLs option turned on

 

While archiving content on communities that have this feature enabled and required settings turned on, you will now see the following popup:

Learn more on archiving community content

API Updates

External URL while archiving content

We have updated the Archive Messages and Edit a Suggested URL endpoints to support the external URL when the Allow external alternate URLs and Turn on content archive permissions are selected in Admin > MOD TOOLS > Content Archive.

Invite by Email for Group Hubs

We have updated the POST/Invite user to join node endpoint to create email invitations for both the community and non-community members to join the Group Hubs. 

Note: You must set the Send Invitation via permission to Email in Admin > System > Invitations.

Contributor Type accessible through LiQL

The current API to retrieve the contributors for TKBs and blogs returns both the co-authors and contributors together. With this release, we introduce a new constraint to list the co-authors and contributors of the published and unpublished blogs and TKBs separately.

This new constraint, called contributor_type, is added to the messages object with two acceptable values:

• co-author
• contributor

Note: The contributor_type constraint must be used in conjunction with the contributor.id constraint in the LiQL query.

Learn more about contributor_type.

LiQL Updates

• As first mentioned in the 22.3 Release Notes, we have updated the messages collection to honor the Hide messages in this board from the List option for a particular board. If you have enabled this option for a particular board, the messages will not appear in the response of a LiQL query. See messages collection.
  Note: This change could impact any customizations created in partnership with our services team that leverage hidden fields, so you should review these areas.
• We have removed the mandatory board.id constraint from the contributor.id constraint in the messages collection.
• We have added the new invite_type and external_user_email constraint in the invites collection to retrieve all the grouphubs invitations of the community and non-community members.

You found it! We fixed it!

General Fixes

• The issue where blog editors on communities with Blog v3 and v3.1 were unable to edit Post published articles in Awaiting review status is fixed. 
  
  
• The issue where you could not successfully submit inline replies to posts on communities that use Products v1 and Forums v5 is fixed.
  
  
• Earlier, when regular users with permissions to comment submitted a comment on a topic, an error displayed indicating that they do not have sufficient privileges to perform this action. This issue is fixed.
  
  
• Earlier, in communities on 21.12, when you ran the query for occasion_data.live_stream_url, an error returned that indicated the object doesn't exist. This issue is fixed. 
  
  
• The issue where some past events were not displayed in the calendar view is fixed. 
  
  
• Earlier, when you tried to access the spam quarantine on communities v22.2 or later with enable.Products set to false, you received an error. This issue is fixed. Now, the spam quarantine page loads successfully, and you can review posts marked as spam.
  
  
• Earlier, on communities v21.7 and above, the board options menu intermittently toggled between Subscribe and Unsubscribe, even though you already subscribed to the board. This issue is fixed. Now, after you subscribe to a board, you receive notifications, and the board options menu displays Unsubscribe and vice-versa.
  
  
• Earlier, users with any of the required roles (MODERATOR,LithiumInternalApiUse, or KHOROS) granted to them by cloning the roles, and with the "Manage roles" permission set ALLOW GRANT, were unable to grant these roles to other users. This issue is fixed. Now, when you have any of these roles assigned to you, you will be able to grant other users these roles, provided you have the "Manage roles" permission set ALLOW GRANT.
  
  
• Earlier, you were not successfully signed out if you had enabled the Keep me signed in option and tried to sign out of the community using the /signout API. This issue is fixed. 

• Earlier, when you subscribed to a label, the label was listed under User Profile > My Subscriptions. But after some time, when you visited this page, the label subscription was not listed. This issue is fixed. Now, under User Profile > My Subscriptions, you can see the labels that you subscribe to.
  
  
• The issue that returned an error when you tried to fetch the body of the post using LiQL in the API browser is fixed. Now, LiQL returns the body of the post.
  
  
• Earlier, the API to fetch user settings did not return correct value in the response since the cache had outdated the user object. This issue is fixed by populating the cache with updated user objects.

Accessibility Fixes

• Earlier, the screen reader did not read the label name of the email address link on the user's profile page. This issue is fixed. Now, the screen reader announces the name of the label followed by its link as "Email null link."

• The issue that keyboard focus is lost after giving kudo to a post, is now fixed. 
  
  
• The issue where Jaws does not announce the action you can perform on the kudos button, is now fixed.