Skip to content
This repository was archived by the owner on Jul 22, 2025. It is now read-only.

Conversation

@keegangeorge
Copy link
Member

@keegangeorge keegangeorge commented May 27, 2025

🔍 Overview

We want to unhide ai_spam_detection_enabled setting so that we can retain staff action log features. However, we also want to ensure users cannot enable spam detection without having AiModerationSetting.spam present in the database.

In this update we unhide the setting, but also add a validator to ensure the necessary configuration is in place before allowing the setting to be enabled.

Test is omitted as it's quite tricky to test. When test env is booted, it tries and validate all settings so we run into errors, before checking.

📷 Screenshots

Screenshot 2025-05-27 at 13 55 19

## 🔍 Overview
We want to unhide `ai_spam_detection_enabled` setting so that we can retain staff action log features. However, we also want to ensure users cannot enable spam detection without having `AiModerationSetting.spam` present in the database.

In this update we unhide the setting, but also add a validator to ensure the necessary configuration is in place before allowing the setting to be enabled.
@keegangeorge keegangeorge merged commit 297c64c into main May 28, 2025
6 checks passed
@keegangeorge keegangeorge deleted the dev-unhide-spam branch May 28, 2025 14:50
keegangeorge added a commit that referenced this pull request Jun 6, 2025
## 🔍 Overview
This update re-introduces the validator used on the `ai_spam_detection_enabled` setting. It was initially added here: #1374 to prevent Spam from being enabled without creating an `AiModerationSetting` value in the database. However, due to issues with backups/migrations we temporarily removed it here: #1393. Now with some internal fixes, we can re-introduce it. We also update the validator so that it only validates when trying to turn on rather than when turning off too.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants