referenced entities of a different bundle are in a weird state after import

Created on 22 January 2025, 2 months ago

Problem/Motivation

If I have a single channel for page nodes, and my page nodes have a reference field to article nodes, then referenced article nodes are pulled, and have a row in the {entity_import_status} table, but aren't visible in the pull UI.

Steps to reproduce

1. create a reference field on page nodes that points to articles
2. create:
- an article node, node A
- a page node which points to the article, node P
3. create a channel for page nodes

When the page node is pulled, the referenced article node is pulled in too.

The article node gets a row in the {entity_import_status} table, but in at admin/content/entity_share/pull you can't see it, so the user can't specifically update it.

If node A is updated, then that page obviously doesn't report that node P has changed.

If the user knows that node P references node A, then they can ticky the box for node P and import P, even though it's unchanged on the server. That will then cause node A to be updated.

Proposed resolution

No idea, unfortunately!

This sort of problem crops up because Entity Share is quite closely coupled to JSONAPI's way of slicing content up per-bundle, but it doesn't work with how users work with content.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

3.0

Component

Entity Share Client

Created by

🇬🇧United Kingdom joachim

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

Comments & Activities

Production build 0.71.5 2024