- Enhancements
- WebP (.webp) image filetype for Community posts and replies
- Announcement
- You Found it! We Fixed it!
Enhancements
WebP (.webp) image filetype for Community posts and replies
With this release, WebP (.webp) has been added as a valid image file format in the community and members can now upload WebP files to their posts and replies. To make sure your community supports .webp images, please add the .webp as a valid file extension from the Settings area (Settings > Features > Images).
Announcement
With the announcement from Oracle that AddThis will be decommissioned on May 31st, 2023, we have ended our support of the AddThis share button on Community Classic. There are no plans to replace the current functionality in Classic or Aurora at this time; given the fast deprecation of AddThis from Oracle, our current roadmap priorities and lower usage of the feature.
As we evaluate the 2024 roadmap later this year, please share your thoughts and questions about our plans with regards to the share button.
This change will automatically be applied to all communities beginning with the 23.6 release and beyond. We have removed the following components from the code base and all community pages:
- <component id="external.widget.add-this"/>
- <component id="external.widget.share-button"/>
- <component id="message-view.widget.share-button"/>
- <component id="share-button"/>
Additionally, the Display social bookmarking links setting is turned off and removed from Community Admin.
You Found it! We Fixed it!
General fixes
- Previously, when community admins granted permissions to members to access certain community pages, members were not able to access the pages and an exception error was displayed. This issue is fixed. Now, members with appropriate permissions can access the community pages.
- Previously, the “LithiumCookiesAccepted” cookie for cookie banner v1 and "LithiumPerformanceCookiesAccepted", "LithiumTargetingCookiesAccepted", "LithiumFunctionalCookiesAccepted", and "LithiumNecessaryCookiesAccepted" cookies for cookie banner v2 were being dropped even if the Out of the Box (OOTB) cookie banner was disabled in the community. This issue is fixed. Now, these cookies no longer get dropped if the OOTB cookie banner is disabled. Learn more from the Khoros Cookies Datasheet.
- Previously, when members clicked the link to navigate to the discussions of any Q&A board that came in their email notifications, they received a HTTP Status 500 error. This issue is fixed. Now, members can navigate to the link to view the discussions.
- The issue where the prefix “Re:” was not added to the autosave drafts when replying to the root discussions of forums v5 is fixed.
- Previously, when members tried to post a reply to the discussions where the lazy load config and recaptcha are enabled for Forums and inline replies, they received an exception error and the captcha action did not complete successfully. This issue is fixed. Now, members can successfully complete the captcha action while replying to the discussions.
- The issue where files with ‘.swu’ extensions failed to upload in the community posts is now fixed.
- Vulnerabilities issues in Jquery Ui 1.8.23 are fixed.
- The issue where a Group hub owner could add a user in the Group hub instead of the user requesting or accepting to join the Group hub is fixed.
- Previously, in communities version 21.12 and 21.10, the member list pages in Group Hubs did not have the pagination functionality. This issue is fixed.
- The issue where the IdP metadata updates of Core SAML Self Service did not sync across the nodes in the community is fixed.
Accessibility fixes
- The issue where the <html> tag did not have the language attribute with proper language code as the value for the attribute is now fixed.