You found it! We fixed it!
General bug fixes
- The Viewed in store metrics records the number of times a product is viewed on the brand domain from the product page or from a product mention. There was an issue that led to this metric not getting incremented in Community Analytics. Now, when you click the View in Store button within the community, this metric will increment. This metric is also available for past date ranges.
- Previously, forum topic pages with inline replies took more than 2 seconds to load, which impacted SEO. This issue is fixed as editor options files are now compressed and are lazy loaded after page load.
- Previously, when you gave multiple kudos in quick succession to a message through REST API v1, multiple email notifications were sent to the author’s email address. This issue is fixed. Now, when multiple kudos are given to a message, only one email notification is sent to the author.
- The issue in Community Release 22.12 where the Quarantine Posts older than 30 days appeared on the Spam Quarantine page is fixed. The fix has been backported to all communities still on the 22.12 Release.
- Previously, some French, Italian, and Catalan language communities encountered issues when archiving posts. This issue was due to incorrect parsing of text keys related to archiving and has been fixed.
- The issue where exception errors resulted in 301 permanent redirect responses when members tried to refresh or navigate away from the page has been fixed.
- Previously, in any board with pre-mod enabled, when a member replied to a post and moderators approved it, members who subscribed to the post did not receive any notification about the newly added reply. This issue is fixed. Now, members receive notifications for all the updates to the posts they are subscribed to.
- Previously, members with appropriate permissions could not upload images to posts via desktop, but they could upload via mobile devices. This issue is fixed. Now, members with appropriate permissions can upload images to posts via both desktop and mobile devices.
- Previously, content filters did not flag non-breaking spaces ( ) and HTML span tags (<span>) added in the posts through the browser's developer console as spam, and members were able to post the content in the community. This prevented some messages from being identified as spam. This issue is fixed. Now, content filters flag non-breaking spaces and HTML span tags added in the posts through the browser's developer console.
- Previously, when you executed a LiQL query to retrieve an archived public forum discussion, blog post, or Knowledge Base article, a 301 error was returned. This issue is now fixed.
Accessibility fixes
The issue where the screen reader did not announce the state as “disabled” for the disabled items in the Options menu on the Gallery page is fixed.
Updated 5 months ago
Version 2.0BhuvanaM
Khoros Alumni (Retired)
Joined April 29, 2022
Release Notes
Review release notes and updates for all of our products! Select a label to browse by product or resource type.