Published state for translated node

Created on 29 June 2023, over 1 year ago
Updated 27 April 2024, 7 months ago

Problem/Motivation

Setting the "Published (status)" target against a source (which is tampered as "Convert to Boolean", only alters the default/English language node and leaves the translated node as published.

Steps to reproduce

Preface: it is assumed you have Drupal 9.5.9 installed with all needed language modules set up, and at least 1 additional language installed, with the article content type set to be translatable.

1. Create a new feed type using the "Upload file" fetcher, and "JsonPath" parser, Node processor, and article content type
2. Add the mapping as stated (per the attached JSON example):
- "Published (status)" target to "status" source
- "Published (status)" target to "status" source, configured setting set to French
- "Title (title)" to "title_english"
- "Title (title)" to "title_french", configured setting set to French
- "Body (body): Text" to "type"
3. Context should be set to "$.items.*"
4. Save and edit tamper
- On "status -> Published: value" add "Convert to Boolean" tamper
- Truth set to "Active", False set to "Inactive"
- Submit changes
4. Create new feed based on the type just created.
5. Import items
6. Observe the 2 nodes imported with translations. The item with the "Inactive" status, is still published while english is unpublished

Other steps tried:
1. Setting language on all "Published" targets
2. Only having 1 "Published" target, in hopes it would apply to all

Proposed resolution

If "Published (status)" set as target, feeds should respect the language being set on and update accordingly.

Current workaround/solution is to not allow the published value to be translated so what happens on the default language, persists to the translation.

🐛 Bug report
Status

Active

Component

Code

Created by

🇨🇦Canada nicole.harnish Halifax

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

Comments & Activities

Production build 0.71.5 2024