indexing nested fields of selected entity ref field

Created on 27 April 2023, almost 2 years ago
Updated 6 July 2023, over 1 year ago

Problem/Motivation

When using nested fields ( in my case nested paragraphs), it is required to add all combinations of nested fields for proper content indexation.
It would be a life-changing breakthrough if a field added for indexation would index all fields contained in it.

Alternatively , Adding one re-used field for indexation, should index it, no matter where it s placed in the nested tree.

Steps to reproduce

- Create a few nested paragraphs with a field content in it
- Try to index the content field , figuring out all possible combinations
- Realise it is quite a configuration task
- Dream of magic

Feature request
Status

Active

Version

1.0

Component

Plugins

Created by

🇫🇷France matoeil

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

Comments & Activities

  • Issue created by @matoeil
  • 🇦🇹Austria drunken monkey Vienna, Austria

    Thanks for suggesting this feature!

    While we cannot really change the behavior when marking a field for index (since that would break people’s configuration), this does sound like functionality that could be implemented in some optional way – for instance, as a processor.
    However, I fear that I currently don’t have time to work on feature requests, except in an advisory capacity. So, if you want to propose a patch (please remember to include tests), I’m happy to review it. (Or provide pointers on where to start.) Otherwise, we’ll have to hope someone else comes along and provides a patch (or hires me to do it).

    That being said, if this is just about getting all the fulltext contents of a paragraph (or the entity that includes it), the recommended way of doing that is to add the “Rendered HTML output” field to the index, which will also (depending on the view mode, of course) include all the paragraph data attached to the entity. (For optimal results, create a new view mode without any field labels, images, etc.).

  • 🇫🇷France matoeil

    as the Rendered HTML output solves it for me, u can choose to close the issue.
    This feature would be useful though when not wanting to index the whole content of the entity

Production build 0.71.5 2024