v8.7.2

New features and improvements

• Allow admins to initiate a 24-hour deletion of a user account via the User Drawer>Account History in the Moderation interface. This makes it easier for sites that don't use our GDPR features or the API endpoint to be compliant with any data deletion laws #4481
• Update references in embeds from Twitter to X #4482
• Add international Outlook accounts to protected email domains #4484
• Update banned word rejection messaging to be DSA compliant #4490
• Add NL translations for DSA strings #4496 thanks @rmens
• Update license to current year #4495 thanks @immber
• Update client handler to add a port to the root URL for local development #4489
• Create a docker-compose and README for setting up a Wordpress environment to work with Coral local development #4491

v8.7.1

• Add optional Top Commenter badge feature for commenters who've had a comment featured by a staff member #4462
• Add requirement to select a rejection reason when rejecting all comments with DSA enabled #4455
• Add max length validations for DSA input fields #4466
• Allow anonymous DSA reporting #4469
• A user's auth token is cleared and the stream reloaded when the token is invalid or expired #4472

v8.7.0

• Upgrade Coral's codebase to Node.js 18 in order to improve its security and performance (#4451)

v8.6.5

New features

• For orgs using multi-site instances, site filters on moderation queues now include a text search #4313, #4468
• Add utilities for adding tenants to existing deployments #4428

Adds the following indexes:

db.sites.createIndex({ tenantID: 1, "$**": "text", createdAt: -1 });

v8.6.4

• Add optional new feature to pre-moderate email addresses based on certain spam-like qualities. Findable under Admin > Config > Moderation (#4458)

v8.6.3

Bug fixes and improvements

• Fix permissions bug so that admin users can archive stories #4357
• Update Dutch translations #4369
• Add COMMENT_LEFT_MODERATION_QUEUE to webhook configuration options #4380
• Add rr.com to the protected email domains list #4383
• Fix bug of some error translations not working by using locale to translate GraphQL errors if available #4385
• Fix share comment interaction event to only fire once and add event for report comment interaction #4387
• Update styles for the Community table of users in the admin #4388
• Truncate comment body sent to Slack to stay under character limits #4392
• Update link to docs in the moderation phases admin configuration #4397
• Update broken links in docs #4390
• Fix broken link in css.md #4401
• Fix broken link to CSS variables doc #4429

v8.6.2

DSA-related features and fixes

• Fix reported states for comments for archived, Q&A, and Ratings & Reviews stories when the data cache is enabled #4426
• Fix translations not working on commentModerationActions when user accounts are deleted #4427
• Show rejected state instead of link to view in stream when DSA report comments are rejected #4431
• Display related reports on single DSA report screen #4434
• Update DSA CSV download info for timestamp and comment media #4435
• Add required custom reason field to Other comment rejection reason #4436
• Add rejection reasons to comment cards and user drawer in admin #4439
• Add view DSA report link with illegal content report info in admin comment moderate card #4442
• Update copy for comment rejection notifications #4443
• Update copy for DSA report submission errors #4445

v8.6.1

• Fixed an issue where commenting and moderation weren't working for existing tenants without DSA enabled #4440

v8.6.0

New features

We've added a series of optional new features aimed at publishers who are either based in the EU, or who deliberately target EU audiences, so that they can be compliant with the EU's Digital Services Act (DSA). The relevant part of the DSA comes into operation on 2/17/24.

The new DSA-related features can be activated by admins inside the 'Configure' menu by switching on the "DSA reporting and moderation experience."

Our DSA features include:

• The ability for end users to report comments for containing illegal content, adding relevant context
• The ability for moderators to review reports of illegal content in a specific tab in the moderation interface labeled "DSA Reports." Moderators can then add notes, mark reports as "In Review", download CSVs for legal review, review the commenter's prior behavior, and make a final decision
• The ability for moderators to add specific reasons for comment rejection
• The ability for end users to receive notifications related to their reports and rejected comments

The branch for this work is #4356

v8.5.3

Bug fixes

• Fix static asset deploys #4363