Do NOT force a new entity revision in content moderation

Created on 26 July 2019, over 5 years ago
Updated 16 September 2024, 3 months ago

Problem/Motivation

Created based on discussions in #2803717: Allow 'syncing' content to be updated in content moderation without forcing the creation of a new revision .

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

11.0 🔥

Component
Content moderation 

Last updated 2 days ago

Created by

🇦🇺Australia Sam152

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇩🇪Germany geek-merlin Freiburg, Germany

    Yes, this gave me headaches too.

    Closed an issue as dup.

  • 🇩🇪Germany geek-merlin Freiburg, Germany
  • 🇮🇳India anandhi karnan Chennai

    Hi @sam152

    I am currently analyzing the ticket regarding content moderation and entity revisions. To ensure that I address the requirement accurately, could you please clarify the following points:

    1. Revision Creation Criteria: What specific criteria should be used to determine when a new revision should or should not be created for content? For instance, should revisions only be created when certain fields are changed, or is there another criterion?
    2. Non-Syncing Content Definition: Can you provide more details on what constitutes "non-syncing content" in this context?
    3. Preferred Approach: Are there any existing solutions or approaches that are recommended for handling this issue?

    Understanding these points will help me make the necessary adjustments to avoid unnecessary revisions and improve content moderation.

Production build 0.71.5 2024