Parent entity ID is not presented to the view when used in a view

Created on 27 January 2023, almost 2 years ago

Updated 15 April 2024, 7 months ago

Problem/Motivation

Using a Views Reference Field in a content type alongside Paragraphs fields could allow to generate highly customizable displays (teaser etc.).

Steps to reproduce

For example, say I have an Article content type with a Paragraphs field.

This paragraph field allows 3 Paragraphs entity types :

Image Paragraphs
Text Paragraphs
"useful information" Paragraphs

These 3 Paragraphs types can be mixed in number and order (image + texte + image + useful information or text + useful information + image)

Now if I want to customize the teaser display in order to show only the first available image followed by the first text trimmed, I can create two views, one getting the first available image, the second the first text trimmed.

I then add two Views Reference fields to the Article content type.

Such Views Reference fields can access the other Article fields only when the node is the main content. If the node is to be retrieved in a view, the Views Reference fields lose the link.

Proposed resolution

I’m not sure if this use would be or not out of scope for the Views Reference Field module, or if there is already a better solution with other modules.

🐛 Bug report

Status

Closed: duplicate

Version

2.0

Component

Code

Created by

🇫🇷France Zigazou

Live updates comments and jobs are added and updated live.

views integration

Comments & Activities

Issue created by @Zigazou
Comment almost 2 years ago →
🇫🇷France Zigazou
I attached a patch file which works in my case but I highly suspect it does not take into consideration lots of other use cases, neither is it solid.
Comment over 1 year ago →
🇳🇱Netherlands seanB Netherlands
I think this is a duplicate of 💬 Parent field entity in plugin interface Fixed . We can pass the data to the view using $view->element['#viewsreference'] so other (custom) views alter hooks can do with the data whatever they want. Does this solve the issue?
Status changed to Closed: duplicate 7 months ago6:23pm 15 April 2024
Comment 7 months ago →
🇫🇷France Zigazou
Sorry to reply this late.

Yes, this solve the issue.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024