Node save required to get newly added fetched field to show up

Created on 4 January 2024, over 1 year ago

Problem/Motivation

There is an odd case where if you add a fetched field to a content type. The fetched field will not show on nodes of that content type until a new save of that node has occurred.

This might be caused by computed values being set artificially in setValue() https://git.drupalcode.org/project/entity_field_fetch/-/blame/1.0.x/src/... instead of with a computed value class.

It would be nice if a node save was not required to get the fetched field to show.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States swirt Florida

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @swirt
Comment over 1 year ago →
🇺🇸United States swirt Florida
This might be resolved by 🐛 Entity Field Fetch should return a value via JSON:API Active
Comment over 1 year ago →
🇺🇸United States swirt Florida
I was hoping this would be resolved by 🐛 Entity Field Fetch should return a value via JSON:API Active but it was not. Also this may not be a bug in the sense that for any other field, if we added a field to an existing content type, we would not expect or want a value to magically show on the published revision of that field that existed before the new field did.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024