Problems with paragraphs in a content moderation flow on a jsonapi powerd next-drupal decoupled website

Created on 6 July 2022, over 2 years ago
Updated 15 March 2023, over 1 year ago

Problem/Motivation

On a site with content moderation and paragraphs: if you enable translations on the paragraphs field of a node, CM "Latest version" tab allows you to directly publish a draft. In this case only modified paragraphs get saved and inconsistencies in revisions between the node field and the paragraph entities revisions arrise. This could mean jsonapi detects a paragraph as non current and disallows viewing for anonymous users.

Steps to reproduce

Allow translations for a paragraphs field on a node in combination with the core Content Moderation module. One could use https://www.drupal.org/project/paragraphs_asymmetric_translation_widgets + patches to allow such use case.

Proposed resolution

node_field_
field data should correspond with paragraphs_item en paragraphs_item_revisions tables in all circumstances, so jsonapi skips access checks on published content.

Remaining tasks

User interface changes

None as of yet.

API changes

None as of yet.

Data model changes

None as of yet.

Release notes snippet

None as of yet.

🐛 Bug report
Status

Postponed: needs info

Version

9.5

Component
Content moderation 

Last updated 1 day ago

Created by

🇳🇱Netherlands jb044 Leeuwarden

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

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.

  • 🇵🇱Poland henk

    I had similar problem Content moderation + translated paragraphs + after adding/editing translations in node display paragraphs was mixed from different languages. Paragraphs revision was taken from origin language instead of translated version.

    Problem appears after upgrade to Drupal 9.4 from Drupal 8.9.

    In this case i disable content moderation for problematic content type and save revisions in all languages, to fix it. Problem was only with edited node after upgrade, so will be hard to reproduce it on clean instance.

Production build 0.71.5 2024