• Announcements
• EoL - Oracle AddThis button
• Enhancements
• API configuration to remove EXIF data from images based on allowed list
• Migrate Community Event’s Zoom Authorization from JWT to Zoom SDK App
• You found it! We fixed it!
• General
• Accessibility

Announcements

EoL - Oracle AddThis button

As per the announcement from Oracle that AddThis will be decommissioned on May 31st, 2023, we will end our support for the AddThis share button on Community Classic. This change will automatically be applied in upcoming releases.  The components will be removed from the code base and therefore, will be removed from your community pages. Additionally, the setting “Display social bookmarking links” will be disabled and removed from the Community Admin.

Starting now, you can begin disabling this setting on your own on your stage sites by navigating to admin>>”applicable discussion styles”>> Uncheck Display social bookmarking links>> Save.

If you experience any styling issues with the removal of the “Share button”, submit a support case.

Enhancements

API configuration to remove EXIF data from images based on allowed list

With this release, the Content Metadata API has been configured to selectively retain and retrieve EXIF and non-EXIF metadata of images mentioned in the allowed list. The configuration is applicable to all uploaded images in the community such as the images in posts, gallery, profile pages, avatars (node and user), image console page, and image widgets. However, images downloaded from the community do not contain any EXIF metadata. Contact Support to add applicable EXIF metadata in the allowed list. This configuration is applicable to the images with JPEG and PNG formats.

Migrate Community Event’s Zoom Authorization from JWT to Zoom SDK App

Previously, members hosted Community Events with Zoom by authenticating Zoom with JWT app type credentials (API ID and secret key). As Zoom has announced End of Life (EOL) for JWT type apps, we no longer authorize Zoom with JWT app type credentials.

With this release, members can authorize Zoom with the Community Events using Zoom SDK App using Client ID and Secret Key. These keys can be generated from the Zoom SDK App.

Customers who use Zoom integration to host Community Events will receive this upgrade. They must reconfigure their Zoom integration to host the Events seamlessly.

To reconfigure Zoom integration, learn more about Integrate Zoom with Community Events.

You found it! We fixed it!

General

• Previously, when members created posts by attaching documents (.docx) in Community v23.2 or later, the posts were not indexed in search engines, and when users tried to search for these posts, the posts were not displayed in search results. This issue is fixed. Now, posts that include attachments are indexed and displayed in search results. This fix has also been backported to 23.2, 23.3, and 23.4 Community versions.  
  
  
• Previously, when a member's username and email address were updated using the restbuilder and restadmin method with the Allow SSO user Email Changes setting turned on in Admin > System > SSO, the username was updated and the email address was not. This issue is fixed. Now, when a member updates both the username and email address with setting turned on, both the username and email address are updated. 
  
  
• Previously, when a config related to ‘dynamic subject for replies’ was enabled and members tried to move replies or inline replies of a discussion to another location, the subjects associated with the moved replies did not appear in the new location. This issue is fixed. Now, the replies that are moved to the new location include the respective subjects. 
  
  
• Previously, when users registered to the community via SSO without filling in their profile details, then tried to reply to a forum discussion by clicking the Reply button, the Reply button was grayed out, and the members were not redirected to update their profile details. This issue is fixed. Now, when partially registered members click Reply, they are redirected to update their profile details. 
  
  
• The issue where members’ online statuses were intermittently displayed as offline even when they were signed in to the community is fixed. 
  
  
• Previously, when members tried to attach TGML (.tgml) and AUT (.aut) files to a draft post in the community, the files failed to upload, and an error message was displayed indicating that the file extensions were not supported. This issue is fixed. Now, members can successfully attach TGML and AUT files while creating a new post or replying to a post in the community. 
  
  
• Previously, when members using Microsoft Windows created syndication widgets and tried to add emojis in their posts or replies (comments), the emojis appeared in large sizes instead of their actual sizes. This issue is fixed. Now, the added emojis appear in their actual sizes in the posts or replies. 
  
  
• Previously, when members requested to join closed group hubs, the group hub owners did not receive email notifications regarding the request. This issue is fixed. Now, group hub owners receive email notifications when members request to join closed group hubs. 
  
  
• Previously, in SSO communities, when group hub owners managed group hub members via Member Management, the changes made to member accounts were also applied to other members with the same username. This issue is fixed. Now, the changes made by group hub owners apply only to the respective member even if the group hub has members with the same username.  

Accessibility

• The issue where members were unable to perform keyboard navigation across the community is fixed.