feat: update init file#276
Conversation
This adds feature of AI moderation system enabled with discussions.enable_ai_moderation waffle flag. This is MVP so various changes on top of this are expected.
Implements soft delete functionality for discussion threads, responses, and comments using the is_deleted flag instead of permanently deleting records. This enables safe deletion and restoration of discussion content while preserving existing data.
Implements soft delete functionality for discussion threads, responses, and comments using the is_deleted flag instead of permanently deleting records. This enables safe deletion and restoration of discussion content while preserving existing data.
This PR removes the read state deletion from the soft-delete thread operation in the MongoDB backend to preserve user read states when threads are soft-deleted, enabling proper restoration and improving performance by eliminating a 5-minute operation.
This PR adds automated deletion of spam forum content detected by AI moderation. The feature is controlled by a new waffle flag discussions.enable_ai_auto_delete_spam and works in conjunction with the existing AI moderation system.
…s deleted (#17) When a comment or response is reported, a "Reported" badge appears in the post sidebar to alert moderators. However, if the reported content is deleted, the badge remains visible even though there's nothing left to review, causing confusion. The badge should only appear when there's at least one reported comment that hasn't been deleted. Once all reported comments are removed, the badge should disappear automatically.
* chore: bump version * fix: user vote query optimization * fix: e2e test case not related to this PR
…vel controls (#7) This update introduces a comprehensive Mute / Unmute feature for discussion forums, enabling learners and staff to manage unwanted interactions more effectively while maintaining a healthy learning environment. The feature supports both personal and course-wide mute scopes, with clear role-based restrictions and overrides. The implementation ensures muted content is hidden retroactively as well as for future posts, without notifying muted users. Special handling is included to prevent learners from muting staff or themselves, while giving staff full moderation control across the course.
Bulk delete functionality is currently implemented only for the MongoDB backend, while the corresponding implementation for the MySQL backend is still pending. As part of the migration from MongoDB to MySQL, it is essential to implement bulk delete support in the MySQL backend to ensure feature parity and consistent behavior across both systems.
Adds the missing audit log entry for muted learners in the MySQL table to ensure all mute actions are properly tracked. This improves visibility and consistency in learner moderation records.
Fixed discussion moderation permissions to restrict delete, ban, mute, and restore operations to discussion moderators only. Course staff and course instructors were incorrectly granted full moderation privileges when mute feature was added - they are authoring roles and should not have discussion moderation access.
…#28) The migration script did not handle soft-deleted fields, resulting in deleted content not being correctly migrated. Updated the script to include soft-deleted records and ensure proper migration of deleted content.
This reverts commit 4535222.
Revert "feat: add instrumentation to forum"
Team posts are not appearing in the discussion/forum after being created. The post creation flow completes successfully without any errors, but the newly created posts are not visible in the UI.
…orum (#38) After migrating the forum backend from MongoDB to MySQL, user retirement via the retire_forum API was failing due to MySQL-specific constraints that were not handled correctly in the existing implementation.
|
Thanks for the pull request, @naincy128! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Submit a signed contributor agreement (CLA)
If you've signed an agreement in the past, you may need to re-sign. Once you've signed the CLA, please allow 1 business day for it to be processed. 🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
openedx-webhooks
added
the
open-source-contribution
mphilbrick211
moved this from Needs Triage
to Needs Tests Run or CLA Signed
in Contributions
|
Hi @naincy128! Welcome, and thank you for this contribution! In order for your CLA check to turn green, you'll need to submit a CLA form. If you are contributing as an individual, please fill out the individual CLA form here. If you are contributing on behalf of an organization, please have your manager reach out to oscm@axim.org so you may be added to your org's existing entity agreement. Please let me know if you have any questions. Thanks! |
7 participants
Merge checklist:
Check off if complete or not applicable: