Change view mode for custom content from "don't include" to "default" break the index process

Created on 16 October 2023, about 1 year ago

View Index (/admin/config/search/search-api/index/default_index) press "Index now" and batch/cron hang on with no errors.

Install Drupal with search_api, search_api_db, search_api_db_defaults and after that uninstall search_api_db_defaults
theme which adds custom node type "News" (has display mode full content and search result highlight - which is working)
theme which adds custom node type "Paragraphs Page" (has display mode default and search result highlight - which is NOT working)
set 1 custom node type to full via drush: drush config:set --input-format=yaml search_api.index.default_index field_settings.rendered_item.configuration.view_mode.entity:node "{news: full}"

until here, the 1 content type is working as expected.

But then I changed this via backend UI:

/admin/config/search/search-api/index/default_index/fields: change view mode for content from "dont inlcude to default
Under /admin/config/search/search-api/index/default_index/fields in the group general the "rendered_item" press edit button (/admin/config/search/search-api/index/default_index/fields/edit/rendered_item) and change "View mode for Content" (my new content type) from "Don't include the rendered item." to "Default".
Press save, and then save again on the fields overview page.
Now press "Clear all indexed data" or "Rebuild tracking information" for clearing the index.
Now, I flushed the Drupal cache.

Is the problem that the content type "Paragraphs Page" has a field with a reference to the search api view, so maybe recursive?

🐛 Bug report

Status

Closed: works as designed

Version

1.30

Component

General code

Created by

🇩🇪Germany thomaswalther Rhein-Main Area

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @thomaswalther
Status changed to Closed: works as designed about 1 year ago11:28am 16 October 2023
Comment about 1 year ago →
🇩🇪Germany thomaswalther Rhein-Main Area
I found in Drupal logs:

Recursive rendering detected when rendering entity media: 3, using the field_parapage_media field on the node:news 3 entity. Aborting rendering.
so I think it's the recursive problem of a node type "paragraph page" with a view of search indexed content

Production build 0.71.5 2024