This release brings a few enhancements on scheduling articles for publication and obtaining published URL when the articles are in draft state, and sending invites to community and non-community members via emails. We also have API updates around the same.
With this release, you’re going to start seeing a new type of interactive documentation in our Release Notes and some knowledge base articles. To learn how to use and get the most out of this content, check out this quick 2-minute video attached with this blog.
Content
- Include time zone while scheduling knowledge base and blog articles for publication
- Send events invitations by email
- Preview published URL
- Include time zone while scheduling knowledge base and blog articles for publication
- Invite by email Events
Enhancements
Include time zone while scheduling knowledge base and blog articles for publication
With this release, you can now set the time zone to use when scheduling Blog and KB articles for publication. Admins and members with authoring roles (author, editor, publisher) can see when and where a draft will be published.
Note: To use this feature, you must be on feature versionsTKB v4.1 and Blogs v3.1. Go to Studio > Features and select 4.1 for TKB version and 3.1 for Blog version.
Here's an interactive tutorial
Send events invitations by email
Until now, you could send invitations to community members for events only via Private Messages. With this release, we’ve introduced the Invite by email feature for Events.
You can now send invitations for events 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 for events via email.
Note: To use this feature, Events must be on version 1.2. Go to Studio > Features and select 1.2 for Events version.
Enablement
To enable this feature, go to Admin> System > Invitations and select Email.
About the feature
- Send invitations for public events: When you send invitations for public events using the Email option , you now see this pop-up window:
- 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
- Members who have RSVP'd to the event do not receive an invitation.
In both these cases, the invites are sent to the email addresses only.
- Send invitations for events in a private events: When you send invitations for events in a private Events board or a closed/hidden Group Hub using the Email option , you now see this pop-up window:
- In the Enter usernames field, add the username of members who belong to the private Events board or a closed/hidden Group Hub. The invites are sent to the email addresses only.
- Invitations for events in a private Events board or a closed/hidden Group Hub are sent only to members who have access to the board or are members of the Group Hub.
- Members who have RSVP'd to the event do not receive an invitation.
Learn more on sending invites to non-community and community members via email
Preview published URL
Prior to this release, Blog and TKB authors could not know what the published URL for an article would be until they published it.
With this release, authors can preview the published URL (the final URL when published) on the workflow page of the draft. You can share this URL with others, who might need to link to this article when it’s published.
This example shows the preview of the URL when the article gets published.
With this URL, you can proactively reference the article from anywhere in the community, but the link won’t work until the article is published.
Note: To use this feature, you must be on feature versions TKB v4.1 and Blogs v3.1. Go to Studio > Features and select 4.1 for TKB version and 3.1 for Blog version.
Announcement
Deprecation of Transport Layer Security (TLS) 1.1
To improve our security and keep up with the latest security standards, Khoros will no longer allow TLS1.1 traffic to its communities. Moving to TLS1.2 (or higher) keeps communities secure and only allows the latest security protocols to be used while encrypting traffic between the end user and the community.
End users will not notice any change to their experience. As long as no outdated connection protocols are being used, the transition is seamless.
These changes are being rolled out during our regular maintenance windows and will take effect immediately.
API Updates
Include time zone while scheduling knowledge base and blog articles for publication
We have updated the following TKB and Blog APIs:
- Create Message API to include the scheduled time zone
- Get Message API to display the schedule time zone details.
Invite by email for Events
We have updated the Events Invite API to include the invitees email addresses. When the Send invitations via permission is set to Email, you can send invitations via email.
Here's an interactive tutorial
You found it! We fixed it!
Here's an interactive tutorial
- We have fixed the issue where members who did not have the ‘Create Event’ permission could not RSVP to events using API calls. With this release, members without this permission can RSVP for themselves using API calls. However, if they want to RSVP for another member, they must have this permission.
- We have fixed the issue where clicking the Knowledge Base Admin menu option from a forum topic page threw an error.
- The Community Page header icons were appearing in reverse order (User Profile, Private Messages, Notifications). We have fixed this display issue and now the icons display in the correct order (Notifications, Private Messages, User Profile).
- We have fixed the issue where selecting the checkbox for an emoji and then clicking on the Save option threw an error. With this release, when you choose emojis and save the changes, members can use them at the category level.
- We have fixed the issue where navigating to a tag page threw an exception error due to the page taking a longer than acceptable time to load.
- When members received an “Invalid HTML was found in the message body” error when submitting posts, they could not re-submit the post since they were blocked by flood controls. With this release, after the HTML errors are removed, members can re-submit posts successfully.
- There was an issue with archiving threaded posts. An error message displayed that the thread was archived but the thread still showed up in the community and was not archived . This issue is now fixed, and the thread successfully archives.
- Previously, when non-admin members clicked the link for an archived post that included a redirect URL, they were not directed to the alternate URL. This issue is now fixed.
- We have fixed the issue where archived posts were displayed in the kudos received and given for the posts components. Archived posts are no longer listed under these components.
- After communities upgraded to 21.8, there was an issue when attempting to access Community Analytics resulting in an error. This issue is now rectified.
- Earlier, if a forum thread with post kudos was archived before the post's author opened the kudo notification, an error message displayed the next time the author opened the notification feed. This issue is now fixed. The notification feed page loads as expected, and users can view the Kudo feed notification even if the post is archived.
- Earlier, a page break unexpected error was thrown while loading a board that was moved from one category to another, and the original category was deleted or had the ‘see categories’ permission set to deny. This was because the permissions and subscriptions related to the category were mismanaged. This issue is now fixed. The board/discussion style page loads as expected, respecting the permissions and subscriptions assigned to the user.
Accessibility fixes
- There was an issue where the HTML image element for product mentions did not display an Alt image tag. This issue is now fixed.
- When the “Show Options” menu is open and users click the Escape key, the focus was not retained on the “Show Options” menu. This issue is now fixed.
- The screen reader read the toggle button for the list and calendar views on the Events page incorrectly. We have fixed this issue. The button now reads "List view of events" and "Calendar view of events", respectively.
- We have fixed the issue when pressing the Escape key on the invites dialog box that the focus moves to the top of the page and does not remain on the “Invite” button.
- We have fixed the issue with the JAWS screen reader reading out the “Star Message Subject” field instead of the “Message Subject” field when the focus is on the “Message Subject” field.
- When a community's TopLevelCategories is set to false and the language for the Value Analytics survey is set to a language other than English, the survey messages displayed in English. With this release, the survey messages display the language that the survey is set to under Community Admin > System > Value Analytics > Localization.
- We have removed the duplicate ID that was present in the Search results page Location drop-down menu.
- While replying to a message, the menu did not activate when the user focused on the “Show Options” menu inside the “Replying to:” section. This issue is now fixed.
- As the ‘Message List Component’ table is not defined in the source code, the screen readers did not readout the information for this control. This issue is now fixed.
